AI agents
Persist model and tool boundaries, enforce budgets, and wait safely for approval.
Use cases
Choose the recovery boundary your process needs
The same engine can serve different industries, but the useful design question stays concrete: what must survive a crash, how long can it wait, and which effects must never be repeated?
SaaS operations
Run onboarding, billing, lifecycle messaging, and account tasks across retries.
Financial workflows
Make consequential effects explicit, idempotent, and reconcilable.
Outreach sequences
Coordinate scheduled steps and replies without duplicate sends.
Solana automation
Separate chain confirmation from durable off-chain process state.
A quick fit test
| Process trait | Likely starting point |
|---|---|
| One short scheduled task | Cron with overlap protection and alerts |
| Many independent jobs | A queue with idempotent consumers |
| Multi-step state across failures or days | A durable workflow |
| A consequential external call | An effect ledger and reconciliation, whatever the scheduler |
Verify the technical details
The documentation is the source of truth for current behavior.