APIs · head to head
Highnote vs Orkes

Highnote
APIs
Card issuing, acquiring and ledger on one platform for embedded payments
- From
- On request
- Free plan
- No

Orkes
Automation Integration
Commercial Conductor, now the maintainer of the workflow engine Netflix archived
- From
- Free
- Free plan
- Yes
The short version
- Orkes is free; Highnote prices on request.
- Only Highnote lists card issuing; only Orkes lists JSON workflow definitions.
- Prices and features on this page were last checked on 20 November 2026.
How do Highnote and Orkes differ?
Highnote and Orkes differ on starting price (On request against Free), free tier (No against Yes) and platforms. Only the attributes on which Highnote and Orkes actually diverge.
Identical on both: pricing model (Quote).
Which features does each one have?
They share no listed features; 8 appear only for Highnote and 8 only for Orkes. 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 Highnote
- Card issuing
- Merchant acquiring
- Unified ledger
- Spend controls
- GraphQL API
- Programme management
- Dispute handling
- Real time authorisation webhooks
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
What is each one used for?
The jobs each tool is most often brought in to do.
Highnote
- A marketplace that both pays out to sellers and issues them spend cards, wanting one settlement ledgernot Orkes
- A vertical software company embedding card acceptance and card issuing for the same customer basenot Orkes
- A fintech launching a commercial charge card programme with custom authorisation logicnot Orkes
- A platform replacing separate issuing and acquiring vendors to remove cross system reconciliationnot Orkes
Orkes
- A microservices estate that needs orchestration across services written in different languages without a shared SDKnot Highnote
- A team already running Conductor OSS that wants a supported distribution now that Netflix has stopped maintaining itnot Highnote
- An AI platform composing agent steps, model calls and vector lookups as versioned workflow definitionsnot Highnote
- A business process needing human approval steps interleaved with automated service callsnot Highnote
Where do Highnote and Orkes fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Highnote
- Card issuing requires a sponsor bank, and that bank sets programme approval, compliance obligations and often minimum volumes, so a small programme can be rejected regardless of technical fit
- Pricing is entirely quoted, including platform fees, per active card charges and monthly minimums that do not appear on the website, so the true cost per card is only visible late in a sales process
- Interchange sharing is the real revenue model for most customers, and the split is negotiated, capped for regulated debit under the Durbin amendment and sensitive to your spend mix, so revenue projections built on headline interchange rates overstate income
- Running issuing and acquiring with one provider concentrates risk: an outage or a compliance action affects both money in and money out at the same time
- Highnote is a younger company than the established issuer processors, so long term programme continuity, network certifications in new geographies and international coverage are thinner than the incumbent alternatives
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
How much do Highnote and Orkes cost?
Highnote is priced on request; Orkes is free to use. Plan by plan below, from each vendor's own pricing page.
Highnote
On request- Highnote platformOn request
- Quoted per programme with no public rate card
- Requires a sponsor bank relationship for card issuing
- Interchange sharing terms negotiated per programme
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
Which should you pick?
Choose Highnote if
- You need card issuing.
- You work on Web, API.
- You also want merchant acquiring.
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.
Questions people ask
- Is Highnote or Orkes better?
- Neither clearly leads. Highnote starts at On request and Orkes at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Highnote or Orkes?
- Orkes has a free tier; the other does not. Paid plans start at On request for Highnote and Free for Orkes.
- Does Highnote or Orkes run on more platforms?
- Highnote runs on Web, API. Orkes runs on Linux, Self-hosted, Web.
- Can I use Orkes for free?
- Yes. Orkes has a free tier, so you can try it without paying. Highnote starts at On request.
- What is Highnote best used for?
- Highnote is most often used for a marketplace that both pays out to sellers and issues them spend cards, wanting one settlement ledger, a vertical software company embedding card acceptance and card issuing for the same customer base, a fintech launching a commercial charge card programme with custom authorisation logic, a platform replacing separate issuing and acquiring vendors to remove cross system reconciliation. Of those, a marketplace that both pays out to sellers and issues them spend cards, wanting one settlement ledger and a vertical software company embedding card acceptance and card issuing for the same customer base are not what Orkes is typically brought in for.
- What can Highnote do that Orkes cannot?
- Highnote covers Card issuing, Merchant acquiring, Unified ledger, Spend controls. Orkes covers JSON workflow definitions, Polyglot workers, Visual workflow builder, AI and LLM tasks.
Answered from the vendors’ own pages
Highnote: Do I need a sponsor bank?
Yes for card issuing in the United States. Highnote is a processor and programme platform, not a bank, and the sponsor bank sets approval and compliance terms.
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.
Highnote: How do customers make money on a card programme?
Mostly interchange sharing. Negotiate the split explicitly and model it against your actual spend mix, since regulated debit interchange is capped.
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.
Highnote: Can Highnote handle both accepting and issuing payments?
Yes since its 2025 acquiring launch, on the same ledger, which is its main structural differentiator.
Orkes: What does Enterprise cost?
Nothing is published; it is quoted by deployment and support requirements.
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
- Highnote vs Marqeta
- Highnote vs Lithic
- Highnote vs Enfuce
- Highnote vs Paymentology
- Highnote vs Episode Six
- Highnote vs Toqio
- Highnote vs i2c
- Highnote vs Thredd
- Highnote vs Unit
- Highnote vs Synctera
- Highnote vs Weavr
- Highnote vs Tribe Payments
- Highnote vs Strapi
- Highnote vs Thunder Client
- Highnote vs Akoya
- Highnote vs Convoy
- Highnote vs Enable Banking
- Highnote vs Fintecture
- Highnote vs Camunda
- Highnote vs Temporal
- Highnote vs n8n
- Highnote vs Inngest
- Highnote vs Hatchet
- Highnote vs Autonoly
- Highnote vs Meltano
- Highnote vs Flowable
- Highnote vs Nango
- Highnote vs Airbyte
- Highnote vs Windmill
- Highnote vs jBPM
- Highnote vs Census
- Highnote vs Cyclr
- Highnote vs Flowise
- Highnote vs IBM MQ
- Highnote vs Talend
- Highnote vs Alloy Automation
- Orkes vs Marqeta
- Orkes vs Lithic
- Orkes vs Enfuce
- Orkes vs Paymentology
- Orkes vs Episode Six
- Orkes vs Toqio
- Orkes vs i2c
- Orkes vs Thredd
- Orkes vs Unit
- Orkes vs Synctera
- Orkes vs Weavr
- Orkes vs Tribe Payments
- Orkes vs Strapi
- Orkes vs Thunder Client
- Orkes vs Akoya
- Orkes vs Convoy
- Orkes vs Enable Banking
- Orkes vs Fintecture
- 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
