FluentCRM vs Twenty
Side-by-side trajectory, velocity, and editorial themes.
FluentCRM's 3.0 rewrite adds SMS, AI authoring, and an MCP server
FluentCRM just shipped 3.0, a ground-up rewrite on Vue 3 with a Gutenberg-native email builder, SMS marketing, AI email authoring and summaries, an MCP server for AI agents, a new dashboard, and dark mode. The releases leading up to it were steady maintenance, hotfixes plus incremental WooCommerce and FluentCart integration work and reporting improvements.
The product is moving from a WordPress email-marketing plugin toward a broader, AI-assisted, multi-channel CRM. SMS and the MCP server in particular push it beyond email and into agent-driven workflows.
Expect 3.x point releases stabilizing the rewrite, plus deeper SMS and AI build-out now that the foundation has shipped.
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 FluentCRM →
See more alternatives to Twenty →