Wakapi
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
A side-by-side editorial comparison of Bonsai and Ever Teams — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Bonsai | Ever Teams |
|---|---|---|
| Sector | PM | PM |
| Velocity score | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | crm, notes, email-sync, api | team-management, ci-cd, release-automation, performance |
| Last editorial update | 7d ago | 18h 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.
Ever Teams shipped ten tags in twelve hours and one of them touched the product
The window is ten releases published between 01:06 and 12:54 on a single day, and nine of them are continuous-integration work: runners migrated to self-hosted ARC, dead ubicloud labels replaced, the DigitalOcean deploy gated behind a flag, actions bumped to Node 24, a desktop cache bounded after it grew to 9.5 GB. The one product change is v0.133.58, which drops four unread relations from the team-wide daily-plan fetch. Several tags carry no changelog at all beyond a compare link.
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.
The window is ten releases published between 01:06 and 12:54 on a single day, and nine of them are continuous-integration work: runners migrated to self-hosted ARC, dead ubicloud labels replaced, the DigitalOcean deploy gated behind a flag, actions bumped to Node 24, a desktop cache bounded after it grew to 9.5 GB. The one product change is v0.133.58, which drops four unread relations from the team-wide daily-plan fetch. Several tags carry no changelog at all beyond a compare link.
The release train is fully automated and fires on every merge, so tag count says nothing about progress here — the same CI changelog is restated verbatim across multiple tags minutes apart. What work is visible points at build infrastructure being rebuilt around self-hosted runners rather than at the application.
Until the runner migration settles, expect the tag stream to stay dominated by CI commits, with product changes appearing as occasional query-cost fixes like the daily-plan one.
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 Ever Teams.
A critical auth bypass lands in the middle of Wakapi's slow identity rebuild.
Process Street's public feed is an SEO content engine, not a changelog.
NocoBase runs two release lines at once while the v3 client rewrite absorbs the AI work
Hive ships in batches, and this one is all planning accuracy and admin control.
Plane ships a fortnightly digest, and the AI layer is where the real work is going.
Asana's agent left the app — it now answers work questions inside Slack threads.
See all Bonsai alternatives → · See all Ever Teams alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Bonsai and Ever Teams are shipping at a similar cadence (velocity 5.0 vs 5.0, 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. Bonsai and Ever Teams are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 Ever Teams alternatives in PM are ranked by recent ship velocity. Browse the "Ever Teams alternatives" section above for the current picks, or visit /alternatives/ever-teams for the full list with editorial commentary on each.