Tracecat
After a mandatory Action Gateway, the RC train is back to hardening the sandbox
A side-by-side editorial comparison of Atlassian and Bonsai — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Atlassian | Bonsai |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 10.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | agents, rovo-mcp, jira, confluence | crm, notes, email-sync, api |
| Last editorial update | 9h ago | 1h ago |
| Website | Visit → | — |
Every surface is being rebuilt around agents, and the shareholder letter says it is paying.
The Inside Atlassian feed interleaves real product releases with engineering-culture writing, and the release half is now almost entirely agent infrastructure. This window holds a rebuilt Deployments page, agents that can be @mentioned to author directly inside Confluence pages, and those same agents reachable from Claude, Cursor, or an IDE through Rovo MCP. Atlassian puts agent invocations above five million, and the Q4 FY26 shareholder letter names enterprise, AI, and the system of work as its priorities.
Bonsai is assembling a real CRM underneath the freelancer billing tools
Bonsai's recent work is system-of-record plumbing: a Notes section spanning contacts, companies and projects, an activity feed per company, and Gmail/Microsoft sync that files email and calendar events against the right record. Alongside it sit a self-serve API key and an MCP connector. Billing is no longer the centre of gravity.
The Inside Atlassian feed interleaves real product releases with engineering-culture writing, and the release half is now almost entirely agent infrastructure. This window holds a rebuilt Deployments page, agents that can be @mentioned to author directly inside Confluence pages, and those same agents reachable from Claude, Cursor, or an IDE through Rovo MCP. Atlassian puts agent invocations above five million, and the Q4 FY26 shareholder letter names enterprise, AI, and the system of work as its priorities.
One direction runs through a long sequence of releases: agents are moving from a feature inside Atlassian products to a layer that other tools call. MCP is the mechanism, and each release widens either what agents can act on or where they can be invoked from, which means the interesting question is no longer what Rovo can do but how little of it requires an Atlassian tab. The culture posts run alongside and increasingly carry internal measurements — ticket quality, code throughput, translation volume — turning the blog into the evidence base for the same argument.
The next releases most likely extend agent reach into the surfaces that remain and add actions rather than new chat entry points. The shareholder framing suggests enterprise controls and scale figures will keep arriving attached to those launches.
Bonsai's recent work is system-of-record plumbing: a Notes section spanning contacts, companies and projects, an activity feed per company, and Gmail/Microsoft sync that files email and calendar events against the right record. Alongside it sit a self-serve API key and an MCP connector. Billing is no longer the centre of gravity.
The pieces landing are the ones a CRM needs before it can be trusted as the single place client history lives — cross-record linking, per-object permissions, automatic contact capture. The API and MCP connector point the same data outward, reachable from outside the app. Documents was rebuilt on that footing, folding proposals and contracts into one editor.
Expect the per-object permissions introduced with Notes to spread to the other record types, and the API surface to widen now that a key can be generated self-serve.
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 Atlassian or Bonsai.
After a mandatory Action Gateway, the RC train is back to hardening the sandbox
The changelog turned into a how-to blog — capability news now arrives disguised as tutorials.
Governance and cross-workspace plumbing, not new AI surface
Two release lines, weekly tags, and not one line of release notes in the feed.
Elle stops being Aha's assistant and becomes where teams encode their own standards.
Competitor-displacement guides published in threes; the changelog lives somewhere else.
See all Atlassian alternatives → · See all Bonsai alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Atlassian is currently shipping more aggressively (velocity 10.0 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. Atlassian is currently shipping more aggressively (velocity 10.0 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 Atlassian alternatives in PM are ranked by recent ship velocity. Browse the "Atlassian alternatives" section above for the current picks, or visit /alternatives/atlassian for the full list with editorial commentary on each.
Top Bonsai alternatives in PM are ranked by recent ship velocity. Browse the "Bonsai alternatives" section above for the current picks, or visit /alternatives/bonsai for the full list with editorial commentary on each.