Process Street
Process Street's public feed is an SEO content engine, not a changelog.
Comparison · PM
Rize vs Wakapi
A side-by-side editorial comparison of Rize and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:time-tracking
Rize vs Wakapi: at a glance
| Feature | Rize | Wakapi |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 7.5 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | agent-toolset, scheduled-automation, mcp, time-tracking | time-tracking, self-hosted, oidc, auth-bypass |
| Last editorial update | 7d ago | 29m ago |
| Website | — | Visit → |
What is Rize?
Rize stops being a time tracker you query and becomes one that runs on a schedule without you.
The August drop lands as one roll-up plus six component entries published together: an Agent tab for live conversation over your Rize data with follow-up actions, Routines that run scheduled prompts and open follow-ups from context, AI Reports that turn prompts and templates into recurring analysis for client profitability and team overviews, Shared AI Skills as reusable saved prompts scoped personal, team or workspace, Agent Context with custom tagging instructions so the agent learns how a team labels clients and projects, and API/MCP surfaces exposing report runs, routine runs, Skills and agent context. Days earlier, v3.0.45 shipped My Timesheet and Team Timesheets with click-and-drag entry editing.
What is Wakapi?
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 vs Wakapi: editorial side-by-side
Rize
7.5PM
Rize stops being a time tracker you query and becomes one that runs on a schedule without you.
◆ Current state
The August drop lands as one roll-up plus six component entries published together: an Agent tab for live conversation over your Rize data with follow-up actions, Routines that run scheduled prompts and open follow-ups from context, AI Reports that turn prompts and templates into recurring analysis for client profitability and team overviews, Shared AI Skills as reusable saved prompts scoped personal, team or workspace, Agent Context with custom tagging instructions so the agent learns how a team labels clients and projects, and API/MCP surfaces exposing report runs, routine runs, Skills and agent context. Days earlier, v3.0.45 shipped My Timesheet and Team Timesheets with click-and-drag entry editing.
◆ Where it's heading
Rize sparked twice this spring on chatting with your time data over MCP; this release is the step from asking to delegating. Routines and scheduled AI Reports mean the analysis happens whether or not anyone opens the app, and Shared Skills plus Agent Context turn one person's prompt into team infrastructure. Exposing routine and report runs through the API and MCP makes the agent layer callable from outside, which is what turns a feature into a platform surface.
◆ Prediction
Expect Routines to gain triggers beyond a schedule — a budget threshold crossed, unlogged time detected — and the timesheet work to be pulled into agent review flows. Invoicing sparked earlier this month, so billing is the obvious destination for a routine that finds unbilled time on its own.
Wakapi
2.5PM
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Rize and Wakapi
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 Rize or Wakapi.
NocoBase
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
Hive
Hive ships in batches, and this one is all planning accuracy and admin control.
Plane
Plane ships a fortnightly digest, and the AI layer is where the real work is going.
Ever Teams
Ever Teams shipped ten tags in twelve hours and one of them touched the product
Asana
Asana's agent left the app — it now answers work questions inside Slack threads.
Recent activity from Rize and Wakapi
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6h agoWakapiCritical auth bypass from a shared cache key namespace
- 8d agoRizeAI Reports
- 8d agoRizeNew Chat and Agent
- 8d agoRizeAugust Update: Introducing the Rize Agent Toolset ⚡
- 8d agoRizeAPI/MCP Improvements
- 8d agoRizeAgent Context and Custom Tagging Instructions
- 8d agoRizeShared AI Skills
- 1mo agoWakapiRelease 2.17.5
- 2mo agoWakapiRelease 2.17.4
- 4mo agoWakapiSecurity fix, relay endpoint dropped, summaries may need regenerating
- 5mo agoWakapiDistroless nonroot container image; SQLite permissions need fixing
- 6mo agoWakapiOIDC-only login mode disables local accounts
Frequently asked questions
What is the difference between Rize and Wakapi?
Both compete on the same themes — time-tracking — within PM. Rize is currently shipping more aggressively (velocity 7.5 vs 2.5), with 1 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.
Is Rize better than Wakapi?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Rize is currently shipping more aggressively (velocity 7.5 vs 2.5), with 1 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.
What are the best alternatives to Rize?
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.
What are the best alternatives to Wakapi?
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.