Softwr

Automation Integration · head to head

Flowable vs Valkey

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
Valkey logo

Valkey

Databases

Open-source in-memory data store forked from Redis

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.; Valkey younger project, so its track record is short even though the codebase is not
  • They diverge on capability: Flowable covers BPMN 2.0 engine, Valkey covers Redis-compatible.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Flowable and Valkey actually diverge.

Attributes where Flowable and Valkey differ
AttributeFlowableValkey
Pricing modelquoteOpen source, no licence fee; managed cloud billed separately
PlatformsLinux, Windows, Docker, Kubernetes, CloudLinux, macOS, Docker, Self-hosted
CategoryAutomation IntegrationDatabases

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 Valkey

  • Redis-compatible
  • BSD licensed
  • Rich data structures
  • Replication and persistence

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 Valkey
  • A bank embedding process orchestration inside an existing Spring Boot estate rather than buying a separate platformnot Valkey
  • A team leaving Activiti or jBPM that wants the same API family with active commercial maintenancenot Valkey
  • A regulated organisation needing complete process history and decision table audit trails for supervisorsnot Valkey

Valkey

  • Continuing on a permissively licensed in-memory store after the Redis licence changenot Flowable
  • Caching and session storage where a foundation-governed project is a procurement requirementnot Flowable
  • Migrating from Redis without rewriting application codenot 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.

Valkey

  • Younger project, so its track record is short even though the codebase is not
  • Divergence from Redis grows over time, so compatibility is strongest near the fork point and weakens as both evolve
  • Ecosystem tooling and documentation still frequently assume Redis, leaving translation work

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

Valkey

Free
  • ValkeyFree
    • Full functionality
    • Self-hosted
    • No usage limits

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

  • You need redis-compatible.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Self-hosted.
  • You also want bsd licensed.
Valkey review

Questions people ask

Is Flowable or Valkey better?
Neither clearly leads. Flowable starts at Free and Valkey at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Flowable or Valkey?
Flowable starts at Free and Valkey at Free.
Does Flowable or Valkey run on more platforms?
Flowable runs on Linux, Windows, Docker, Kubernetes, Cloud. Valkey runs on Linux, macOS, Docker, Self-hosted.
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 Valkey is typically brought in for.
What can Flowable do that Valkey cannot?
Flowable covers BPMN 2.0 engine, CMMN case management, DMN decision tables, Spring Boot integration. Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence.

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.

Valkey: Is Valkey free?

Yes, BSD-licensed open source under the Linux Foundation.

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.

Valkey: Why does Valkey exist?

Redis changed its licence away from BSD in 2024. Valkey is the community fork continuing under permissive terms, backed by AWS, Google Cloud and Oracle among others.

Flowable: What does Flowable Enterprise cost?

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

Valkey: Can I switch from Redis to Valkey?

At the fork point it is drop-in compatible with existing clients and data. The further both projects move from that point, the more you should verify the specific features you use.

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.

Share

Related pages

More on Flowable

More on Valkey

Keep looking

Other head to heads