Our assessment is that Twenty merits evaluation for technical teams that want a CRM they can shape like software: customizable objects and views, open APIs with webhooks and MCP, and honest self-hosting. The limits to weigh are the operational cost of self-hosting, migration effort from a large Salesforce estate, tiered governance features, and API rate caps on heavy integrations.[1][2][3]
Good fit. We would evaluate Twenty first if the goal is a CRM that developers can shape like an internal tool: custom objects, APIs, webhooks, and MCP access make it a natural fit for teams that already build software.[1][2]
Keep in mind. Self-hosting is real but operational: the install runs on Docker Compose with Postgres and Redis, and the team running it owns upgrades, backups, monitoring, and availability.[1]
Repository review signals: unknown status, very stale · Observed August 31, 2026.
Sources and editorial review
Source research. Reviewed on October 9, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Twenty official homepage
official · Observed October 9, 2026
Official homepage: open-source CRM alternative to Salesforce; customizable objects and views; email and calendar sync; REST and GraphQL APIs; webhooks; MCP integration; no-code and AI workflows; self-hosting option.
- Twenty pricing and billing
official · Observed October 9, 2026
Official pricing and billing page: Start/Boost/Scale/Organization tiers with monthly and annual per-user prices, 7-day trial, free self-hosted edition, and SSO/row-level permissions on higher tiers.
- twentyhq/twenty repository README
official · Observed October 9, 2026
Official repository README: TypeScript CRM with NestJS, React, Postgres, Redis; Docker self-hosting; create-twenty-app framework; no-code and AI workflows; CSV and Salesforce migration tooling.