Atarim
Post-V5 releases are spent making the AI agency actually usable rather than adding to it.
A side-by-side editorial comparison of Bonsai and Leantime — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Bonsai | Leantime |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | crm, notes, email-sync, api | project-management, self-hosted, api, permissions |
| Last editorial update | 5h ago | 1mo 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.
Leantime is stabilizing its big 3.9 rewrite while extending cross-project planning and a mobile API
Leantime is deep in a modernization cycle. The 3.9.0 release rebuilt the app around a native, fail-closed permission engine, a JSON-RPC API, and a consolidated Blueprints domain; the releases since then mostly stabilize that foundation. Recent point releases fix regressions (repeated Bearer/PAT auth fixes) while adding cross-project program views and a mobile app backend.
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.
Leantime is deep in a modernization cycle. The 3.9.0 release rebuilt the app around a native, fail-closed permission engine, a JSON-RPC API, and a consolidated Blueprints domain; the releases since then mostly stabilize that foundation. Recent point releases fix regressions (repeated Bearer/PAT auth fixes) while adding cross-project program views and a mobile app backend.
The work is consolidation over expansion: hardening the new auth/permission and API layers, closing security IDORs domain by domain, and building the surface a mobile app and program-level planning need. The steady stream of small patch releases reflects shaking out regressions from the 3.9.0 refactor rather than opening new product directions.
Expect continued point releases fixing regressions from the permission-engine and JSON-RPC migration, plus buildout of the Leantime Mobile app now that its Bearer-authenticated backend API is landing.
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 Leantime.
Post-V5 releases are spent making the AI agency actually usable rather than adding to it.
Hostaway is becoming a compliance and finance system that happens to manage channels
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.
See all Bonsai alternatives → · See all Leantime alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — api — within PM. Leantime 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. Leantime 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 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 Leantime alternatives in PM are ranked by recent ship velocity. Browse the "Leantime alternatives" section above for the current picks, or visit /alternatives/leantime for the full list with editorial commentary on each.