[ pricing ]
Priced like infrastructure, not like seats
Every plan includes unlimited collaborators, full tracing, and the API. You pay for what runs.
2 months free, billed annually
Build
For proving the first workflow.
$0free while you build
- 3 workflows in production
- 50k events / month
- 7-day trace retention
- Community support
Scale
For teams running real volume.
$890per month
- Unlimited workflows
- 5M events / month included
- 90-day trace retention
- Approval gates & replay
- SSO · audit log export
- Support with a 4-hour SLA
Enterprise
For regulated and high-volume estates.
Customannual agreement
- Custom event volume
- Regional data residency
- Customer-managed keys
- SCIM · custom retention
- Dedicated environment option
- Named engineer & 99.95% SLA
[ faq ]
Asked in most evaluations
Does Orlix replace our existing queue or scheduler?
No. Orlix sits above them. Steps can enqueue jobs, call services, and wait on external systems — the durable state, gating, and tracing live in Orlix while execution stays where it is.
Which model providers are supported?
Any provider with an HTTP API, plus self-hosted models behind your own endpoint. Routing is declared per step, so swapping providers is a config change, not a rewrite.
Where does our data live?
In the region you choose per workflow — us-east, eu-west, or ap-south today. Traces are retained per your plan's policy, and Enterprise can bring customer-managed keys.
How do human approval gates work?
A gate is a step. It holds the run, notifies the declared owner in Slack, Teams, or email, and records the decision — who, when, and with what context — in the audit trail.
Can we run Orlix in our own cloud?
Enterprise plans can run a dedicated environment in your cloud account with the control plane managed by us. Fully self-hosted deployments are on the roadmap, not shipping today.
What does migration from a homegrown pipeline look like?
Most teams wrap their existing scripts as steps first, then decompose. The first workflow typically reaches production in under two weeks; nothing requires a big-bang rewrite.
Put your next workflow on rails
A 30-minute walkthrough with an engineer — your use case, not our slides.