ERPNext vs Clari
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.
Post-Salesloft merger, Clari is fusing two GTM stacks into one AI-driven revenue platform.
Following its late-2025 merger with Salesloft, Clari is consolidating two overlapping go-to-market products into a single revenue platform. Recent releases have shifted from parallel Clari/Groove notes into unified Clari+Salesloft release notes, and Clari Copilot has been promoted to the platform's conversation-intelligence layer, displacing Salesloft Conversations. Groove, the older acquisition, is now in wind-down mode with migration notices and a scheduled maintenance window.
The arc is steady integration and consolidation: cross-product workflows (AI emails, tasks, follow-ups) shipped first, then Copilot absorbed Conversations as the unified intelligence engine, and now the data layer is being opened to external AI agents via MCP. Legacy plumbing is being retired in parallel — the Salesforce Connected App is being replaced with a managed AppExchange package, and Groove is being folded in. The direction points toward one platform, one intelligence layer, and increasingly agent-accessible revenue data.
The next moves are likely the phased migration of existing Salesloft Conversations customers onto Clari Copilot and broader MCP/agent connectivity, extending the pattern set by the Copilot MCP Server and the Claude connector.
See more alternatives to ERPNext →
See more alternatives to Clari →