Automation Integration · head to head
Activiti vs Rowy

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

Rowy
Spreadsheets
Spreadsheet interface for Google Cloud Firestore with cloud functions written in the browser
- From
- Free
- Rated
- -
The short version
- Each has a real cost: 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.; Rowy every Firestore limit is inherited, including the one megabyte per document ceiling and roughly one sustained write per second per document, which surprises users who expect spreadsheet behaviour.
- They diverge on capability: Activiti covers BPMN 2.0 engine, Rowy covers Firestore backed grid.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Activiti and Rowy actually diverge.
Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated).
What each one covers
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 Rowy
- Firestore backed grid
- Browser authored cloud functions
- Typed columns
- Runs in your Google Cloud project
- Role based access
- Form view
- Open source
What people use each 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 Rowy
- A Java application that needs to embed a BPMN engine as a library under a permissive licencenot Rowy
- An organisation that has ruled out Camunda 8 on licence grounds and needs an Apache 2.0 alternativenot Rowy
- Document-centric approval workflows where the process engine sits inside the content management stack rather than beside itnot Rowy
Rowy
- A Firebase application that needs an internal admin interface without building onenot Activiti
- Operations staff correcting production records in Firestore without developer involvementnot Activiti
- Attaching a small transformation or notification function to a field change without a full deployment pipelinenot Activiti
- A content team populating documents that a mobile application reads directly from Firestorenot Activiti
Where each one falls 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.
Rowy
- Every Firestore limit is inherited, including the one megabyte per document ceiling and roughly one sustained write per second per document, which surprises users who expect spreadsheet behaviour.
- Firestore has no joins, so linking tables in the grid is a convenience layer rather than a relational feature and reports across collections still need a separate query.
- It is useful only to teams already on Firebase, so choosing it effectively locks the operational tooling to one cloud vendor.
- Query costs are billed by document read, and an unfiltered grid on a large collection can generate a bill that a spreadsheet user has no intuition for.
- Development activity has slowed relative to the broader category, so evaluate current maintenance before making it load bearing for internal operations.
Pricing, plan by plan
Activiti
Free- ActivitiFree
- Apache 2.0 licence
- Embeddable Java library or Activiti Cloud services
- No usage limits
Rowy
Free- Open source self hostedFree
- No licence fee
- Deploys into your own Google Cloud project
- You pay Google Cloud for Firestore reads, writes and storage
Which should you pick?
Choose Activiti if
- You need bpmn 2.0 engine.
- You want to start without paying.
- You work on Linux, Windows, Docker, Kubernetes.
- You also want activiti cloud.
Choose Rowy if
- You need firestore backed grid.
- You want to start without paying.
- You also want browser authored cloud functions.
Questions people ask
- Is Activiti or Rowy better?
- Neither clearly leads. Activiti starts at Free and Rowy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Activiti or Rowy?
- Activiti starts at Free and Rowy at Free.
- Does Activiti or Rowy run on more platforms?
- Activiti runs on Linux, Windows, Docker, Kubernetes. Rowy runs on Web.
- Can I use Activiti for free?
- Both have a free tier, so you can try either at no cost before committing.
- 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 Rowy is typically brought in for.
- What can Activiti do that Rowy cannot?
- Activiti covers BPMN 2.0 engine, Activiti Cloud, Modeler, Java and REST APIs. Rowy covers Firestore backed grid, Browser authored cloud functions, Typed columns, Runs in your Google Cloud project.
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.
Rowy: Where is my data stored?
In your own Firestore instance inside your own Google Cloud project. Rowy does not hold a copy.
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.
Rowy: What does it cost to run?
No licence fee. You pay Google Cloud for Firestore reads, writes, storage and function invocations, and an open grid on a big collection reads a lot.
Activiti: What licence is it?
Apache 2.0, which distinguishes it from Camunda 8’s source-available licence.
Rowy: Can it do joins across collections?
Not really. Firestore does not support joins, and no interface layer can add them.
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.
Rowy: Is there a row limit?
Not from Rowy. The limits that bite are Firestore document size and per document write throughput.
Rowy: Is it suitable if I am not on Firebase?
No. It is specifically a Firestore interface.
Related pages
Other head to heads
- Activiti vs n8n
- Activiti vs Temporal
- Activiti vs Flowable
- Activiti vs jBPM
- Activiti vs Camunda
- Activiti vs Nango
- Activiti vs Kogito
- Activiti vs Airbyte
- Activiti vs Windmill
- Activiti vs Meltano
- Activiti vs Zapier
- Activiti vs Microsoft Power Automate
- Activiti vs Census
- Activiti vs Decodable
- Activiti vs Dify
- Activiti vs Flowise
- Activiti vs Baserow
- Activiti vs Mathesar
- Activiti vs Budibase
- Activiti vs APITable
- Activiti vs Teable
- Activiti vs Quadratic
- Activiti vs Fibery
- Activiti vs Google Sheets
- Activiti vs Numbers
- Activiti vs Zoho Sheet
- Activiti vs Coefficient
- Activiti vs Sigma Computing
- Activiti vs Equals
- Activiti vs Cube Software
- Rowy vs n8n
- Rowy vs Temporal
- Rowy vs Flowable
- Rowy vs jBPM
- Rowy vs Camunda
- Rowy vs Nango
- Rowy vs Kogito
- Rowy vs Airbyte
- Rowy vs Windmill
- Rowy vs Meltano
- Rowy vs Zapier
- Rowy vs Microsoft Power Automate
- Rowy vs Census
- Rowy vs Decodable
- Rowy vs Dify
- Rowy vs Flowise
- Rowy vs Baserow
- Rowy vs Mathesar
- Rowy vs Budibase
- Rowy vs APITable
- Rowy vs Teable
- Rowy vs Quadratic
- Rowy vs Fibery
- Rowy vs Google Sheets
- Rowy vs Numbers
- Rowy vs Zoho Sheet
- Rowy vs Coefficient
- Rowy vs Sigma Computing
- Rowy vs Equals
- Rowy vs Cube Software
