ERPNext vs Twenty
Side-by-side trajectory, velocity, and editorial themes.
ERPNext's recent tags are mostly bug-fix batches, with only a minor timeout setting as new capability.
The recent feed is dominated by maintenance releases across parallel v15 and v16 branches: v16.26.2, v16.26.1, v16.26.0, and v15.115.0 are large bug-fix rollups covering stock valuation, reconciliation, permission checks, and reporting, with little to no new functionality. v16.25.0 adds a single configurable PCV Job Timeout setting. One entry, "Patch-test v14 baseline" (tag v14-baseline), carries a big feature list but is a staging/test baseline tag rather than a shipped GA release, so the crawler is picking up a non-release tag here.
ERPNext is in a steady dual-branch maintenance rhythm, hardening stock/accounting correctness and tightening access controls, with bug fixes frequently mirrored between v15 and v16. Larger capability work (product bundle versioning, Frappe CRM sync, standard-cost valuation) shows up in the baseline/older feature entries rather than the current top of feed. The near-term signal is stabilization, not new direction.
Expect continued paired v15/v16 patch releases weighted toward stock, accounting, and permission fixes. No pricing or architectural pivot is visible in these entries; the v14-baseline tag should be treated as a crawl-source artifact, not a release.
Twenty is turning its open-source CRM into an AI-native, app-extensible platform.
Twenty is an open-source CRM shipping on a weekly cadence — five tagged releases (v2.15 through v2.19) in about three weeks. The work clusters into three arcs: AI chat and agent tooling that operates on workflows and data, a third-party app SDK with a partner marketplace, and email/calendar sync via webhook push. A credit-and-entitlement billing model is being wired through the product in parallel.
The direction is a programmable CRM platform where third-party apps are first-class, AI agents act on records and workflows, and cloud usage is metered by credits while self-host relies on an enterprise license. Recent releases have moved this from scaffolding toward production hardening — declarative app metadata sync, row-level security on API and application principals, and a rebuilt AI streaming pipeline. The open-core split is sharpening: capability stays open, cloud consumption and enterprise entitlements become the paid surface.
Expect the app SDK to keep maturing toward a stable marketplace GA and more product surfaces to move behind credit metering, following the email-metering pattern just shipped. The AI agent toolset should continue expanding from workflow inspection toward more write/act capabilities.
See more alternatives to ERPNext →
See more alternatives to Twenty →