Tracecat
After a mandatory Action Gateway, the RC train is back to hardening the sandbox
A side-by-side editorial comparison of Bonsai and NocoBase — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Bonsai | NocoBase |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | crm, notes, email-sync, api | no-code, ai-employees, plugins, portals |
| Last editorial update | 1h ago | 14h ago |
| Website | — | Visit → |
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.
NocoBase is building an AI employee layer while running its 2.2 and 3.0 lines in parallel.
NocoBase is shipping two trains at once: v2.2.0 is at beta.17 and v3.0.0 is at alpha.8, with features crossing between them. The work concentrates in three areas — AI employees that draw skills from the plugin system, a Portal manager that defines application entry points, and an AI knowledge base backed by configurable vector databases. Cadence on the alpha line is close to daily.
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.
NocoBase is shipping two trains at once: v2.2.0 is at beta.17 and v3.0.0 is at alpha.8, with features crossing between them. The work concentrates in three areas — AI employees that draw skills from the plugin system, a Portal manager that defines application entry points, and an AI knowledge base backed by configurable vector databases. Cadence on the alpha line is close to daily.
The plugin system is becoming the extension mechanism for agents, not just for the no-code builder: AI employee skills are built from plugins, and a plugin development guide for defining tools, skills and built-in employees shipped alongside them. Portals are turning into first-class application surfaces with their own access checks, AI conversations, unread counts and backup support. Setup that started as CLI-only — LLM services, vector databases — keeps acquiring UI navigation a release or two later.
Expect the AI employee skill system and vector database management to keep filling in, since CLI-driven setup already has UI navigation and model selection guidance just landed. Features appearing first on the 3.0 alpha line and then reaching the 2.2 betas is now the established pattern, so the next 2.2 beta is the place to watch for what 3.0 tested.
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 Bonsai or NocoBase.
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.
Every surface is being rebuilt around agents, and the shareholder letter says it is paying.
See all Bonsai alternatives → · See all NocoBase alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NocoBase is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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. NocoBase is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 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.
Top NocoBase alternatives in PM are ranked by recent ship velocity. Browse the "NocoBase alternatives" section above for the current picks, or visit /alternatives/nocobase for the full list with editorial commentary on each.