TopGit
GitHub Repo Review

Twenty CRM: Open-Source Salesforce Alternative

twentyhq/twenty
TTopGit review image for twentyhq/twenty
Review by Topgit.dev for twentyhq/twenty, with GitHub repository stats and README context.
Quick verdict

Twenty CRM is an open-source alternative to Salesforce built to be defined in code, not clicked together in an admin panel. Reach for it if you're a technical team that wants custom objects and workflows versioned like the rest of your stack, self-hosted on infrastructure you control. Skip it if you need a mature app marketplace and no one on the team wants to run a NestJS/React/Postgres stack.

Stars
★ 54.3k
Forks
⑂ 8.4k
Language
TypeScript
License
See repository
Topic
Frontend
Updated
Aug 2026
Homepage
GitHub

What is Twenty?

Twenty is an open-source CRM platform for modeling contacts, companies, and deals as code instead of working inside a vendor's fixed schema, built on a React frontend and a NestJS/GraphQL backend over PostgreSQL. You can sign up for a hosted cloud workspace at twenty.com in minutes, or self-host it yourself with Docker Compose if you want the data on your own infrastructure.

Core features of Twenty

  • Code-first schema - twenty-sdk/define lets you declare objects like a 'deal' with TEXT, CURRENCY, and DATE_TIME fields instead of clicking through a schema builder.
  • CLI scaffolding and publishing - `npx create-twenty-app my-app` bootstraps a new app, and `npx twenty app:publish --private` ships it to your workspace.
  • Composable primitives - objects, views, workflows, and agents are the building blocks the docs walk through, each extendable as code.
  • GraphQL API - the backend exposes GraphQL, per the repo's topics, for querying and mutating CRM data programmatically.
  • Background job processing - the NestJS backend runs on BullMQ with Redis, so long-running work doesn't block requests.
  • Nx monorepo stack - React frontend (Jotai, Linaria, Lingui) and NestJS backend live in one Nx-managed repo alongside PostgreSQL and Redis.
How this repository's GitHub stars have grown over time. Source: star-history.com.View the star history

What you can build with Twenty

  • Sales pipeline tracking - model deals with custom fields like close date and amount, and move them through stages you define yourself.
  • Contact and company records - a central database of customers that other internal tools can query through Twenty's GraphQL API.
  • Custom line-of-business objects - define something Salesforce doesn't ship out of the box, using the same defineObject API used for deals.
  • Internal apps on CRM data - the docs point to workflows and agents as ways to automate actions on records, built and published with the same CLI used to scaffold apps.

Running Twenty locally or on your server

Twenty CRM gives you three paths to running it, per the project's README. The fastest is the hosted cloud: sign up at twenty.com and a workspace is ready in under a minute, with no infrastructure to manage. To build a custom app on top of Twenty, scaffold one with `npx create-twenty-app my-app`, define objects and fields with the `twenty-sdk/define` package (a `defineObject` call with fields like TEXT, CURRENCY, or DATE_TIME), then ship it to your workspace with `npx twenty app:publish --private` - the README points to a separate app development guide for views, agents, and logic functions. To self-host on your own infrastructure, the README links out to a Docker Compose guide; the exact compose file and environment variables aren't included in the material reviewed here, so check that guide directly before deploying.

Strengths

  • Objects, fields, and views are defined in code via twenty-sdk/define, so schema changes go through the same review process as any other code change instead of a click-through admin panel.
  • The cloud path needs zero infrastructure - README says a workspace is ready in under a minute at twenty.com.
  • Docker Compose self-hosting is a real, documented option for teams that need the CRM's data on their own servers.
  • Built on a stack most web teams already know - TypeScript, NestJS, React, PostgreSQL, Redis - so there's no new paradigm to learn just to extend it.

