Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Flowable and Process Street — 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.
Process Street's public feed is an SEO content engine, not a changelog.
Nothing in this feed reports a product change. It runs a steady daily-ish cadence of evergreen business content — risk management primers, business writing advice, an MBTI personality explainer, a compliance audit walkthrough — interleaved with lead-generation assets built around free Process Playbook checklists and product how-tos like an employee onboarding automation guide. The one item with substance behind it is a customer story on a healthcare practice cutting insurance appeals prep from 15 minutes to under 2, which reads as a compliance-ops proof point rather than a release.
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.
Nothing in this feed reports a product change. It runs a steady daily-ish cadence of evergreen business content — risk management primers, business writing advice, an MBTI personality explainer, a compliance audit walkthrough — interleaved with lead-generation assets built around free Process Playbook checklists and product how-tos like an employee onboarding automation guide. The one item with substance behind it is a customer story on a healthcare practice cutting insurance appeals prep from 15 minutes to under 2, which reads as a compliance-ops proof point rather than a release.
The company positions itself as a compliance operations platform in its own feed signature, and the content is being steered to match: PHI handling, appeals packets, audit readiness, risk assessment and controls now sit alongside the older generic productivity material. Some of that older material is being recirculated rather than retired — a 2021 milestone retrospective carries a current date in this window, so the feed is partly an archive re-dump. Product direction cannot be read here at all.
Expect more compliance and regulated-industry content to displace the generic productivity posts, but this feed will keep carrying no release information, so any actual product movement will have to be observed elsewhere.
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 Process Street.
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
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 Process Street alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Process Street is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. Process Street is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Process Street alternatives in PM are ranked by recent ship velocity. Browse the "Process Street alternatives" section above for the current picks, or visit /alternatives/process-st for the full list with editorial commentary on each.