Pre-alpha — Flowatch development is ongoing. No compatibility guarantees between pre-1.0 releases. Latest release ›

Open-source GUI for Flowable 7+

Model. Deploy. Operate.
The browser GUI for Flowable 7+ OSS.

Flowatch is a single-page React GUI for Flowable, the open-source BPMN/DMN process engine. It embeds the official bpmn-js and dmn-js modelers, ships every Flowable REST call through a built-in API Inspector, and talks only to the live engine. Apache 2.0. Self-hosted. No telemetry. 

docker pull ghcr.io/syalioune/flowatch:latest
View on GitHub

Why Flowatch exists

Flowatch gives Flowable 7+ OSS users a complete browser GUI: model BPMN and DMN, deploy them, watch instances, work tasks, inspect jobs and history, and manage identity — all without writing a single curl command.

The need is real. Flowable's 7.x OSS distribution ships the engine and REST API; the web UI sits in the enterprise tier. Public-sector teams, SMEs, and air-gapped self-hosters need an OSS browser front-end — and the 2026 OSS landscape has none actively maintained. Most community alternatives are modeler-only POCs.

Flowatch fills that gap. The benchmark is the legacy 6.x OSS UI: if a 6.x-OSS operator used to do it, Flowatch should do it.

What you get

Modeler

Embedded bpmn-js and dmn-js. Load deployed XML, edit, deploy back to the engine via multipart upload.

Admin

Deployments. Process definitions (suspend/activate/view XML). Process instances (start/cancel/variables). Jobs — executable, timer, dead-letter. History.

Identity & Tenants

Users, groups, add-to-group. Multi-tenant cycle in the chrome. Tenants list synthesised from deployments (since /identity/tenants isn't exposed in flowable-rest 7.2).

Not an exhaustive feature list — the goal is parity with the legacy 6.x OSS UI, ten screens at v1.

What makes it different

  1. API Inspector

    Every Flowable REST call your session makes is visible in a side drawer: method, path, status, response time, body. Copy any call as a curl command. Operator-grade transparency, built in by default.

  2. Three-look design system

    editorial · terminal · industrial × light/dark × compact/regular/comfy. Unique across every direct and adjacent competitor. The operator picks once, the whole app respects it.

  3. Flowable-aware

    DMN sub-app URL prefix, missing /identity/tenants, multipart-only deployments, multi-tenant derivation from deployments — all the 7.x REST quirks are baked in so you don't trip over them.

Get started

Run the published image against any reachable Flowable backend — configure the URL in Settings after the SPA loads:

# GitHub Container Registry (no auth needed for public pulls)
docker run --rm -p 8081:8080 ghcr.io/syalioune/flowatch:latest

# Open http://localhost:8081
# In Settings, set baseUrl to your Flowable instance

Don't have a Flowable engine handy? Boot the whole local stack — Postgres + flowable-rest 7.2.0 + nginx + Vite — in one command:

git clone https://github.com/syalioune/flowatch.git
cd flowatch
make stack       # boot-to-Dashboard in under 2 minutes

Default credentials in the local stack: rest-admin / test — change them in Settings (the gear icon). The image runs as non-root (uid 101) on unprivileged port 8080 and drops cleanly into Kubernetes restricted-baseline policies.

What we promise

Project status

Pre-alpha. Flowatch runs against flowable-rest:7.2.0 end-to-end today, and is being put on a defensible engineering footing — TypeScript strict, Vitest + Playwright against a live Dockerized engine, Biome lint+format, TanStack Router, GitHub Actions CI — before adding net-new capabilities. Treat current implementation choices as starting points, not as permanent decisions.

Built openly with AI as a first-class collaborator: every commit is human-reviewed and the maintainer carries the DCO sign-off. The roadmap, architecture, and per-story specs live in a private companion repo; the implementation, docs, and this site are all here on GitHub.

Compatibility matrix Latest release Issue tracker