Known limitations of Twenty

  • Self-hosting means running the full stack yourself - NestJS, PostgreSQL, Redis, and BullMQ - not a single lightweight binary; the README links to a Docker Compose guide but doesn't detail resource requirements.
  • The README doesn't name a license. Confirm it in the repo before shipping to production.
  • Building custom objects and apps goes through the twenty-sdk/define API and the Twenty CLI - no no-code schema builder is described for that path, only the base cloud UI.
  • AI is listed as a core building block, but the README only links out to further docs for it ('Learn more about AI in doc') without describing what the AI agents do.

Alternatives to consider

Salesforce - the incumbent proprietary CRM Twenty CRM positions itself against; the safer default if you need a mature app marketplace and don't want to run any of your own infrastructure.HubSpot - a hosted CRM/marketing platform with a large ecosystem of pre-built integrations, for teams that want a SaaS product rather than something they define in code.Pipedrive - a simpler, sales-pipeline-focused CRM for teams that just want deal tracking without customizing a data model.crm - another open-source CRM option on TopGit worth comparing before committing to Twenty CRM's code-first approach.

Frequently asked questions about Twenty

Is Twenty CRM free and open source?

Twenty CRM is published as open-source software on GitHub, and its README calls it 'the open alternative to Salesforce.' The specific license terms aren't listed in the metadata reviewed for this review, so check the repository's license file directly before relying on Twenty CRM for a commercial deployment.

What programming languages and frameworks power Twenty?

Twenty CRM is written mainly in TypeScript. Its backend runs on NestJS with BullMQ for background jobs, PostgreSQL for data, and Redis for queues, while its frontend uses React with Jotai for state, Linaria for CSS-in-JS, and Lingui for translations, all inside an Nx monorepo.

Can I self-host Twenty on my own infrastructure?

Self-hosting Twenty CRM on your own infrastructure is supported through Docker Compose, according to the project's documentation. Contributors can also run Twenty locally using the project's local setup guide instead of relying on the hosted cloud workspace at twenty.com.

What AI features does Twenty CRM include?

Twenty CRM's README lists AI as one of its core building blocks alongside objects, views, and workflows, and links out to further documentation for it. The README itself doesn't describe what the AI agents do, so check Twenty's docs directly for specifics.

How customizable is Twenty compared to Salesforce?

Twenty CRM is customized at the code level: you define objects, fields, and views with the twenty-sdk/define API and ship them using the Twenty CLI. Salesforce customization typically happens through its own admin UI and Apex, so Twenty trades a steeper technical bar for version-controlled, code-reviewed changes.

Is Twenty suitable for small teams or only enterprises?

Twenty CRM works for small teams that use the hosted cloud workspace at twenty.com without managing any infrastructure. The README doesn't mention an enterprise-only tier, but self-hosting Twenty does require running a NestJS, PostgreSQL, and Redis stack, which favors teams with some technical capacity.

The problem it solves

Off-the-shelf CRMs like Salesforce lock the data model behind an admin UI and a proprietary customization language, so extending them for a niche business process means fighting the platform or paying for consultants. Twenty CRM's own README frames its goal as giving technical teams a CRM defined in code - objects, fields, and workflows as version-controlled artifacts - so the CRM evolves at the same pace as the rest of the product instead of lagging behind as a separate system.

Who should try it — and who should skip

Twenty CRM fits engineering-led teams that already run a TypeScript/PostgreSQL stack and want their CRM schema living in the same repo and review pipeline as the rest of their code. It also works for teams happy to start on the hosted cloud workspace and move to self-hosting later if requirements change. Skip it if you need a large marketplace of pre-built integrations out of the box, or if nobody on the team wants to own a NestJS/React/Postgres/Redis deployment long-term.

Related repositories

Source & attribution

Based on the twentyhq/twenty GitHub repository and its README (github.com/twentyhq/twenty).

GitHub data · last synced Aug 14, 2026Reviewed by Henry
Back to TopGit

Want a second opinion on twenty?

Ask an AI that can read this page — one click and you get its take on twenty.

GitHub