Tracecat
Tracecat 1.0 stable lands with workspace entitlements, SSRF hardening, and an open-source MCP skills catalog
A side-by-side editorial comparison of Wakapi and Rize — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Wakapi | Rize |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 2.5 | 8.8 |
| Sparks · 30d | 0 | 2 |
| Top themes | time-tracking, self-hosted, oidc, auth-bypass | time-tracking, agencies, invoicing, team-management |
| Last editorial update | 28d ago | 4d ago |
| Website | Visit → | — |
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.
Rize pivots from solo time tracker to agency operations platform with invoicing, profitability reporting, and a ChatGPT integration.
Rize has made a deliberate category jump: the August 27 release cluster — profitability by client and project, resourcing and utilization planning, invoicing from tracked time, and team permissions — repositions the product from a productivity tool for individual knowledge workers to a full operations layer for agencies and consulting firms. The organizational primitives added in September (titles, departments, tracking schedules, member settings) are scaffolding for larger teams adopting the new suite. The official ChatGPT partnership adds a distribution surface that bypasses the Rize app itself.
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.
Rize has made a deliberate category jump: the August 27 release cluster — profitability by client and project, resourcing and utilization planning, invoicing from tracked time, and team permissions — repositions the product from a productivity tool for individual knowledge workers to a full operations layer for agencies and consulting firms. The organizational primitives added in September (titles, departments, tracking schedules, member settings) are scaffolding for larger teams adopting the new suite. The official ChatGPT partnership adds a distribution surface that bypasses the Rize app itself.
Rize is assembling the full billing cycle for service firms: track time automatically, generate invoices from that time, record payments, and report margin by client and project — all without manual timesheets. Embedding in ChatGPT via the @Rize integration signals that Rize sees conversational access as a long-term interface, not just a feature. The 'available in the Agent, API, and MCP' note on the agencies launch suggests the data layer is being designed for AI consumption as much as human dashboards.
Direct payment collection (Stripe or similar) is the natural next step to close the invoicing loop. Budget vs. actuals tracking and project margin alerts would extend the FP&A layer that profitability reporting has started.
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 Wakapi or Rize.
Tracecat 1.0 stable lands with workspace entitlements, SSRF hardening, and an open-source MCP skills catalog
NocoBase adds an AI knowledge base retrieval API, connecting no-code workflows to external knowledge sources.
RentRedi embeds AI into its maintenance workflow end-to-end, handling tenant intake and drafting landlord replies.
Camunda 8.10 alpha cycles through broad platform bug fixes while 8.7 gets routine security patches
Asana embeds AI into Slack threads and closes the rich-text gap with Notion
Hive is building shared AI automation infrastructure into the core of its PM platform.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — time-tracking — within PM. Rize is currently shipping more aggressively (velocity 8.8 vs 2.5), with 2 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. Rize is currently shipping more aggressively (velocity 8.8 vs 2.5), with 2 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 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.
Top Rize alternatives in PM are ranked by recent ship velocity. Browse the "Rize alternatives" section above for the current picks, or visit /alternatives/rize for the full list with editorial commentary on each.