Crash it yourself
Run a workflow, interrupt it, and watch it resume from its checkpoint.
Open the live crash demo →Orch8 · durable workflow engine
Keep AI agents running after the request ends.
Orch8 checkpoints long-running workflows across crashes, deploys, human approvals, and lost connectivity. The same Rust runtime runs on servers and offline-capable mobile devices.
Built for work where repeating a completed step is dangerous. For a short stateless job, use a queue.
Temporal-class durability in one self-hosted binary, with an embedded path for iOS and Android.
execution_01J8
One identity across every placement
- 1CloudAgent calls a toolcommitted
- 2HandoffWork moves to a deviceclaimed
- 3iPhoneLocal steps run offlinelocal
- 4HumanApproval pauses safelywaiting
- 5CloudThe same run continuesresumed
Completed boundaries stay completed. Only the next eligible step runs.
Proof you can inspect
Do not take a runtime’s recovery claims on faith.
There are no invented customer quotes or unlabeled benchmark tiles here. Test the failure path, read the code, and check the release history yourself.
Read the implementation
Inspect the Rust engine, storage adapters, migrations, and test suites.
Browse the source →Check what shipped
Release notes separate available behavior from planned work.
Read the changelog →Review the trust boundary
See credential handling, encryption scope, disclosure, and deployment responsibilities.
Read security details →How it works
Define a sequence. Commit each boundary. Resume the same run.
A sequence is a versioned workflow definition: steps, delays, branches, retries, signals, and placement rules. Orch8 owns the durable execution state; your handlers own the business logic.
welcome.json
{
"id": "welcome_drip",
"blocks": [
{ "type": "step", "handler": "send_email" },
{ "type": "step", "handler": "noop",
"delay": { "duration": 259200000 } },
{ "type": "step", "handler": "human_review" }
]
}curl -fsSL https://orch8.io/start.sh | shThe runtime boundary
Use Orch8 when time, failure, people, or placement changes the workflow.
It fits agent tool calls, payment recovery, lifecycle automation, field operations, and any process that must remember exactly what has already happened.
Resume after failure
Checkpoints persist completed boundaries. A restart continues eligible work instead of replaying the whole workflow.
Protect side effects
Effect receipts and stable idempotency keys make payment, email, and API recovery decisions explicit.
Wait without holding compute
Delays, signals, approvals, and retries persist for seconds or days while workers remain free.
Run where the work is
Use the Rust server runtime or embed the same engine through UniFFI on iOS and Android with local SQLite state.
Pricing
The engine is free to self-host. Managed Cloud starts at $49.
The same pricing data powers this summary and the full pricing page. Prices are USD before applicable tax; paid execution overages do not automatically stop workflows.
Self-hosted
Free
Run the complete engine on your infrastructure.
Run the quickstart →Starter
$49/month
Managed infrastructure for one operator shipping to production.
Start on Cloud →Pro
$199/month
Managed infrastructure for a production team.
Start on Cloud →Enterprise / OEM
Custom
Dedicated capacity, longer retention, and commercial licensing.
Discuss requirements →Talk to a human
Bring the workflow you are afraid to restart.
Tell us where it runs, which effects cannot repeat, and how long it may wait. We will reply with a concrete deployment path—or tell you a queue is enough.