Softwr

Automation Integration · head to head

Orkes vs Volt

Orkes logo

Orkes

Automation Integration

Commercial Conductor, now the maintainer of the workflow engine Netflix archived

From
Free
Free plan
Yes
Volt logo

Volt

APIs

Account-to-account pay by bank across Europe, the UK, Brazil and Australia

From
On request
Free plan
No

The short version

  • Orkes is free; Volt prices on request.
  • Only Orkes lists JSON workflow definitions; only Volt lists pay by bank.
  • Prices and features on this page were last checked on 20 November 2026.

How do Orkes and Volt differ?

Orkes and Volt differ on starting price (Free against On request), free tier (Yes against No) and platforms. Only the attributes on which Orkes and Volt actually diverge.

Attributes where Orkes and Volt differ
AttributeOrkesVolt
Starting priceFreeOn request
Free tierYesNo
PlatformsLinux, Self-hosted, WebWeb, API
CategoryAutomation IntegrationAPIs

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 Volt. 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 Volt

  • Pay by bank
  • Circuit Breaker
  • Virtual IBANs
  • Payouts and refunds
  • Verify
  • Stablecoin checkout

What is each one used for?

Volt is most often brought in for A marketplace verifying seller bank accounts before paying out. 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 Volt
  • A team already running Conductor OSS that wants a supported distribution now that Netflix has stopped maintaining itnot Volt
  • An AI platform composing agent steps, model calls and vector lookups as versioned workflow definitionsnot Volt
  • A business process needing human approval steps interleaved with automated service callsnot Volt

Volt

  • A travel seller with high average order values paying percentage card fees it wants to replace with flat transfer feesnot Orkes
  • An iGaming operator needing fast deposits and payouts where card acceptance is restrictednot Orkes
  • A merchant with heavy card fraud that wants strongly authenticated irreversible paymentsnot Orkes
  • A marketplace verifying seller bank accounts before paying outnot Orkes

Where do Orkes and Volt 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

Volt

  • Account-to-account payments carry no chargeback mechanism, so consumers lose scheme dispute protection and merchants lose a familiar framework for handling claims
  • Refunds are outbound payments rather than reversals, which changes treasury handling and means a refund can fail for reasons a card refund never would
  • Conversion is lower than a stored card because the shopper must complete a bank authentication journey, and drop-off varies significantly by bank
  • Core pay by bank pricing is per transaction but refunds, payouts, virtual IBANs, Verify and fraud tooling are billed separately, so the real cost is a stack of line items
  • Bank API availability and quality vary across markets, and an outage at a major bank removes a slice of your checkout with no fallback unless you keep cards live

How much do Orkes and Volt cost?

Orkes is free to use; Volt 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

Volt

On request
  • Volt pay by bankOn request
    • Per successful transaction fee, quoted by volume and market
    • Separate charges for refunds, payouts, virtual IBANs and Verify
    • Circuit Breaker fraud tooling priced as an add-on

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 Volt if

  • You need pay by bank.
  • You work on Web, API.
  • You also want circuit breaker.

Questions people ask

Is Orkes or Volt better?
Neither clearly leads. Orkes starts at Free and Volt at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Orkes or Volt?
Orkes has a free tier; the other does not. Paid plans start at Free for Orkes and On request for Volt.
Does Orkes or Volt run on more platforms?
Orkes runs on Linux, Self-hosted, Web. Volt runs on Web, API.
Can I use Orkes for free?
Yes. Orkes has a free tier, so you can try it without paying. Volt 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 Volt is typically brought in for.
What can Orkes do that Volt cannot?
Orkes covers JSON workflow definitions, Polyglot workers, Visual workflow builder, AI and LLM tasks. Volt covers Pay by bank, Circuit Breaker, Virtual IBANs, Payouts and refunds.

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.

Volt: Are there chargebacks?

No. Bank transfers are irrevocable, so disputes are handled commercially between merchant and customer, not through a card scheme.

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.

Volt: How do refunds work?

As a separate outbound payment initiated by the merchant, which Volt charges for separately from the inbound transaction.

Orkes: What does Enterprise cost?

Nothing is published; it is quoted by deployment and support requirements.

Volt: Which markets are covered?

Europe and the UK, plus Brazil and Australia, on a single API integration.

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.

Share

Related pages

Other head to heads