[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3jjfgxv4unqc9":3},{"code":4,"message":5,"data":6,"timestamp":36},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":26,"homepage":27,"updated_at":28,"history":29},"flowable\u002Fflowable-engine",15,"A compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users.","Java",9620,2900,4,3663,[],"A Java BPM engine for teams that need to run BPMN processes, CMMN cases and DMN rules inside their own applications.","Flowable Engine is worth a look if your team already owns the surrounding application and wants an embeddable process engine rather than a hosted workflow product. It is a mature Java codebase with a commercial host behind it and a long public history; the README is thin on operational detail, so expect to read the docs before committing.\n\n## The problem\n\nA team needs to model an approval chain, an onboarding flow or a claims process and track every open case and decision as it moves. The usual path is hand-rolled state tables, status enums and transition checks, then discovering that audit history, retries and rule evaluation were never designed in. With Flowable, the process definition becomes a BPMN or CMMN model the engine executes, and state lives in the engine's own tables. Rules scattered through Java code can become DMN decision tables, so the shift is from custom persistence code to a model plus API calls.\n\n## What's different\n\nFlowable bundles three engines rather than one: BPMN for processes, CMMN for less structured case work, and DMN for decision tables. That matters when one workflow mixes a fixed sequence with an open-ended case and a policy lookup, because they share a runtime and API. The README states it can run embedded in a Java application, as a server, in a cluster or in the cloud, and that it integrates with Spring. The rich Java and REST APIs are the real surface; the engine is meant to be orchestrated by your code, not to replace it.\n\nThe trade-off is that it is a library and service, not an app you log into. You choose how to embed or deploy it, wire it to your data, and keep schemas and engine versions current. The README lists no default operator console, and the free Flowable Cloud Design app is for modelling, not for running processes. That is fine for a backend team, but it pushes UI, auth and monitoring decisions onto you.\n\n## Who should try it\n\nGood fit: a Java\u002FSpring team with an existing application that needs a process engine callable from existing services, REST access for other clients, and process definitions versioned alongside code. It also suits organisations standardising on BPMN and DMN rather than a JSON DSL and wanting CMMN for work without a fixed path.\n\nPoor fit: a small team wanting a ready-made workflow UI with built-in forms and dashboards, or a non-Java stack unwilling to adopt a JVM service just for orchestration. If the workflow is a handful of status columns, a full engine costs more to learn and operate than it saves. Flowable Design is free to use for modelling but does not remove the need to run an engine.\n\n## Requirements and limitations\n\nFlowable V7 needs JDK 17 or newer; the README says V6 is still maintained for Java 8+. On embedding, the README advertises Spring integration and a REST API but gives no detail on database setup, cluster coordination or upgrading an existing process schema. The deployment model and the database you supply will drive much of the operating burden; check the project page and forum for specifics before adopting. The README also gives no performance numbers and no migration guidance between major versions. Because workflow state is persistent, long-running instances and versioning are ongoing concerns, not one-off setup tasks.\n\n## HotRepo's take\n\nHotRepo tracked only 2026-10-24 and 2026-10-25, recording 9,619 stars with gains of +5 and +4; the sample is too short and incomplete to judge whether interest is growing or fading. What it supports is a large existing codebase, not a trend. Before adopting, verify engine setup and migration guidance in the [project instructions](https:\u002F\u002Fgithub.com\u002Fflowable\u002Fflowable-engine\u002Fblob\u002Fmain\u002FREADME.md) and [docs](https:\u002F\u002Fwww.flowable.org\u002F).",{"slug":19,"name":20},"developer-tools","Developer Tools",[22,23,24,25],"bpmn","java","workflow","workflow-engine","Apache-2.0","https:\u002F\u002Fwww.flowable.org","2026-10-25T03:21:13Z",[30,34],{"date":31,"stars":32,"stars_gained":33},"2026-10-24",9619,5,{"date":35,"stars":11,"stars_gained":13},"2026-10-25",1792906119]