Grocy
Grocy opened a plugin seam for barcode lookups, then went quiet for a year.
A side-by-side editorial comparison of Flowable and Atlassian — 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.
In two days Atlassian shipped AI into Trello, opened LLMs to Forge developers, and made Jira dispatch coding agents.
Three substantial releases landed inside 48 hours. Jira Automation can now trigger GitHub Copilot, Cursor or Claude Code as a step in any rule, with conditions deciding when work hands off. The Forge LLMs API went generally available, giving any app developer model access as a platform primitive. Trello got seven AI features at once, extended to every paid user on Standard, Premium and Enterprise. Rovo Search, Chat and Agents can now read documents the user already has access to in Google Drive, SharePoint and OneDrive. The remaining entries are an internal ML engineering write-up and an analyst-report announcement.
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.
Three substantial releases landed inside 48 hours. Jira Automation can now trigger GitHub Copilot, Cursor or Claude Code as a step in any rule, with conditions deciding when work hands off. The Forge LLMs API went generally available, giving any app developer model access as a platform primitive. Trello got seven AI features at once, extended to every paid user on Standard, Premium and Enterprise. Rovo Search, Chat and Agents can now read documents the user already has access to in Google Drive, SharePoint and OneDrive. The remaining entries are an internal ML engineering write-up and an analyst-report announcement.
Atlassian is building the layer beneath other people's agents rather than competing feature-for-feature with them. Automation becomes the dispatcher that decides when a coding agent runs; Forge becomes the place third-party apps get model access without their own inference contracts; Rovo becomes the retrieval surface over documents Atlassian does not host. The Trello release is the consumer-facing counterpart, and shipping it to all paid tiers rather than the top one suggests AI is being treated as table stakes rather than an upsell.
Expect the agent-dispatch pattern to spread from Jira Automation to other Atlassian surfaces, and Rovo's connector set to keep widening to systems Atlassian doesn't own.
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 Atlassian.
Grocy opened a plugin seam for barcode lookups, then went quiet for a year.
A comparison-content engine where the changelog should be — Everhour ranks itself against rivals.
RescueTime publishes essays, not releases — the feed shows no product movement at all.
Workamajig's changelog is a content-marketing blog — buyer-guide listicles, zero product news.
A no-code platform rebuilding itself around AI employees and Portals at once
Process Street's blog buries the actual news: it has an MCP server
See all Flowable alternatives → · See all Atlassian alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Atlassian is currently shipping more aggressively (velocity 10.0 vs 0.0), with 3 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. Atlassian is currently shipping more aggressively (velocity 10.0 vs 0.0), with 3 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 Atlassian alternatives in PM are ranked by recent ship velocity. Browse the "Atlassian alternatives" section above for the current picks, or visit /alternatives/atlassian for the full list with editorial commentary on each.