A
atomic-crm
82.7
1,446 stars · MIT
CRM
Twenty leads by 11.1 · clear
A
82.7
1,446 stars · MIT
B · leads
93.8
61,042 stars · AGPL-3.0
atomic-crm versus Twenty is a CRM comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 82.7 for atomic-crm and 93.8 for Twenty.
Twenty has 61,042 GitHub stars to atomic-crm's 1,446, a gap of 59,596 (42.21×). Forks are 927 for atomic-crm and 10,113 for Twenty. On the log scale used inside this pair, adoption is 66 versus 100, and the fork community is 74 versus 100.
Push history: atomic-crm was last pushed on 17 November 2026 (0 days ago), and Twenty was last pushed on 17 November 2026 (0 days ago). Open issues stand at 22 for atomic-crm (0.015 per star) and 146 for Twenty (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
atomic-crm is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Twenty is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for atomic-crm and 52 for Twenty. This is a procurement signal, not legal advice.
In CRM, both atomic-crm (1,446 stars) and Twenty (61,042 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: atomic-crm is open source, Twenty is freemium.
The lead is split. atomic-crm is furthest ahead on license flexibility (96 to 52), while Twenty is furthest ahead on adoption (100 to 66). Choose the dimension a rollout cannot compromise on.
Twenty finishes ahead at 93.8 against atomic-crm at 82.7, a 11.1 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | atomic-crm | Twenty |
|---|---|---|
| GitHub stars | 1,446 | 61,042 |
| Forks | 927 | 10,113 |
| Open issues | 22 | 146 |
| Adoption | 66 | 100 |
| Activity | 100 | 100 |
| Community | 74 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 82.7 | 93.8 |
A full-featured CRM built with React, shadcn/ui, and Supabase.
Twenty is an open CRM aimed at teams that want a modern interface without adopting a closed SaaS contact database. It covers people, companies, and opportunities and is built to be self-hosted.
Twenty has more GitHub stars: 61,042 versus 1,446 for atomic-crm. The gap is 59,596 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both atomic-crm and Twenty as self-hostable. Confirm each project's deploy docs before you plan a migration.
atomic-crm is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Twenty is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Twenty scores 93.8 and atomic-crm scores 82.7. This page calls that a clear lead for Twenty.