Automation Integration · head to head
Activiti vs Split

Activiti
Automation Integration
Apache 2.0 BPMN engine under Hyland, from which Flowable and Camunda were forked
- From
- Free
- Free plan
- Yes

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
- Activiti is free; Split prices on request.
- Only Activiti lists Activiti Cloud; only Split lists feature flags with targeting.
- Prices and features on this page were last checked on 20 November 2026.
How do Activiti and Split differ?
Activiti and Split differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which Activiti and Split actually diverge.
Not yet recorded: founded for Split.
Which features does each one have?
They share no listed features; 6 appear only for Activiti 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 Activiti
- BPMN 2.0 engine
- Activiti Cloud
- Modeler
- Java and REST APIs
- Pluggable persistence
- Identity integration
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.
Activiti
- An Alfresco or Hyland content services deployment where Activiti is already the embedded workflow enginenot Split
- A Java application that needs to embed a BPMN engine as a library under a permissive licencenot Split
- An organisation that has ruled out Camunda 8 on licence grounds and needs an Apache 2.0 alternativenot Split
- Document-centric approval workflows where the process engine sits inside the content management stack rather than beside itnot Split
Split
- A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Activiti
- Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Activiti
- Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Activiti
- A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Activiti
Where do Activiti and Split fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Activiti
- The last stable release was 8.2.0 in January 2024, and while release candidate builds continue, a two-year gap between stable versions is a real risk signal for a production dependency
- Both Camunda and Flowable forked away and took large parts of the contributor base with them, so the community, tutorials and third-party tooling around Activiti are much thinner than around either fork
- Commercial support is only realistically available by buying Hyland Alfresco subscriptions, so there is no way to pay for Activiti support on its own
- Activiti Cloud imposes a distributed architecture of several Spring Boot services plus Keycloak, which is heavy for teams who simply wanted an embeddable engine
- Documentation is dated and partly split between old Alfresco sites and Hyland Connect, and the transition between Activiti 6, 7 and 8 architectures makes much of the older material actively misleading
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 Activiti and Split cost?
Activiti is free to use; Split is priced on request. Plan by plan below, from each vendor's own pricing page.
Activiti
Free- ActivitiFree
- Apache 2.0 licence
- Embeddable Java library or Activiti Cloud services
- No usage limits
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 Activiti if
- You need bpmn 2.0 engine.
- You want to start without paying.
- You work on Linux, Windows, Self-hosted.
- You also want activiti cloud.
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 Activiti or Split better?
- Neither clearly leads. Activiti starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Activiti or Split?
- Activiti has a free tier; the other does not. Paid plans start at Free for Activiti and On request for Split.
- Does Activiti or Split run on more platforms?
- Activiti runs on Linux, Windows, Self-hosted. Split runs on Web, API, iOS, Android, Windows.
- Can I use Activiti for free?
- Yes. Activiti has a free tier, so you can try it without paying. Split starts at On request.
- What is Activiti best used for?
- Activiti is most often used for an alfresco or hyland content services deployment where activiti is already the embedded workflow engine, a java application that needs to embed a bpmn engine as a library under a permissive licence, an organisation that has ruled out camunda 8 on licence grounds and needs an apache 2.0 alternative, document-centric approval workflows where the process engine sits inside the content management stack rather than beside it. Of those, an alfresco or hyland content services deployment where activiti is already the embedded workflow engine and a java application that needs to embed a bpmn engine as a library under a permissive licence are not what Split is typically brought in for.
- What can Activiti do that Split cannot?
- Activiti covers BPMN 2.0 engine, Activiti Cloud, Modeler, Java and REST APIs. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.
Answered from the vendors’ own pages
Activiti: Is Activiti still maintained?
Yes, Hyland continues to publish builds, but the last stable release was 8.2.0 in January 2024.
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.
Activiti: What is its relationship to Camunda and Flowable?
Both are forks of Activiti: Camunda in 2013 and Flowable in 2016, when core developers left Alfresco.
Split: Can I buy just feature flags?
Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.
Activiti: What licence is it?
Apache 2.0, which distinguishes it from Camunda 8’s source-available licence.
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.
Activiti: Should I choose Activiti for a new project?
Only if the Apache licence or an existing Alfresco deployment is decisive. Flowable and Camunda have far larger ecosystems.
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
- Activiti vs Flowable
- Activiti vs jBPM
- Activiti vs Camunda
- Activiti vs n8n
- Activiti vs Temporal
- Activiti vs Nango
- Activiti vs Kogito
- Activiti vs Airbyte
- Activiti vs Meltano
- Activiti vs Windmill
- Activiti vs Zapier
- Activiti vs Microsoft Power Automate
- Activiti vs Inngest
- Activiti vs Boomi
- Activiti vs Dagster
- Activiti vs Nintex
- Activiti vs Dify
- Activiti vs Hevo Data
- Activiti vs GrowthBook
- Activiti vs Kameleoon
- Activiti vs Eppo
- Activiti vs Katalon
- Activiti vs Selenium
- Activiti vs Sauce Labs
- Activiti vs TestRail
- Activiti vs Applitools
- Activiti vs CloudBees Smart Tests
- Activiti vs QA Wolf
- Activiti vs CircleCI
- Activiti vs BrowserStack
- Activiti vs BugHerd
- Activiti vs SoapUI
- Activiti vs Playwright
- Activiti vs GitHub Actions
- Activiti vs Cypress
- Activiti vs Appium
- Split vs Flowable
- Split vs jBPM
- Split vs Camunda
- Split vs n8n
- Split vs Temporal
- Split vs Nango
- Split vs Kogito
- Split vs Airbyte
- Split vs Meltano
- Split vs Windmill
- Split vs Zapier
- Split vs Microsoft Power Automate
- Split vs Inngest
- Split vs Boomi
- Split vs Dagster
- Split vs Nintex
- Split vs Dify
- Split vs Hevo Data
- 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
