Softwr

Automation Integration · head to head

Flowable vs Rowy

Flowable logo

Flowable

Automation Integration

Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti

From
Free
Rated
-
Full reviewWebsite
Rowy logo

Rowy

Spreadsheets

Spreadsheet interface for Google Cloud Firestore with cloud functions written in the browser

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Flowable the open source engine is genuinely usable but ships without the modelling studio, work application and admin console, so an open source deployment means building your own user interfaces before anyone can use it.; 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: Flowable 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 Flowable and Rowy actually diverge.

Attributes where Flowable and Rowy differ
AttributeFlowableRowy
Pricing modelquoteOpen source, no licence fee
PlatformsLinux, Windows, Docker, Kubernetes, CloudWeb
CategoryAutomation IntegrationSpreadsheets

Identical on both: starting price (Free), 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 Flowable

  • BPMN 2.0 engine
  • CMMN case management
  • DMN decision tables
  • Spring Boot integration
  • Modelling studio
  • Task and case application
  • REST APIs
  • History and audit

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.

Flowable

  • An insurer automating claims handling where each case follows a different path and BPMN alone cannot express itnot Rowy
  • A bank embedding process orchestration inside an existing Spring Boot estate rather than buying a separate platformnot Rowy
  • A team leaving Activiti or jBPM that wants the same API family with active commercial maintenancenot Rowy
  • A regulated organisation needing complete process history and decision table audit trails for supervisorsnot Rowy

Rowy

  • A Firebase application that needs an internal admin interface without building onenot Flowable
  • Operations staff correcting production records in Firestore without developer involvementnot Flowable
  • Attaching a small transformation or notification function to a field change without a full deployment pipelinenot Flowable
  • A content team populating documents that a mobile application reads directly from Firestorenot Flowable

Where each one falls short

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

Flowable

  • The open source engine is genuinely usable but ships without the modelling studio, work application and admin console, so an open source deployment means building your own user interfaces before anyone can use it.
  • It expects Java engineering capacity; teams looking for a business-user low-code automation tool will find the modelling and deployment cycle far too technical.
  • Enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives.
  • The Activiti fork left three engines with related APIs and overlapping documentation in circulation, and search results routinely return advice for the wrong one.
  • Flowable AG is a small Swiss company relative to its competitors, so the partner network, training market and pool of engineers with production experience are all limited outside Europe.

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

Flowable

Free
  • Flowable Open SourceFree
    • Apache 2.0 licensed BPMN, CMMN and DMN engines
    • Embeddable Java library or standalone apps
    • No modelling studio or enterprise applications
  • Flowable Enterprise$undefined/year
    • Modelling studio, work application and admin console
    • Connectors, forms and advanced identity management
    • Support with SLA and version maintenance

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

  • You need bpmn 2.0 engine.
  • You want to start without paying.
  • You work on Linux, Windows, Docker, Kubernetes, Cloud.
  • You also want cmmn case management.
Flowable review

Choose Rowy if

  • You need firestore backed grid.
  • You want to start without paying.
  • You also want browser authored cloud functions.
Rowy review

Questions people ask

Is Flowable or Rowy better?
Neither clearly leads. Flowable 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, Flowable or Rowy?
Flowable starts at Free and Rowy at Free.
Does Flowable or Rowy run on more platforms?
Flowable runs on Linux, Windows, Docker, Kubernetes, Cloud. Rowy runs on Web.
Can I use Flowable for free?
Both have a free tier, so you can try either at no cost before committing.
What is Flowable best used for?
Flowable is most often used for an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it, a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform, a team leaving activiti or jbpm that wants the same api family with active commercial maintenance, a regulated organisation needing complete process history and decision table audit trails for supervisors. Of those, an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it and a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform are not what Rowy is typically brought in for.
What can Flowable do that Rowy cannot?
Flowable covers BPMN 2.0 engine, CMMN case management, DMN decision tables, Spring Boot integration. Rowy covers Firestore backed grid, Browser authored cloud functions, Typed columns, Runs in your Google Cloud project.

Answered from the vendors’ own pages

Flowable: Is Flowable open source?

Yes, the BPMN, CMMN and DMN engines are Apache 2.0. The modelling studio and enterprise applications are commercial.

Rowy: Where is my data stored?

In your own Firestore instance inside your own Google Cloud project. Rowy does not hold a copy.

Flowable: How does it relate to Activiti and jBPM?

The same core developers built jBPM, then Activiti, then forked Activiti in 2016 to create Flowable.

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.

Flowable: What does Flowable Enterprise cost?

Nothing is published. It is quoted per deployment by the vendor.

Rowy: Can it do joins across collections?

Not really. Firestore does not support joins, and no interface layer can add them.

Flowable: Why choose it over Camunda?

CMMN case management is a first-class engine, which matters when work is exception-driven rather than a fixed sequence.

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.

Share

Related pages

More on Flowable

More on Rowy

Keep looking

Other head to heads