Softwr

Automation Integration · head to head

Camunda vs Volt

Camunda logo

Camunda

Automation Integration

BPMN process orchestration engine, now source-available rather than open source

From
On request
Free plan
No
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

  • Only Camunda lists BPMN 2.0 execution; only Volt lists pay by bank.
  • Prices and features on this page were last checked on 20 November 2026.

How do Camunda and Volt differ?

Camunda and Volt differ on platforms and category. Only the attributes on which Camunda and Volt actually diverge.

Attributes where Camunda and Volt differ
AttributeCamundaVolt
PlatformsWeb, Linux, Self-hostedWeb, API
CategoryAutomation IntegrationAPIs

Identical on both: starting price (On request), pricing model (Quote), free tier (No).

Not yet recorded: founded for Volt.

Which features does each one have?

They share no listed features; 6 appear only for Camunda 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 Camunda

  • BPMN 2.0 execution
  • DMN decision tables
  • Zeebe engine
  • Operate console
  • Job workers
  • Optimize

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.

Camunda

  • Long-running business processes crossing several services where the state must be visible to non-developersnot Volt
  • Insurance claims or loan origination where the process model is itself a compliance artefactnot Volt
  • Replacing orchestration logic scattered across microservices with one engine that owns the state machinenot Volt
  • A regulated organisation that needs an auditable record of how each process instance actually executednot Volt

Volt

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

Where do Camunda and Volt fall short?

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Camunda

  • Camunda 7 Community Edition stopped receiving security patches after the 7.24 release in October 2025, so free production deployments are now running unpatched software
  • Camunda 8 Self-Managed is source-available under the Camunda License 1.0, not open source: production use requires a paid licence, and organisations that adopted Camunda for its Apache licence have to renegotiate that decision
  • Migrating from Camunda 7 to 8 is a rewrite rather than an upgrade because the engine, the API and the persistence model all changed, and there is no in-place migration for running instances
  • Camunda 8 Self-Managed has substantial infrastructure requirements including Zeebe brokers, Elasticsearch and Identity, which is a considerable operations burden compared with the single database that Camunda 7 needed
  • Pricing is not published at all, so evaluating total cost requires a sales process, and there is no way to size a budget before committing engineering time to a proof of concept

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 Camunda and Volt cost?

Camunda is priced on request; Volt is priced on request. Plan by plan below, from each vendor's own pricing page.

Camunda

On request
  • Camunda 8On request
    • Self-Managed under Camunda License 1.0, production licence required
    • SaaS with a thirty day full trial
    • Free unlimited BPMN and DMN modelling after the trial

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

  • You need bpmn 2.0 execution.
  • You work on Web, Linux, Self-hosted.
  • You also want dmn decision tables.

Choose Volt if

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

Questions people ask

Is Camunda or Volt better?
Neither clearly leads. Camunda starts at On request and Volt at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Camunda or Volt?
Camunda starts at On request and Volt at On request.
Does Camunda or Volt run on more platforms?
Camunda runs on Web, Linux, Self-hosted. Volt runs on Web, API.
What is Camunda best used for?
Camunda is most often used for long-running business processes crossing several services where the state must be visible to non-developers, insurance claims or loan origination where the process model is itself a compliance artefact, replacing orchestration logic scattered across microservices with one engine that owns the state machine, a regulated organisation that needs an auditable record of how each process instance actually executed. Of those, long-running business processes crossing several services where the state must be visible to non-developers and insurance claims or loan origination where the process model is itself a compliance artefact are not what Volt is typically brought in for.
What can Camunda do that Volt cannot?
Camunda covers BPMN 2.0 execution, DMN decision tables, Zeebe engine, Operate console. Volt covers Pay by bank, Circuit Breaker, Virtual IBANs, Payouts and refunds.

Answered from the vendors’ own pages

Camunda: Is Camunda still open source?

No. Camunda 8 Self-Managed ships under the Camunda License 1.0, which is source-available and requires a paid production licence.

Volt: Are there chargebacks?

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

Camunda: What happened to Camunda 7?

Its final feature release, 7.24, was in October 2025 and the Community Edition receives no further patches. Enterprise support runs to April 2030.

Volt: How do refunds work?

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

Camunda: Can I upgrade from 7 to 8?

Not in place. The engine, API and persistence changed, so it is a rewrite of the integration layer.

Volt: Which markets are covered?

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

Camunda: What does it cost?

Camunda does not publish prices. Both self-managed production and SaaS require a quote.

Share

Related pages

Other head to heads