Twenty
Twenty 2.50 lets app front components read the host route, filling a gap in its app platform.
A side-by-side editorial comparison of ERPNext and Twenty — release velocity, themes, recent moves, and the top alternatives to consider.
Two ERPNext lines ship minutes apart: v16 takes the features, v15 takes the same fixes
ERPNext maintains two release lines in parallel and publishes them within minutes of each other — v16.x carries features, v15.x carries backported fixes, frequently as paired PR numbers for an identical change. The last two weeks delivered an optional customer overdue-limit block on Sales Invoice submission, accounting entries for stock-related expenses, partial Pick List transfers, and a faster data source behind the General Ledger, Trial Balance, Balance Sheet and Profit and Loss reports. The notes are LLM-summarized from commits and say so at the bottom of each release.
Twenty opens 2.50 by giving sandboxed front components the host route.
Twenty ships a minor version roughly weekly with the SDK and CLI tagged in lockstep. 2.48 continued one agent conversation per Slack thread, let the AI chat manage agents, capped an application's credits and supported more than two billing plans. 2.49 carried only a regenerated SDK metadata client, and the first 2.50 tags expose the host location (pathname, search, hash, origin) to front components through useLocation().
ERPNext maintains two release lines in parallel and publishes them within minutes of each other — v16.x carries features, v15.x carries backported fixes, frequently as paired PR numbers for an identical change. The last two weeks delivered an optional customer overdue-limit block on Sales Invoice submission, accounting entries for stock-related expenses, partial Pick List transfers, and a faster data source behind the General Ledger, Trial Balance, Balance Sheet and Profit and Loss reports. The notes are LLM-summarized from commits and say so at the bottom of each release.
No new direction is visible here; this is an ERP working through the long tail of accounting correctness and warehouse edge cases — variant BOM selection, double-counted stock on same-timestamp cancellations, weekly auto-reposting of incorrect valuation entries, a revised country chart of accounts. The pattern worth tracking is the dual-line discipline itself: v15 keeps receiving fixes on the same day v16 receives features, which says the installed base has not moved and the project plans to carry both for some time.
The cadence should hold — a paired v15/v16 drop roughly weekly, features on 16 and fixes mirrored onto 15. Nothing in these entries signals a major-version push or a change in how long v15 will be supported.
Twenty ships a minor version roughly weekly with the SDK and CLI tagged in lockstep. 2.48 continued one agent conversation per Slack thread, let the AI chat manage agents, capped an application's credits and supported more than two billing plans. 2.49 carried only a regenerated SDK metadata client, and the first 2.50 tags expose the host location (pathname, search, hash, origin) to front components through useLocation().
Agents are becoming the organising idea of the product, living in Slack threads and managed from the AI chat. The app platform grows in parallel: a marketplace consent screen, install stats, usage caps, recorded app versions and now route awareness for front components that run in a worker. Each release adds a piece apps need to behave like native parts of the CRM.
Expect more of 2.50 to land through the week, likely more front-component APIs and the second part of the Campaigns work; new billing tiers look likely but their shape isn't visible.
Other CRM 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 ERPNext or Twenty.
Twenty 2.50 lets app front components read the host route, filling a gap in its app platform.
folk's MCP connector can now create and update CRM records in bulk for AI agents.
Close takes Chloe Chat out of beta for every customer, a month after OIDC SSO.
GroupOffice ships a fourth 26.0 build in nine days, still with install-only notes.
Corteza 2026.9.0 goes final after a week of single-fix candidates.
Django CRM spends a morning hardening itself against abusive input.
See all ERPNext alternatives → · See all Twenty alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ERPNext and Twenty 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. ERPNext and Twenty 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 CRM products to evaluate alongside.
Top ERPNext alternatives in CRM are ranked by recent ship velocity. Browse the "ERPNext alternatives" section above for the current picks, or visit /alternatives/erpnext for the full list with editorial commentary on each.
Top Twenty alternatives in CRM are ranked by recent ship velocity. Browse the "Twenty alternatives" section above for the current picks, or visit /alternatives/twenty-crm for the full list with editorial commentary on each.