Reliant Engine · For platform builders
Coming soonReliant Workflows, inside your own product.
Reliant Engine is coming soon. It will let you embed Reliant Workflows in your own product, white-labelled, so your users run agent workflows inside your app without seeing Reliant. It is not available yet.
Your users would start a Reliant workflow from a screen in your app, watch it work, and approve its next step, without leaving your product or seeing ours. We are building it now. There is no date yet, so join the waitlist to hear when it is ready.
At a glance
What is real now, and what is coming
- Go SDKToday
- TypeScript SDKToday
- Scoped API tokensToday
- Webhook triggersToday
- A workflow view inside your appComing
- Your app keeps sign-in and navigationComing
- Workflows you publish, not an editorComing
Who it is for
Teams whose users should get agent workflows, inside the product they already use.
Developer tools
Let your users hand a task to an agent from inside your tool, follow it step by step, and review what it did before anything lands.
Internal platforms
Give the engineers in your company workflows your platform team wrote and reviewed, behind your portal and your sign-in.
SaaS products
Offer agentic features as part of your product rather than as a link out to someone else’s, with a person approving the steps that matter.
What is coming
What you would be able to do.
This is the direction, from the design work in the product today. All of it is coming, none of it is usable yet, and details may change before it ships.
A workflow view inside your app
ComingA white-labelled view of a run that your users open in your product: they send messages to a workflow, see each step’s progress, and answer approvals inline.
Your app keeps sign-in and navigation
ComingYour product owns identity. The embedded view asks your app for a token through the same small interface the TypeScript SDK uses today, and adds no sign-out button, settings or project switcher of its own.
Workflows you publish, not an editor
ComingYour users run and steer the workflows you chose for them. Authoring, terminals, files and settings stay with your team in Reliant, out of your product.
Part of your product, not a Reliant window
ComingThe point of white-labelling: the view sits inside your product as one of its screens, so your users see your product, not a second app to learn.
Available today
Start with the SDKs.
You do not have to wait to put Reliant behind your product. The SDKs are the same clients Reliant’s own app and command line use, licensed Apache 2.0 so you can ship them in commercial software. Today you build the screens yourself.
Go SDK
TodayFrom your backend: start a run, follow it to a verdict, answer the questions it asks, fire a trigger, and read the inbox.
No tagged release yet: you require it at a commit of main.
Go SDK docs ↗TypeScript SDK
TodayFrom your frontend: stream a chat live into a UI you build, resume after a dropped connection, and send messages that are safe to retry. Your app supplies the token.
Version 0.1.0, built from the repository: not on npm yet, and no React hooks yet.
TypeScript SDK docs ↗Scoped API tokens
TodayGive a service only what it needs: runs:start, runs:read, runs:control or triggers:fire, enforced on every call. Tokens stay on your server, never in a browser.
A token acts as the person who created it, so runs use that person’s connections and billing.
Credentials and scopes ↗Webhook triggers
TodayStart an automation from your own system with a credential that can do exactly one thing: deliver an event to that one trigger.
Enabling a trigger is a person’s decision in the app, not an SDK call.
Webhooks docs ↗
c, err := reliant.FromEnv() // reads RELIANT_TOKEN
run, err := c.Runs.Start(ctx, reliant.StartRun{
Workflow: "builtin://agent",
Message: "fix the failing test in ./internal/billing",
})
f, err := c.Runs.Follow(ctx, run.GetId(), reliant.FollowOptions{})
res, err := f.Wait()
fmt.Println(res.Succeeded)Built on the platform
The same pieces your team already uses.
An embedded workflow would not be a separate product. It would drive the same runs the Reliant app does.
Workflows in YAML
Agents mixed with deterministic steps, versioned in your repository, with lint and scenario tests.
Docs ↗Approvals and questions
A run can stop and wait for a person. The SDKs can report a pending approval, but only a person decides it.
Docs ↗Scoped credentials
Narrow tokens for services and single-purpose webhook credentials, so nothing in your stack holds more authority than its job needs.
Docs ↗Any model
Models from several providers, or bring your own, named in the workflow’s configuration. Your workflows are not tied to one vendor.
Docs ↗
Straight answers
What you want to know first.
When will it ship?
No date yet. Join the waitlist and we will email you when it is ready.
Can I build on Reliant today?
Yes. The Go SDK starts and follows runs from your backend, and the TypeScript SDK streams a chat into a UI you build. What is coming is the ready-made, white-labelled view, so you do not have to build those screens.
SDK overview ↗Whose account does a run use?
Today, a run executes as the person whose token started it, with that person’s machines, connections and billing. How runs started by your users are identified and billed in an embed is not settled yet; waitlist members will hear first.
Can I ship the SDKs in a commercial product?
Yes. Both SDKs are licensed Apache 2.0. The rest of the Reliant repository is under the Business Source License.
License FAQ ↗
Related
- Why ReliantOne platform that knows every seam, so your agents can too.
- Reliant WorkflowsMulti-agent workflows in YAML, on any model. Autopilot uses them to review pull requests, work issues and investigate alerts.
- SDK overviewWhat the Go and TypeScript SDKs do, their credentials, and what they deliberately cannot do.
Want it in your product?
Join the waitlist and tell us what your users would run. No date yet; you will hear first.
Rather talk it through? hello@reliantlabs.io or contact us.