Automation Integration · head to head
Camunda vs Split

Camunda
Automation Integration
BPMN process orchestration engine, now source-available rather than open source
- From
- On request
- Free plan
- No

Split
Testing
Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME
- From
- On request
- Free plan
- No
The short version
- Only Camunda lists BPMN 2.0 execution; only Split lists feature flags with targeting.
- Prices and features on this page were last checked on 20 November 2026.
How do Camunda and Split differ?
Camunda and Split differ on platforms and category. Only the attributes on which Camunda and Split actually diverge.
Identical on both: starting price (On request), pricing model (Quote), free tier (No).
Not yet recorded: founded for Split.
Which features does each one have?
They share no listed features; 6 appear only for Camunda and 8 only for Split. 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 Split
- Feature flags with targeting
- Metrics impact engine
- Guardrail metrics
- Statistical significance testing
- Event ingestion
- SDKs and streaming updates
- Audit and approvals
- Harness platform integration
What is each one used for?
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 Split
- Insurance claims or loan origination where the process model is itself a compliance artefactnot Split
- Replacing orchestration logic scattered across microservices with one engine that owns the state machinenot Split
- A regulated organisation that needs an auditable record of how each process instance actually executednot Split
Split
- A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Camunda
- Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Camunda
- Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Camunda
- A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Camunda
Where do Camunda and Split 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
Split
- Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
- Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
- The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
- Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
- As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product
How much do Camunda and Split cost?
Camunda is priced on request; Split 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
Split
On request- Harness FreeFree
- Harness Open Source and community support
- Intended for individuals and small teams
- Feature management capability limited at this tier
- Harness EssentialsOn request
- Bundled DevOps modules including CI, CD, IaC and security testing
- Standard support
- Pricing requires contacting sales
- Harness EnterpriseOn request
- Mix and match from 15 or more modules including Feature Management and Experimentation
- Premier support with a dedicated account manager
- Higher pipeline concurrency and organisation limits
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 Split if
- You need feature flags with targeting.
- You work on Web, API, iOS, Android, Windows.
- You also want metrics impact engine.
Questions people ask
- Is Camunda or Split better?
- Neither clearly leads. Camunda starts at On request and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Camunda or Split?
- Camunda starts at On request and Split at On request.
- Does Camunda or Split run on more platforms?
- Camunda runs on Web, Linux, Self-hosted. Split runs on Web, API, iOS, Android, Windows.
- 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 Split is typically brought in for.
- What can Camunda do that Split cannot?
- Camunda covers BPMN 2.0 execution, DMN decision tables, Zeebe engine, Operate console. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.
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.
Split: Is Split still called Split?
It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.
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.
Split: Can I buy just feature flags?
Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.
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.
Split: What does it do that a plain flag service does not?
It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.
Camunda: What does it cost?
Camunda does not publish prices. Both self-managed production and SaaS require a quote.
Split: Do we need a lot of traffic?
Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.
Related pages
Other head to heads
- Camunda vs Flowable
- Camunda vs Activiti
- Camunda vs Kogito
- Camunda vs jBPM
- Camunda vs n8n
- Camunda vs Orkes
- Camunda vs Temporal
- Camunda vs UiPath
- Camunda vs Parabola
- Camunda vs Blue Prism
- Camunda vs Zapier
- Camunda vs Microsoft Power Automate
- Camunda vs Nango
- Camunda vs Paragon
- Camunda vs Prefect
- Camunda vs Automation Anywhere
- Camunda vs CrewAI
- Camunda vs Lytics
- Camunda vs GrowthBook
- Camunda vs Kameleoon
- Camunda vs Eppo
- Camunda vs Katalon
- Camunda vs Selenium
- Camunda vs Sauce Labs
- Camunda vs TestRail
- Camunda vs Applitools
- Camunda vs CloudBees Smart Tests
- Camunda vs QA Wolf
- Camunda vs CircleCI
- Camunda vs BrowserStack
- Camunda vs BugHerd
- Camunda vs SoapUI
- Camunda vs Playwright
- Camunda vs GitHub Actions
- Camunda vs Cypress
- Camunda vs Appium
- Split vs Flowable
- Split vs Activiti
- Split vs Kogito
- Split vs jBPM
- Split vs n8n
- Split vs Orkes
- Split vs Temporal
- Split vs UiPath
- Split vs Parabola
- Split vs Blue Prism
- Split vs Zapier
- Split vs Microsoft Power Automate
- Split vs Nango
- Split vs Paragon
- Split vs Prefect
- Split vs Automation Anywhere
- Split vs CrewAI
- Split vs Lytics
- Split vs GrowthBook
- Split vs Kameleoon
- Split vs Eppo
- Split vs Katalon
- Split vs Selenium
- Split vs Sauce Labs
- Split vs TestRail
- Split vs Applitools
- Split vs CloudBees Smart Tests
- Split vs QA Wolf
- Split vs CircleCI
- Split vs BrowserStack
- Split vs BugHerd
- Split vs SoapUI
- Split vs Playwright
- Split vs GitHub Actions
- Split vs Cypress
- Split vs Appium
