Process Street
Process Street's public feed is an SEO content engine, not a changelog.
A side-by-side editorial comparison of Scoro and Wakapi — release velocity, themes, recent moves, and the top alternatives to consider.
Scoro is making itself agent-readable: AI assistant for everyone, MCP server, app platform.
Three releases in close succession define where Scoro is investing: an MCP server for AI-powered cross-app workflows, the ELI AI assistant rolled out to all users, and a New Apps by Scoro layer announced in May 2026. The fundamentals — subtasks, role assignment on tasks, time-and-cost-to-invoice allocation, financial reports — are still shipping in parallel.
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.
Three releases in close succession define where Scoro is investing: an MCP server for AI-powered cross-app workflows, the ELI AI assistant rolled out to all users, and a New Apps by Scoro layer announced in May 2026. The fundamentals — subtasks, role assignment on tasks, time-and-cost-to-invoice allocation, financial reports — are still shipping in parallel.
Scoro is positioning itself to be operated by both humans and agents over the same data model. MCP plus a public ELI assistant plus an apps layer is a deliberate platform move, not feature scatter. The classic project-management roadmap (subtasks, time tracking, financial reporting) continues underneath as table stakes.
Expect deeper integrations between ELI and the new Apps layer next, plus more granular MCP tool surfaces (timesheet, invoicing, quoting). A marketplace or partner-built apps story is the obvious follow-on if New Apps by Scoro is going to mean anything beyond first-party.
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 Scoro or Wakapi.
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
Asana's agent left the app — it now answers work questions inside Slack threads.
See all Scoro alternatives → · See all Wakapi alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — time-tracking — within PM. Scoro and Wakapi are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). 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. Scoro and Wakapi are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top Scoro alternatives in PM are ranked by recent ship velocity. Browse the "Scoro alternatives" section above for the current picks, or visit /alternatives/scoro 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.