Celoxis
Celoxis publishes buyer-guide SEO two or three times a day and product news almost never.
A side-by-side editorial comparison of Grocy and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
Grocy opened a plugin seam for barcode lookups, then went quiet for a year.
Grocy releases on a slow, maintainer-paced rhythm — a handful of releases across 2024 and 2025, then a single 4.6.0 in March 2026 that makes PHP 8.5 with SQLite 3.40+ the only supported runtime. The functional work concentrates on stock handling: quantity-unit defaults that stay editable until a product has been in stock, automatic 1:1 unit conversions when no default applies, and a long tail of filter and validation fixes across the stock, shopping list and master data pages.
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
Wakapi's recent releases cluster around identity and deployment rather than time tracking itself: OpenID Connect login, then an OIDC-only mode, multiple API keys per user, and a switch from Alpine to a distroless nonroot container image. The 2.17.x line has carried two security fixes now — a responsibly disclosed issue in 2.17.3, and a critical authentication bypass in 2.17.6 caused by a shared cache key namespace. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.
Grocy releases on a slow, maintainer-paced rhythm — a handful of releases across 2024 and 2025, then a single 4.6.0 in March 2026 that makes PHP 8.5 with SQLite 3.40+ the only supported runtime. The functional work concentrates on stock handling: quantity-unit defaults that stay editable until a product has been in stock, automatic 1:1 unit conversions when no default applies, and a long tail of filter and validation fixes across the stock, shopping list and master data pages.
The notable structural move was 4.4.0, which introduced external barcode lookup as a product-picker workflow with a pluggable backend and shipped an Open Food Facts plugin on by default. That converted Grocy from a purely self-contained ledger into something that pulls product data from the outside world, and the releases since have mostly been refining that plugin — localized names, empty-name handling, image URLs with query parameters. Beyond it, the direction is consolidation: fewer rough edges, a tighter supported runtime, no expansion of scope.
Expect continued single-release years focused on stock and quantity-unit correctness. The barcode plugin interface is the one place where new capability could arrive without new maintainer surface, so additional lookup providers are the most plausible next addition.
Wakapi's recent releases cluster around identity and deployment rather than time tracking itself: OpenID Connect login, then an OIDC-only mode, multiple API keys per user, and a switch from Alpine to a distroless nonroot container image. The 2.17.x line has carried two security fixes now — a responsibly disclosed issue in 2.17.3, and a critical authentication bypass in 2.17.6 caused by a shared cache key namespace. Release notes are mostly bare issue numbers, so several entries state that something changed without saying what.
The direction is a self-hosted tool making itself deployable somewhere other than one developer's server. External identity providers, an option to disable local login entirely, per-key credentials and a container that runs as a nonroot user are the requirements that come from someone else's security review. The 2.17.6 bypass sits awkwardly against that: a cache keyed without proper namespacing is exactly the class of bug that multi-tenant deployment surfaces, which suggests the auth work is now being exercised harder than the code was written for. Releases have also thinned to roughly one a month from a much faster earlier cadence.
The identity and packaging thread is the only sustained one in this feed, so further hardening in that area is the most likely continuation; the sparse release notes make anything more specific guesswork.
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 Grocy or Wakapi.
Celoxis publishes buyer-guide SEO two or three times a day and product news almost never.
Process Street's public feed is an SEO content engine, not a changelog.
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
See all Grocy alternatives → · See all Wakapi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within PM. Wakapi is currently shipping more aggressively (velocity 2.5 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. Wakapi is currently shipping more aggressively (velocity 2.5 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 Grocy alternatives in PM are ranked by recent ship velocity. Browse the "Grocy alternatives" section above for the current picks, or visit /alternatives/grocy for the full list with editorial commentary on each.
Top Wakapi alternatives in PM are ranked by recent ship velocity. Browse the "Wakapi alternatives" section above for the current picks, or visit /alternatives/wakapi for the full list with editorial commentary on each.