A
Django-CRM
87.1
2,471 stars · MIT
CRM
platform leads by 5.5 · narrow
A
87.1
2,471 stars · MIT
B · leads
92.6
28,135 stars · EPL-2.0
Django-CRM versus platform 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; platform is written mainly in TypeScript. The composite score is 87.1 for Django-CRM and 92.6 for platform.
platform has 28,135 GitHub stars to Django-CRM's 2,471, a gap of 25,664 (11.39×). Forks are 1,065 for Django-CRM and 2,194 for platform. On the log scale used inside this pair, adoption is 76 versus 100, and the fork community is 91 versus 100.
Push history: Django-CRM was last pushed on 14 November 2026 (3 days ago), and platform was last pushed on 09 November 2026 (8 days ago). Open issues stand at 74 for Django-CRM (0.030 per star) and 698 for platform (0.025 per star). Issue-health scores are 70 and 70; activity scores are 100 and 92.
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. platform is listed as EPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for Django-CRM and 78 for platform. This is a procurement signal, not legal advice.
In CRM, both Django-CRM (2,471 stars) and platform (28,135 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, platform is open source.
The lead is split. Django-CRM is furthest ahead on license flexibility (96 to 78), while platform is furthest ahead on adoption (100 to 76). Choose the dimension a rollout cannot compromise on.
platform finishes ahead at 92.6 against Django-CRM at 87.1, a 5.5 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 | platform |
|---|---|---|
| GitHub stars | 2,471 | 28,135 |
| Forks | 1,065 | 2,194 |
| Open issues | 74 | 698 |
| Adoption | 76 | 100 |
| Activity | 100 | 92 |
| Community | 91 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 87.1 | 92.6 |
BottleCRM: free, open-source (MIT) CRM with sales, support tickets and invoicing in one app. Unlimited users; self-host or use the hosted app.
Huly — All-in-One Project Management Platform (alternative to Linear, Jira, Slack, Notion, Motion)
platform has more GitHub stars: 28,135 versus 2,471 for Django-CRM. The gap is 25,664 stars.
Django-CRM was pushed more recently: 14 November 2026 versus 09 November 2026 for platform. That is 5 days apart.
Yes. This catalog marks both Django-CRM and platform 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. platform is listed as EPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
platform scores 92.6 and Django-CRM scores 87.1. This page calls that a narrow lead for platform.