What you need
1 projectCommercial useMaintainedSetupCost
TwentyAn open-source CRM for contacts, companies and deals, with custom fields and data objects.Commercial useConditionsMaintainedActiveSetupModerateCostPaid tiers- Commercial use
- Conditions
- The core is AGPL-3.0, while files marked @license Enterprise fall under Twenty’s commercial license (requiring a paid subscription) and SDK/UI packages are MIT. An explicit Twenty Application Exception under AGPLv3 Section 7 lets you build proprietary apps and integrations over Twenty’s REST/GraphQL APIs, webhooks and SDKs without triggering copyleft; modifying Twenty itself and serving users over a network still requires offering your modified source.
- Maintained
- Active
- Last push on 2026-11-04. The repository is not archived.
- Setup
- Moderate
- There is a one-line install script as well as an official Docker Compose stack running four services: server, worker, PostgreSQL and Redis. The docs state a hard minimum of 2 GB of RAM (processes crash below that). Before going live you set SERVER_URL, generate a random ENCRYPTION_KEY, and keep special URL characters (@, /, #, %) out of PG_DATABASE_PASSWORD so the unencoded database URL parses cleanly.
- Cost
- Paid tiers
- Self-hosting the Pro tier is free for unlimited users, objects and records (up to 5 workspaces, with field-level custom roles); you only pay for a 2 GB+ RAM server. List prices in November 2026: adding row-level permissions and SSO on a self-hosted install requires the Organization plan at $19 per user a month billed yearly ($25 monthly), with Enterprise starting at $50,000 a year. Official Twenty Cloud hosting is $9 per user a month billed yearly ($12 monthly) for Pro and $39 per user a month billed yearly ($51 monthly) for Organization.
- What to watch out for
- The free self-hosted tier stops at field-level permissions: hiding specific deals or contacts between sales reps requires row-level permissions, which — along with SAML / OIDC SSO and custom AI models — sits in the paid $19/user/month Organization plan. Back up your ENCRYPTION_KEY safely as well: losing it permanently breaks encrypted OAuth tokens and secrets stored in the database.
Your industry is not here?
Tell me the industry and what you need solved. I will look at it next.