Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Avaza and Tracecat — release velocity, themes, recent moves, and the top alternatives to consider.
Avaza ships an MCP server, opening its professional-services suite to AI clients
Avaza is moving on two fronts: a notable strategic push — an MCP server that exposes projects, time-tracking, and billing data to AI clients — and steady product improvements (custom project statuses, a rebuilt subtask model with assignees and time tracking). Educational content reinforces the professional-services positioning around capacity, risk, and resource planning.
Tracecat is turning case comments into an agent console while it hardens the sandbox around them
Tracecat is deep in a beta.52 release-candidate train, eight RCs in, following the beta.51 release that made the Action Gateway mandatory. Two threads dominate: agents are becoming addressable from inside case comments, and the sandbox that runs them is being bounded — socket budgets, registry artifact caches, egress filtering. The product is a security automation platform steadily converting its agent story from a feature into the primary interaction surface.
Avaza is moving on two fronts: a notable strategic push — an MCP server that exposes projects, time-tracking, and billing data to AI clients — and steady product improvements (custom project statuses, a rebuilt subtask model with assignees and time tracking). Educational content reinforces the professional-services positioning around capacity, risk, and resource planning.
Avaza is positioning itself to become the system AI agents read from and write to when a professional-services workflow needs context — quotes, billable hours, project status. The MCP server is the infrastructure for that bet; the subtask rebuild and status customization narrow the gap with heavier-weight project management tools. Cadence is moderate, but the MCP move is unusual for an SMB-focused vendor.
Expect use-case content showing the MCP server driving Claude or ChatGPT workflows around timesheet entry, invoice drafting, and project status updates. Further automation surfaces (webhooks, agentic billing) are likely follow-ons given the MCP foundation.
Tracecat is deep in a beta.52 release-candidate train, eight RCs in, following the beta.51 release that made the Action Gateway mandatory. Two threads dominate: agents are becoming addressable from inside case comments, and the sandbox that runs them is being bounded — socket budgets, registry artifact caches, egress filtering. The product is a security automation platform steadily converting its agent story from a feature into the primary interaction surface.
The agent work is moving from 'you can invoke an agent' to 'the agent lives in the case thread' — mentions, session chat, activity shown inline, and now MCP integration references correlated on workspace pull. Running alongside it is a sustained isolation effort: every second RC raises or filters the NSTUN socket budget, which reads as capacity being tuned under real agent load rather than a one-off fix. The UI is catching up too, with a properties rail and editor redesign borrowed from Linear's density.
Expect beta.52 to land as a final release with agent-in-comments as its headline, and the NSTUN capacity raises to stop once the ceiling holds. Whether the MCP reference correlation grows into full workspace-level integration mapping is not yet visible in these entries.
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 Avaza or Tracecat.
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
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 Avaza alternatives → · See all Tracecat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within PM. Tracecat is currently shipping more aggressively (velocity 7.5 vs 6.3), 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. Tracecat is currently shipping more aggressively (velocity 7.5 vs 6.3), 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 Avaza alternatives in PM are ranked by recent ship velocity. Browse the "Avaza alternatives" section above for the current picks, or visit /alternatives/avaza for the full list with editorial commentary on each.
Top Tracecat alternatives in PM are ranked by recent ship velocity. Browse the "Tracecat alternatives" section above for the current picks, or visit /alternatives/tracecat for the full list with editorial commentary on each.