Twenty, the open-source CRM

What Twenty actually is

Twenty is an open-source CRM, licensed AGPL-3.0, that you can self-host for free or run on its managed cloud. French-founded and Y Combinator-backed, it pairs a modern Notion-and-Attio-inspired interface with a clean, API-first data model. The pitch: a CRM you own as infrastructure, not rent as a vendor lock.

It has serious developer momentum: over 40,000 GitHub stars, more than 300 active contributors, and a fast release cadence that shipped Twenty 2.0 in April 2026. That release matters for this page, because it closed real gaps, native workflows, a developer platform, AI agents and a built-in MCP server, and dated a lot of the "Twenty is too early" takes you will read elsewhere. We track it because the open-source CRM is the one teams in our world keep asking about, and we want to give an honest read rather than a reflex.

Who Twenty is for, and who it is not

Most teams know within two questions whether Twenty is their CRM. The deciding factor is rarely a feature. It is whether ownership of the software is a requirement or a preference.

• Pick Twenty if open source, self-hosting or data sovereignty are hard requirements. A compliance posture that distrusts third-party clouds, a mandate to keep the system of record under your own roof, or a principled preference for owning your stack: that decides it on its own.
• Pick Twenty if you have engineering capacity to run software you operate. Self-hosting is real ops: upgrades, backups, uptime, security, getting paged when it breaks. A developer-led startup absorbs that easily. A lean revenue team without a platform engineer rarely should.
• Pick Twenty if cost per seat is the binding constraint. Self-hosted, the licence is free. Managed cloud runs far below the incumbents per user.
• Think twice if you want the CRM to simply work today with deep native integrations and nothing to operate. That is a managed-product strength, and it is where a polished SaaS like Attio still leads.

Where Twenty is genuinely strong

Where Twenty still trails, honestly

We do not run Twenty in production, so read this section as the read of an Attio-leaning team, not a takedown. Twenty's trajectory is good and 2.0 closed real gaps. These are the ones still open as of mid-2026.

• Integrations and ecosystem are younger. Fewer native connectors, a small app marketplace, a fraction of the partner and template ecosystem a mature managed CRM carries. The open codebase is a partial answer, but "we can build it" is a cost, not a feature.
• Reporting is lighter. Earlier-stage and thinner than what a relationship-led revenue team usually expects out of the box. A real gap today, on either platform honestly, but more so here.
• Self-hosting hides its true cost. The zero-licence price is the price before the work. Provisioning, upgrades, backups, security and on-call are real engineering time that a few cheap seats often outweigh.
• Maturity is a different risk profile. Software you operate yourself at this stage is not the same bet as a managed product with predictable upgrades and uptime. For some teams that trade is exactly right. For most, it is a real consideration.

Twenty vs Attio and HubSpot

The honest one-liner you will hear elsewhere holds up: Attio is the stronger CRM today, Twenty is the more interesting bet on tomorrow. Attio wins on maturity, native integrations, an API built for AI agents and a reporting path that works. Twenty wins, decisively, the moment open source, self-hosting or data ownership move from preference to requirement, because Attio cannot self-host, full stop. We laid the whole thing out, eight criteria with a winner on each row and the trade-offs that a feature count hides, in our Attio vs Twenty comparison.

Against HubSpot the contrast is different: Twenty is the open, low-cost, developer-led answer to a closed, premium-priced suite. If you are weighing the broader CRM landscape, our HubSpot page and Attio page cover where each managed product fits, and our comparison hub puts them side by side.

How Buildrhaus implements Twenty

Straight answer first: we specialise in Attio and we do not yet run Twenty in production. What we bring to a Twenty build is the method, not a portfolio of Twenty deployments, and we will tell you that before you sign anything. If your requirements point to an open-source, self-hosted system of record, that method transfers cleanly, because the hard parts of a CRM build are platform-agnostic.

• Data model designed on your real motion, not a template. The same modelling work behind our Attio builds: typed objects, first-class relationships, custom objects for whatever your business actually carries.
• Migration done properly. Field mapping, deduplication by identity, a full dry run on a copy, a verified cutover that reconciles to the record before anything touches production. The bar we hold every cutover to, documented on the Attio page.
• Automation on Twenty 2.0's workflow engine. Form triggers, conditions, HTTP requests, webhooks and serverless functions, plus the native MCP server for agent-driven reads and writes, configured against your process rather than a demo.
• Documentation and handover. A runbook, a model you understand, no standing access kept. With self-hosted Twenty that also means your infrastructure stays yours from day one.

If you are choosing between Twenty and a managed CRM, the fastest path is the diagnostic. We will give you a fair read before recommending either direction, including the case for not picking Twenty.

Before you ask

Go deeper

Where Twenty fits in the wider CRM landscape, with the same first-hand sources, no recycled marketing.