CRM 2 min read

BottleCRM vs Django-CRM: two Django CRMs, two designs

One ships a REST API with web and mobile apps; the other runs inside Django Admin. Scope, interfaces, licences and setup compared.

Same framework, separate projects

BottleCRM and Django-CRM are both self-hosted CRMs built on Django, and BottleCRM's repository is still called Django-CRM, which makes them easy to confuse. They are separate projects with different maintainers and licences: BottleCRM is maintained by RunCode Inc. under the MIT licence, and Django-CRM, from the DjangoCRM GitHub organisation, is licensed under AGPL-3.0.

Their scope overlaps on leads, contacts, opportunities or deals, and tasks. BottleCRM adds support tickets and invoices, with a helpdesk that the README describes as having SLA timers, escalations, macros and a knowledge base. Django-CRM adds projects, office memos, internal chat, sales funnel and income reports, and an email marketing module with campaigns and newsletters.

Interfaces and integrations

The biggest design difference is the interface. BottleCRM puts a SvelteKit web app, a native Flutter mobile app and a documented REST API in front of one Django backend, and it pitches that API to AI agents through personal access tokens. Django-CRM runs entirely on Django Admin, and its README says there is no built-in standalone REST API; API-based integrations, mobile apps and headless clients need a third-party package designed for Django Admin.

If other systems must read and write CRM records, BottleCRM's README covers that directly. If your staff are comfortable in admin-style screens and you want email accounts, IMAP synchronisation and campaigns inside the CRM, Django-CRM's README describes that in more detail.

Licences and hosting

The MIT licence on BottleCRM puts few conditions on modification or redistribution. AGPL-3.0 on Django-CRM requires you to share source changes with users if you offer a modified version over a network, so check it before customising heavily for clients.

BottleCRM isolates tenants with PostgreSQL Row-Level Security, and its README says one deployment can serve one company or many; managed hosting is also offered. Django-CRM can be evaluated on SQLite without an external database, and its compatibility list names MySQL and PostgreSQL.

Before you choose

Neither README establishes how either product performs with your data. Run both on a copy of real records, test the integrations you need and decide who will own upgrades and backups. Managed hosting prices for BottleCRM were not captured, and Django-CRM's README mentions no hosted option.

Sources

BottleCRM: bottlecrm-project · Evidence: documentation · Not checked

Django-CRM: django-crm-project · Evidence: documentation · Not checked

Next step

Tools in this guide

All CRM tools
All guides