A
atomic-crm
83.3
1,446 stars · MIT
CRM
erpnext leads by 7.6 · clear
A
83.3
1,446 stars · MIT
B · leads
90.9
41,374 stars · GPL-3.0
atomic-crm versus erpnext is a CRM comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. atomic-crm is written mainly in TypeScript; erpnext is written mainly in Python. The composite score is 83.3 for atomic-crm and 90.9 for erpnext.
erpnext has 41,374 GitHub stars to atomic-crm's 1,446, a gap of 39,928 (28.61×). Forks are 927 for atomic-crm and 13,544 for erpnext. On the log scale used inside this pair, adoption is 68 versus 100, and the fork community is 72 versus 100.
Push history: atomic-crm was last pushed on 17 November 2026 (0 days ago), and erpnext was last pushed on 17 November 2026 (0 days ago). Open issues stand at 22 for atomic-crm (0.015 per star) and 2,265 for erpnext (0.055 per star). Issue-health scores are 84 and 52; 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. erpnext is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for atomic-crm and 64 for erpnext. This is a procurement signal, not legal advice.
In CRM, both atomic-crm (1,446 stars) and erpnext (41,374 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, erpnext is open source.
The lead is split. atomic-crm is furthest ahead on issue health (84 to 52), while erpnext is furthest ahead on adoption (100 to 68). Choose the dimension a rollout cannot compromise on.
erpnext finishes ahead at 90.9 against atomic-crm at 83.3, a 7.6 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 | erpnext |
|---|---|---|
| GitHub stars | 1,446 | 41,374 |
| Forks | 927 | 13,544 |
| Open issues | 22 | 2,265 |
| Adoption | 68 | 100 |
| Activity | 100 | 100 |
| Community | 72 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 83.3 | 90.9 |
A full-featured CRM built with React, shadcn/ui, and Supabase.
Free and Open Source Enterprise Resource Planning (ERP)
erpnext has more GitHub stars: 41,374 versus 1,446 for atomic-crm. The gap is 39,928 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both atomic-crm and erpnext 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. erpnext is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
erpnext scores 90.9 and atomic-crm scores 83.3. This page calls that a clear lead for erpnext.