Softwr

Smart Home · head to head

ESPHome vs Flowable

ESPHome logo

ESPHome

Smart Home

Custom firmware for ESP8266/ESP32 smart home devices

From
Free
Rated
-
Full reviewWebsite
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

The short version

  • Each has a real cost: ESPHome eSPHome runs only on supported microcontrollers; the project recommends ESP32, ESP32-S3, ESP32-C3 and ESP32-C6 and advises against ESP8266 for new projects; 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.
  • They diverge on capability: ESPHome covers YAML Configuration, Flowable covers BPMN 2.0 engine.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which ESPHome and Flowable actually diverge.

Attributes where ESPHome and Flowable differ
AttributeESPHomeFlowable
Pricing modelopen-sourcequote
PlatformsESP8266, ESP32, Docker, Raspberry PiLinux, Windows, Docker, Kubernetes, Cloud
CategorySmart HomeAutomation Integration
Founded2018Unknown

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 ESPHome

  • YAML Configuration
  • OTA Updates
  • Home Assistant Native
  • Custom Components
  • Home Assistant
  • MQTT
  • API
  • Native integration

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

What people use each for

The jobs each tool is most often brought in to do.

ESPHome

  • Building custom smart home sensors and switches on ESP32 hardwarenot Flowable
  • Replacing vendor cloud firmware on ESP based devices with locally controlled firmwarenot Flowable
  • Integrating DIY devices into Home Assistant over a native API or MQTTnot Flowable

Flowable

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

Where each one falls short

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

ESPHome

  • ESPHome runs only on supported microcontrollers; the project recommends ESP32, ESP32-S3, ESP32-C3 and ESP32-C6 and advises against ESP8266 for new projects
  • Support for ESP32-H2, RP2040 and other newer chips is documented as less mature
  • Large displays and some sensors do not work well on ESP8266 because of its limited RAM, which is roughly a fifth of an ESP32

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.

Pricing, plan by plan

ESPHome

Free
  • CommunityFree
    • Full firmware
    • Home Assistant integration
    • Custom sensors

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

Which should you pick?

Choose ESPHome if

  • You need yaml configuration.
  • You want to start without paying.
  • You work on ESP8266, ESP32, Docker, Raspberry Pi.
  • You also want ota updates.
ESPHome review

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

Questions people ask

Is ESPHome or Flowable better?
Neither clearly leads. ESPHome starts at Free and Flowable at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, ESPHome or Flowable?
ESPHome starts at Free and Flowable at Free.
Does ESPHome or Flowable run on more platforms?
ESPHome runs on ESP8266, ESP32, Docker, Raspberry Pi. Flowable runs on Linux, Windows, Docker, Kubernetes, Cloud.
Can I use ESPHome for free?
Both have a free tier, so you can try either at no cost before committing.
What is ESPHome best used for?
ESPHome is most often used for building custom smart home sensors and switches on esp32 hardware, replacing vendor cloud firmware on esp based devices with locally controlled firmware, integrating diy devices into home assistant over a native api or mqtt. Of those, building custom smart home sensors and switches on esp32 hardware and replacing vendor cloud firmware on esp based devices with locally controlled firmware are not what Flowable is typically brought in for.
What can ESPHome do that Flowable cannot?
ESPHome covers YAML Configuration, OTA Updates, Home Assistant Native, Custom Components. Flowable covers BPMN 2.0 engine, CMMN case management, DMN decision tables, Spring Boot integration.

Answered from the vendors’ own pages

ESPHome: Is ESPHome free to use?

Yes. ESPHome is free and open-source software. The Desktop App, Device Builder, components, and recipe tools are all available at no cost.

Source
Flowable: Is Flowable open source?

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

ESPHome: What is the cost to run ESPHome?

ESPHome software itself is completely free. Hardware devices and components used with ESPHome vary in cost depending on which microcontrollers and IoT devices you choose.

Source
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.

ESPHome: Does ESPHome require a subscription or license fee?

No. ESPHome is open-source software with no subscription fees, license costs, or commercial restrictions associated with its use.

Source
Flowable: What does Flowable Enterprise cost?

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

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 ESPHome

More on Flowable

Keep looking

Other head to heads