Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Avaza and OpenProject — 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.
OpenProject settles into patch work after 17.7 shipped resource management.
17.7.0 was the substantial release — a resource management module with departments and work schedules, pushing OpenProject past task tracking into staffing. The two releases since are patches. 17.7.2 fixes four bugs, among them project-level hourly rates that could not be adjusted and non-working days silently dropped when saved while a reschedule job was running — both in the scheduling and cost areas 17.7 had just expanded.
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.
17.7.0 was the substantial release — a resource management module with departments and work schedules, pushing OpenProject past task tracking into staffing. The two releases since are patches. 17.7.2 fixes four bugs, among them project-level hourly rates that could not be adjusted and non-working days silently dropped when saved while a reschedule job was running — both in the scheduling and cost areas 17.7 had just expanded.
The release rhythm is a feature minor followed by a short tail of patches repairing the surface it just added, and this tail sits squarely in resource-management territory. Rate and non-working-day bugs are the predictable cost of shipping scheduling and cost tracking together. For self-hosted operators the advice does not change between these releases: take the patch.
Expect one or two more 17.7.x patches against the resource management surface before 17.8 opens a new feature line.
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 OpenProject.
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 OpenProject alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Avaza and OpenProject are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. Avaza and OpenProject are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 OpenProject alternatives in PM are ranked by recent ship velocity. Browse the "OpenProject alternatives" section above for the current picks, or visit /alternatives/openproject for the full list with editorial commentary on each.