Four editions. Seats included.
From € 30/month, billed monthly. Every edition ships with developer and operator seats; add more when you outgrow them.
All prices in EUR, excl. 21% VAT.
Solo
One builder, a team that runs the work
Includes 1 developer + 3 operators. Extra operator seats on request.
1 developer
- 1 developer seat, 3 operator seats included
- Cloud only
- Extra operator seats on request
- Self-serve — no onboarding included
Teams
A working automation team
Includes 3 developers + 9 operators. Extra operator seats on request.
2–10 developers
- 3 developer seats, 9 operator seats included
- Up to 10 developers — beyond that, Business
- Cloud only
- 2 hours of online onboarding
Business
Modelled processes, on your infrastructure if you want it
Includes 6 developers + 18 operators. Extra operator seats on request.
11–50 developers
- 6 developer seats, 18 operator seats included
- Up to 50 developers — beyond that, Enterprise
- Cloud, Managed Cloud or self-hosted
- BPMN process flows and DMN decisions included
- 4 hours of online onboarding
- Support SLA available, by quote
Enterprise
Your governance, your infrastructure
Seats, hosting and support scoped and quoted with you.
50+ developers
- Unlimited developers and operators
- Cloud, Managed Cloud or self-hosted
- Managed Cloud and self-hosted can be white-labelled
- 8 hours of onboarding, online or on-site
- Support SLA available, by quote
Seats
Two kinds of seat. Developers build the automations; operators run them. Each edition includes both, and you can add more on top.
An API consumer is an operator
Operator seats are not only people. Anything that calls Orvanta to run work — a service account, an API token, another system in your estate — consumes an operator seat, exactly as a human operator does. Count your integrations when you count your seats: for most teams the API consumers, not the people, decide the number.
Operator seats are added to any edition, up to that edition's operator cap — we price them with you when we scope the plan, so count your API consumers before you ask. Developers work differently: the maximum above is a ceiling, and going past it means moving up an edition rather than buying another developer seat.
Self-hosted seats cost less than managed cloud ones, because you provide and run the infrastructure. Self-hosting is available on Business and Enterprise.
Where it runs
Three options. Cloud is shared infrastructure on every edition: we apply each release as it ships and your workspaces are isolated to your organisation. Managed Cloud gives you your own subdomain with the hardware run by us. Self-hosted puts you fully in control of the infrastructure. The last two start at Business.
Cloud
Solo · Teams · Business · Enterprise
We run Orvanta on shared infrastructure and apply every release as it ships, so you are always on the current version. Your workspaces are isolated to your organisation. Available on every edition, and the only option on Solo and Teams.
Managed Cloud
Business · Enterprise
Your own Orvanta on your own subdomain — client.orvanta.cloud. We manage the hardware, so you can focus entirely on the orchestration and not on the DevOps underneath it.
Self-hosted
Business · Enterprise
Your infrastructure, fully under your control. We provide the image and the licence key; we publish updates and applying them is yours to do. The right choice when you already have a DevOps or platform team running your infrastructure. Seats cost less self-hosted, because you provide the compute.
White label
Enterprise only · Managed Cloud or Self-hosted · by quote
Run Orvanta under your own brand instead of ours, on Managed Cloud or on your own infrastructure. Not available on Cloud: shared infrastructure cannot carry one customer's brand. A bespoke engagement with its own commercial terms, scoped and quoted per case.
Support
Every edition includes product support. A contracted response time is a support SLA, available on Business and Enterprise — on any deployment, Cloud, Managed Cloud or self-hosted. Solo and Teams have no SLA.
Custom pricing
Every SLA is quoted, so none of them is listed
What a support contract costs depends on things we can only know once we have seen your estate: how complex it is, how many timezones have to be covered, and how many people we hold on standby to meet the response time. A self-hosted deployment costs more to support than one we run. Rather than print a figure you would have to renegotiate, we scope it with you and quote it with the rest of your contract.
Contact salesOne response commitment per tier, with no severity levels, measured from the moment a ticket is raised. Response times apply on the channels listed for that tier.
Solo vs Teams vs Business vs Enterprise
What each edition includes, and what changes when you move up. Solo is a strict subset of Teams; Business adds seats, workspaces, self-hosting and process modelling in BPMN and DMN; Enterprise lifts the ceilings entirely and adds identity, compliance and event-integration capabilities on top.
An allowance of the edition, not a meter — you are never billed per run.
A hard ceiling. Past it you move up an edition; developer seats cannot be bought beyond it.
Developer counts are hard ceilings. If you need more developers than your edition allows, you move up an edition — developer seats cannot be bought beyond the limit. Operator seats can be added within an edition, up to its operator cap.
Onboarding
Included in the edition price, not billed separately. Solo is self-serve by design.
Developer Packages
Temporary extra development capacity: a one-off block of our developers' hours, added to your team to get things built, used within the first three months and on top of the onboarding your edition already includes. Available on Teams, Business and Enterprise — not on Solo, where self-serve is the whole promise. Pricing is on request, quoted with your contract.
Launch
20 h · 3 months
Remote
Ramp
40 h · 3 months
Remote
Accelerate
80 h · 3 months
Remote + on-site days