Tracecat
Tracecat 1.2.0 goes stable in under two days: sub-cases, workflow forms and on-prem tunnels.
A side-by-side editorial comparison of Avaza and Productboard — 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.
Productboard v2 adds exact-match text filters as the data model keeps widening.
Productboard's v2 API spent the summer closing v1 parity gaps, then in September made entity types an open, workspace-specific string. Since then the data model has kept widening: rich text accepts tables and checklists, relationships hold their own field values, and as of October 15 entity search supports exact-match filtering on text fields.
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.
Productboard's v2 API spent the summer closing v1 parity gaps, then in September made entity types an open, workspace-specific string. Since then the data model has kept widening: rich text accepts tables and checklists, relationships hold their own field values, and as of October 15 entity search supports exact-match filtering on text fields.
With parity mostly done, v2 is extending the data model and making it queryable. Workspace-defined entity types and relationship fields push schema decisions into each workspace's configuration, and filter operators like eq let integrations match records precisely instead of scanning with contains.
Expect filtering and search to reach relationship fields next, following the pattern of new data shapes gaining query operators a few weeks later. Whether the beta customer score endpoint leaves beta isn't signalled by the 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 Productboard.
Tracecat 1.2.0 goes stable in under two days: sub-cases, workflow forms and on-prem tunnels.
Float is moving from who's-free scheduling toward staffing on experience and pricing on rate cards.
SmartSuite's dashboard filters learn to exclude, as admin undo reaches deleted teams.
RentRedi opens tenant chats to teammates, part of a run of fixes for landlords with staff.
Hive makes its AI proofer a named approver and lets workflow buttons open prefilled Forms.
NocoBase's 2.x line keeps shipping fixes while the agent stack runs in betas.
See all Avaza alternatives → · See all Productboard 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 Productboard 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 Productboard 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 Productboard alternatives in PM are ranked by recent ship velocity. Browse the "Productboard alternatives" section above for the current picks, or visit /alternatives/productboard for the full list with editorial commentary on each.