Celoxis
Celoxis publishes buyer-guide SEO two or three times a day and product news almost never.
A side-by-side editorial comparison of Productboard and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
Productboard is methodically making its customer-insight data programmable through a v2 API build-out.
Productboard's public activity is a steady stream of v2 REST API additions. The recent window closes v1 parity gaps (fulltext note search, team and note-type filters, custom-field filtering with an isSet presence check, source metadata for CRM matching) and adds net-new surface — a beta endpoint returning an aggregated customer score for any product-hierarchy entity. The work is developer-platform, not end-user UI.
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.
Productboard's public activity is a steady stream of v2 REST API additions. The recent window closes v1 parity gaps (fulltext note search, team and note-type filters, custom-field filtering with an isSet presence check, source metadata for CRM matching) and adds net-new surface — a beta endpoint returning an aggregated customer score for any product-hierarchy entity. The work is developer-platform, not end-user UI.
The throughline is making Productboard's prioritization and customer-insight data fully queryable and integrable via API. Reaching and exceeding v1 parity, then exposing scoring data, points toward Productboard positioning its data as a programmable layer other systems build on, not just a UI to visit. This deepens an integration strategy rather than changing product direction.
Expect continued v2 endpoint expansion toward eventual v1 deprecation, with more prioritization and scoring signals exposed for CRM, analytics, and internal tooling integrations.
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 Productboard 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 Productboard alternatives → · See all Wakapi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Productboard is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. Productboard is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Productboard alternatives in PM are ranked by recent ship velocity. Browse the "Productboard alternatives" section above for the current picks, or visit /alternatives/productboard 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.