Tracecat
Tracecat's 1.3 alphas keep reworking agent plumbing: tunnels, multi-org MCP, pluggable runners.
A side-by-side editorial comparison of Avaza and Camunda — 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.
Camunda opens the 8.11 cycle with job-worker fixes and variable metadata across gRPC, REST and MCP.
Camunda's feed is mostly release plumbing: 8.10 patch candidates, Optimize CVE patches, and dry-run tags. Today's two 8.11.0-alpha1 candidates are the first real content in weeks. They fix job-worker streaming bugs that dropped or stalled work and a batch-cancel bug that could cancel every running root instance in a cluster.
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.
Camunda's feed is mostly release plumbing: 8.10 patch candidates, Optimize CVE patches, and dry-run tags. Today's two 8.11.0-alpha1 candidates are the first real content in weeks. They fix job-worker streaming bugs that dropped or stalled work and a batch-cancel bug that could cancel every running root instance in a cluster.
8.11 is leaning toward operational hardening for managed and multi-region setups: cluster secrets, an upgrade-completeness API, per-index shard config, and Oracle Data Guard lag monitoring. The variablesMetadata work lands on the MCP surface at the same time as gRPC and REST, so MCP is being treated as a first-class API rather than an add-on.
Expect more 8.11 alpha candidates on a near-daily cadence, alongside continued 8.10.x patch tags. Whether 8.11 has a headline feature is not yet visible in these notes.
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 Camunda.
Tracecat's 1.3 alphas keep reworking agent plumbing: tunnels, multi-org MCP, pluggable runners.
NocoBase's Runner Agent gets conversation management, task links and agent switching mid-thread.
Todoist's 2026 bets are on capture: voice via Ramble, photos and files via Task Capture.
Atarim's AI experts now propose changes to live pages as drafts, and the app runs on phones.
Fibery's MCP server can now upload local files, so AI assistants can attach screenshots and images.
SmartSuite adds a scheduled JavaScript runtime with secrets and run history.
See all Avaza alternatives → · See all Camunda alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within PM. Avaza is currently shipping more aggressively (velocity 6.3 vs 5.0), 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. Avaza is currently shipping more aggressively (velocity 6.3 vs 5.0), 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 Camunda alternatives in PM are ranked by recent ship velocity. Browse the "Camunda alternatives" section above for the current picks, or visit /alternatives/camunda for the full list with editorial commentary on each.