A
Django-CRM
87.0
2,471 stars · MIT
CRM
nocobase leads by 3.0 · narrow
A
87.0
2,471 stars · MIT
B · leads
90.0
24,950 stars · license n/a
Django-CRM versus nocobase is a CRM comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Django-CRM is written mainly in Python; nocobase is written mainly in TypeScript. The composite score is 87.0 for Django-CRM and 90.0 for nocobase.
nocobase has 24,950 GitHub stars to Django-CRM's 2,471, a gap of 22,479 (10.10×). Forks are 1,065 for Django-CRM and 2,956 for nocobase. On the log scale used inside this pair, adoption is 77 versus 100, and the fork community is 87 versus 100.
Push history: Django-CRM was last pushed on 14 November 2026 (3 days ago), and nocobase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 74 for Django-CRM (0.030 per star) and 330 for nocobase (0.013 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
Django-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. nocobase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for Django-CRM and 30 for nocobase. This is a procurement signal, not legal advice.
In CRM, both Django-CRM (2,471 stars) and nocobase (24,950 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: Django-CRM is open source, nocobase is unpriced in this catalog.
The lead is split. Django-CRM is furthest ahead on license flexibility (96 to 30), while nocobase is furthest ahead on adoption (100 to 77). Choose the dimension a rollout cannot compromise on.
nocobase finishes ahead at 90.0 against Django-CRM at 87.0, a 3.0 point narrow 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 | Django-CRM | nocobase |
|---|---|---|
| GitHub stars | 2,471 | 24,950 |
| Forks | 1,065 | 2,956 |
| Open issues | 74 | 330 |
| Adoption | 77 | 100 |
| Activity | 100 | 100 |
| Community | 87 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 87.0 | 90.0 |
BottleCRM: free, open-source (MIT) CRM with sales, support tickets and invoicing in one app. Unlimited users; self-host or use the hosted app.
NocoBase is the open-source platform for building, running, and evolving business systems with AI. Agents write the code and do the work, NocoBase provides the foundation and governance, and people make the decisions.
nocobase has more GitHub stars: 24,950 versus 2,471 for Django-CRM. The gap is 22,479 stars.
nocobase was pushed more recently: 17 November 2026 versus 14 November 2026 for Django-CRM. That is 3 days apart.
Yes. This catalog marks both Django-CRM and nocobase as self-hostable. Confirm each project's deploy docs before you plan a migration.
Django-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. nocobase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
nocobase scores 90.0 and Django-CRM scores 87.0. This page calls that a narrow lead for nocobase.