A process engine for work that branches.
A workflow is more than a series of prompts. Runfabric makes paths, decisions, handoffs and external effects part of an inspectable, versioned process.
Design with your agent. Operate with confidence.
Start with the outcome and the systems involved. Your agent discovers the schema and installed integrations, writes a definition, validates it and publishes a version. You can inspect and edit the graph or its JSON at any time.
Published versions are immutable. Editing a draft does not silently change a run that is already under way. Each run retains its own definition and the record of what happened.
Control flow is part of the product.
| Capability | How it works |
|---|---|
| Conditions and switches | Route data down named paths based on comparisons, classifications or explicit values. |
| For-each and repeat | Process a collection or repeat a bounded process until its condition is satisfied. |
| Parallel branches | Start independent work together, then join when every branch has finished. |
| Transforms | Build structured values from inputs and previous results using declarative expressions. |
| Waits and schedules | Pause until a due time, or start published workflows on a recurring schedule. |
| Human approvals | Park a run for a recorded approval or rejection, with a separate path for each. |
| Integration activities | Call configured HTTP APIs, MCP tools, model-backed agents or a private local worker. |
A failure and an unknown result are different.
A request can time out after another system accepted it. Runfabric does not promise exactly-once effects across every provider. Activities carry stable work identities, fenced leases and explicit execution modes. Uncertain writes require reconciliation.
Inspect attempts, decisions and outcomes alongside the versioned graph. Your agent can retrieve the same evidence through the SDK, CLI or MCP and determine the next action.
Choose where the work runs.
Hosted integrations execute permitted HTTP, remote MCP and agent work. Profiles fix destinations, operation mappings and credentials. A workflow supplies structured data; it does not supply an unrestricted shell or a provider key.
Run a worker where your private systems live. It claims only activity kinds allowed by its Project Key and invokes explicitly configured commands or local MCP servers. Runfabric persists the process without needing access to your machine.
A composable product.
Sentient can use the TypeScript SDK to compose workflows with knowledge and model services. A standalone coding agent can use the same product without adopting an organization operating system.