Twenty

Twenty is an open source CRM for technical teams that build their own objects, workflows and apps, bought per user in the cloud or self-hosted at no cost.

Twenty gives a sales or operations team a CRM whose data model it can reshape, rather than a fixed schema it has to work around. Twenty.com PBC, an independent public benefit corporation incorporated in Delaware, builds it, and its full code base is public on GitHub. Companies, People and Opportunities come as standard objects, and admins add their own objects and fields without writing code. The same application runs as a hosted cloud workspace or on a team's own servers. Opportunities sit on a Kanban board where reps drag cards between stage columns, and any object can also be shown as a table or a calendar. Each record page carries tabs for its overview, its communication, its tasks and its files. Connected Gmail, Microsoft 365 or IMAP mailboxes sync email threads onto the matching records, and replies go out from inside Twenty. Workflows react to record events by creating tasks, updating fields or sending email, and AI agents with custom skills work alongside them. Dashboards hold tabs of chart, number and iFrame widgets, while REST and GraphQL APIs and webhooks expose every object to code. The product is aimed at technical teams that need a CRM built around complex processes and expect to keep changing it as the business evolves. Developer-led companies extend it with custom apps and the API, and companies that must keep customer data in house can self-host it. The cloud service is sold per user on the Pro and Organization plans, with Enterprise contracts arranged through the sales team. Self-hosting costs nothing and relies on community support on Discord, while Organization customers can bring in an implementation partner for a tailored rollout. A rep's day starts on the Opportunities board, moving a deal forward and finding the latest email thread already attached to the contact. Each team member gets a daily email of tasks due today, sent by a workflow, and managers follow the pipeline on a shared dashboard. When a deal is marked closed won, another workflow can create follow-up tasks for its owner or pass the deal's details to Stripe, QuickBooks or Xero. Teams leaving another CRM bring their contacts in through CSV import, then rebuild their own record types as custom objects. Twenty fits companies with engineers on hand and a sales process too specific for an off-the-shelf schema.