Grocy
Grocy opened a plugin seam for barcode lookups, then went quiet for a year.
A side-by-side editorial comparison of Flowable and Everhour — 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.
A comparison-content engine where the changelog should be — Everhour ranks itself against rivals.
The feed is entirely search content from Everhour's time-tracking blog: buyer's guides for time tracking, employee management and remote work software, a vertical guide for landscaping crews, an explainer on time theft, and a positioning post framing Everhour as the employee-friendly alternative to automatic tracking. Most posts are competitor roundups that list Everhour among the options. No release notes appear.
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.
The feed is entirely search content from Everhour's time-tracking blog: buyer's guides for time tracking, employee management and remote work software, a vertical guide for landscaping crews, an explainer on time theft, and a positioning post framing Everhour as the employee-friendly alternative to automatic tracking. Most posts are competitor roundups that list Everhour among the options. No release notes appear.
The one durable signal here is positioning, and it is deliberate: while much of the category sells surveillance-style automatic tracking, Everhour repeatedly markets manual, task-based tracking as the employee-friendly choice — and pairs that with a time-theft explainer aimed at the managers who want the opposite. That tension is a marketing strategy, not a product direction. What actually ships is not visible from this source, and the velocity score reflects blog cadence.
More vertical and comparison guides is the safe expectation from this feed. Judging the product's direction requires a release-notes source, which this feed is not.
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 Everhour.
Grocy opened a plugin seam for barcode lookups, then went quiet for a year.
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
Notion is turning Custom Agents into event-driven workers with their own runtime and billing.
See all Flowable alternatives → · See all Everhour alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Everhour 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. Everhour 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 Everhour alternatives in PM are ranked by recent ship velocity. Browse the "Everhour alternatives" section above for the current picks, or visit /alternatives/everhour for the full list with editorial commentary on each.