Automation Integration · head to head
Orkes vs Ozone API

Orkes
Automation Integration
Commercial Conductor, now the maintainer of the workflow engine Netflix archived
- From
- Free
- Free plan
- Yes

Ozone API
APIs
Standards-compliant open banking API layer for banks and regulators
- From
- On request
- Free plan
- No
The short version
- Orkes is free; Ozone API prices on request.
- Only Orkes lists JSON workflow definitions; only Ozone API lists multi-standard support.
- Where Ozone API falls short: value is driven by regulatory obligation, so an institution not under a mandate struggles to build a business case for the spend.
- Prices and features on this page were last checked on 20 November 2026.
How do Orkes and Ozone API differ?
Orkes and Ozone API differ on starting price (Free against On request), free tier (Yes against No) and platforms. Only the attributes on which Orkes and Ozone API actually diverge.
Identical on both: pricing model (Quote).
Which features does each one have?
They share no listed features; 8 appear only for Orkes and 6 only for Ozone API. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Orkes
- JSON workflow definitions
- Polyglot workers
- Visual workflow builder
- AI and LLM tasks
- Human tasks
- Event handlers
- RBAC and secrets
- Hosted or self-hosted
Only in Ozone API
- Multi-standard support
- Consent management
- Developer portal
- Regulatory reporting
- Premium API monetisation
- Deployment flexibility
What is each one used for?
Ozone API is most often brought in for A regulator or standards body building national open finance infrastructure. The jobs each tool is most often brought in to do.
Orkes
- A microservices estate that needs orchestration across services written in different languages without a shared SDKnot Ozone API
- A team already running Conductor OSS that wants a supported distribution now that Netflix has stopped maintaining itnot Ozone API
- An AI platform composing agent steps, model calls and vector lookups as versioned workflow definitionsnot Ozone API
- A business process needing human approval steps interleaved with automated service callsnot Ozone API
Ozone API
- A building society facing an open banking compliance deadline with no API team of its ownnot Orkes
- A bank operating in several jurisdictions that must satisfy different open banking standards at oncenot Orkes
- A regulator or standards body building national open finance infrastructurenot Orkes
- A bank wanting to sell premium APIs beyond the regulatory minimum without building entitlement plumbingnot Orkes
Where do Orkes and Ozone API fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Orkes
- Netflix archived the Conductor repository in December 2023 and Orkes took over maintenance, so the large-company backing that justified many original adoptions no longer exists
- Enterprise pricing is entirely unpublished, and the only free option is explicitly a prototyping sandbox whose limits can change at any time, so there is no supported low-cost entry point
- Self-hosting Conductor OSS in production means operating the engine plus its persistence and indexing dependencies, typically Postgres or Cassandra with Elasticsearch, which is a substantial platform commitment
- JSON workflow definitions are language agnostic but verbose and awkward to test, and teams accustomed to defining workflows in code find them a step backwards in developer experience
- Orkes is a small company whose commercial future is tied to a single open source project it also maintains, which concentrates both vendor and project risk in the same place
Ozone API
- It provides the API layer, not the core connectivity, so the bulk of the project is still integrating your own core banking systems and that cost is not in the licence
- Value is driven by regulatory obligation, so an institution not under a mandate struggles to build a business case for the spend
- It is a small UK vendor selling to large regulated institutions, which raises procurement and vendor viability questions during bank due diligence
- Premium API monetisation is a genuine capability but few banks have found real demand, so revenue projections used to justify the purchase often do not materialise
- Standards evolve continuously and each revision means a change programme in your own systems, even where Ozone absorbs the specification work at the API edge
How much do Orkes and Ozone API cost?
Orkes is free to use; Ozone API is priced on request. Plan by plan below, from each vendor's own pricing page.
Orkes
Free- Developer EditionFree
- All Conductor OSS features plus enterprise capabilities
- Sandbox for prototyping only
- Rate limits and resources may change without notice
- EnterpriseOn request
- Availability SLA up to 99.99%
- Orkes-hosted or customer-hosted deployment
- Dedicated technical account manager
Ozone API
On request- Ozone APIOn request
- Annual licence or managed service subscription, quoted
- Scaling by institution size, standards in scope and API call volume
- Implementation and core integration charged separately
Which should you pick?
Choose Orkes if
- You need json workflow definitions.
- You want to start without paying.
- You work on Linux, Self-hosted, Web.
- You also want polyglot workers.
Choose Ozone API if
- You need multi-standard support.
- You work on Web, API, Linux.
- You also want consent management.
Questions people ask
- Is Orkes or Ozone API better?
- Neither clearly leads. Orkes starts at Free and Ozone API at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Orkes or Ozone API?
- Orkes has a free tier; the other does not. Paid plans start at Free for Orkes and On request for Ozone API.
- Does Orkes or Ozone API run on more platforms?
- Orkes runs on Linux, Self-hosted, Web. Ozone API runs on Web, API, Linux.
- Can I use Orkes for free?
- Yes. Orkes has a free tier, so you can try it without paying. Ozone API starts at On request.
- What is Orkes best used for?
- Orkes is most often used for a microservices estate that needs orchestration across services written in different languages without a shared sdk, a team already running conductor oss that wants a supported distribution now that netflix has stopped maintaining it, an ai platform composing agent steps, model calls and vector lookups as versioned workflow definitions, a business process needing human approval steps interleaved with automated service calls. Of those, a microservices estate that needs orchestration across services written in different languages without a shared sdk and a team already running conductor oss that wants a supported distribution now that netflix has stopped maintaining it are not what Ozone API is typically brought in for.
- What can Orkes do that Ozone API cannot?
- Orkes covers JSON workflow definitions, Polyglot workers, Visual workflow builder, AI and LLM tasks. Ozone API covers Multi-standard support, Consent management, Developer portal, Regulatory reporting.
Answered from the vendors’ own pages
Orkes: Does Netflix still maintain Conductor?
No. Netflix archived its repository in December 2023. The open source project continues at conductor-oss under Apache 2.0, maintained by Orkes.
Ozone API: Is this a competitor to Plaid or TrueLayer?
No, the opposite side. Ozone is bought by the bank exposing data; Plaid and TrueLayer consume it on behalf of third parties.
Orkes: Is there a free production tier?
No. The Developer Edition is a sandbox that the vendor states is unsuitable for production. Self-hosting Conductor OSS is the free production route.
Ozone API: Does it connect to my core banking system?
It provides the standards-compliant API surface and adapters, but connecting your core is an integration project you scope separately.
Orkes: What does Enterprise cost?
Nothing is published; it is quoted by deployment and support requirements.
Ozone API: Which standards does it support?
UK Open Banking, Berlin Group, FDX, Consumer Data Right and Gulf regional standards, among others, from one platform.
Orkes: How does it compare with Temporal?
Conductor uses declarative JSON workflow definitions and external workers; Temporal defines workflows in code. Temporal has the larger community.
Related pages
Other head to heads
- Orkes vs Camunda
- Orkes vs Temporal
- Orkes vs n8n
- Orkes vs Inngest
- Orkes vs Hatchet
- Orkes vs Autonoly
- Orkes vs Meltano
- Orkes vs Flowable
- Orkes vs Nango
- Orkes vs Airbyte
- Orkes vs Windmill
- Orkes vs jBPM
- Orkes vs Census
- Orkes vs Cyclr
- Orkes vs Flowise
- Orkes vs IBM MQ
- Orkes vs Talend
- Orkes vs Alloy Automation
- Orkes vs TrueLayer
- Orkes vs Enable Banking
- Orkes vs Salt Edge
- Orkes vs Token.io
- Orkes vs Temenos Transact
- Orkes vs MX Technologies
- Orkes vs Tink
- Orkes vs Akoya
- Orkes vs Sensedia
- Orkes vs Tribe Payments
- Orkes vs Bud Financial
- Orkes vs Synctera
- Orkes vs Trustly
- Orkes vs WSO2 API Manager
- Orkes vs Brite Payments
- Orkes vs Dwolla
- Orkes vs Liveblocks
- Orkes vs Parse Server
- Ozone API vs Camunda
- Ozone API vs Temporal
- Ozone API vs n8n
- Ozone API vs Inngest
- Ozone API vs Hatchet
- Ozone API vs Autonoly
- Ozone API vs Meltano
- Ozone API vs Flowable
- Ozone API vs Nango
- Ozone API vs Airbyte
- Ozone API vs Windmill
- Ozone API vs jBPM
- Ozone API vs Census
- Ozone API vs Cyclr
- Ozone API vs Flowise
- Ozone API vs IBM MQ
- Ozone API vs Talend
- Ozone API vs Alloy Automation
- Ozone API vs TrueLayer
- Ozone API vs Enable Banking
- Ozone API vs Salt Edge
- Ozone API vs Token.io
- Ozone API vs Temenos Transact
- Ozone API vs MX Technologies
- Ozone API vs Tink
- Ozone API vs Akoya
- Ozone API vs Sensedia
- Ozone API vs Tribe Payments
- Ozone API vs Bud Financial
- Ozone API vs Synctera
- Ozone API vs Trustly
- Ozone API vs WSO2 API Manager
- Ozone API vs Brite Payments
- Ozone API vs Dwolla
- Ozone API vs Liveblocks
- Ozone API vs Parse Server
