Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Flowable and NocoBase — release velocity, themes, recent moves, and the top alternatives to consider.
Flowable ships once a year and spends it on the Java platform, not on the process engine.
Flowable's release history is a slow major-version cadence — 7.0.0 in 2023, 7.1.0 in 2024, 7.2.0 in 2025, 8.0.0 in February 2026 — and each major is anchored to a Java-ecosystem jump rather than to process modelling itself. Flowable 8 moves to Spring Framework 7 and Spring Boot 4, makes Jackson 3 the default, and removes JUnit 3 and JUnit 4 support outright. The engine-level additions that do arrive, like lambda expressions in expressions, are incremental extensions to BPMN and CMMN semantics.
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
NocoBase is shipping a v3.0.0 alpha train alongside maintenance on the 2.2.0 beta line. The newest alpha adds an online AI documentation assistant that cites verified official docs, DeepSeek V4 Flash and V4 Pro through the Responses API with reasoning continuity, native web search and citations, LDAP user synchronisation for the v2 client, and debounced search in the multi-space switchers. Everything else is the v2 client grind - filter forms, export and import, kanban, approval workflows, map blocks - plus renewable lease support in both the local and Redis lock managers.
Flowable's release history is a slow major-version cadence — 7.0.0 in 2023, 7.1.0 in 2024, 7.2.0 in 2025, 8.0.0 in February 2026 — and each major is anchored to a Java-ecosystem jump rather than to process modelling itself. Flowable 8 moves to Spring Framework 7 and Spring Boot 4, makes Jackson 3 the default, and removes JUnit 3 and JUnit 4 support outright. The engine-level additions that do arrive, like lambda expressions in expressions, are incremental extensions to BPMN and CMMN semantics.
This is a project whose roadmap is largely set by the platform underneath it. Each major forces a coordinated upgrade on adopters — Java 17 and Jakarta 9 at 7.0.0, Spring Boot 4 and Jackson 3 at 8.0.0 — and in exchange delivers query, variable and migration refinements aimed at large existing deployments. The 7.0.0 decision to drop the UI applications and the content, form and Mule modules set the pattern: narrow to the engines and the REST APIs, and let everything else go.
Expect the next major to track the following Spring and Java LTS jump on roughly the same annual rhythm. Nothing in these entries points to an AI or agent-facing direction, so any such move would be a genuine departure rather than a continuation.
NocoBase is shipping a v3.0.0 alpha train alongside maintenance on the 2.2.0 beta line. The newest alpha adds an online AI documentation assistant that cites verified official docs, DeepSeek V4 Flash and V4 Pro through the Responses API with reasoning continuity, native web search and citations, LDAP user synchronisation for the v2 client, and debounced search in the multi-space switchers. Everything else is the v2 client grind - filter forms, export and import, kanban, approval workflows, map blocks - plus renewable lease support in both the local and Redis lock managers.
The alpha line is doing two jobs simultaneously: porting the entire block and action catalogue to the v2 client, and layering AI employees on top of the plugin model that alpha.7 established. The model work has settled into a pattern of adding providers to an existing surface rather than reshaping it - DeepSeek here, skills-as-plugins earlier - which suggests the extensibility question is considered answered and the remaining risk is the client port. Bug volume weighted heavily toward client-v2 confirms where the effort sits.
Expect the alphas to keep trading feature additions for v2 client parity until the port closes, with AI work continuing as provider and tooling breadth rather than another structural change.
Other PM products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Flowable or NocoBase.
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
Process Street's public feed is an SEO content engine, not a changelog.
Hive ships in batches, and this one is all planning accuracy and admin control.
Plane ships a fortnightly digest, and the AI layer is where the real work is going.
Ever Teams shipped ten tags in twelve hours and one of them touched the product
Asana's agent left the app — it now answers work questions inside Slack threads.
See all Flowable alternatives → · See all NocoBase alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NocoBase is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NocoBase is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top Flowable alternatives in PM are ranked by recent ship velocity. Browse the "Flowable alternatives" section above for the current picks, or visit /alternatives/flowable for the full list with editorial commentary on each.
Top NocoBase alternatives in PM are ranked by recent ship velocity. Browse the "NocoBase alternatives" section above for the current picks, or visit /alternatives/nocobase for the full list with editorial commentary on each.