Django-CRM
Django-CRM (BottleCRM) is an open-source, self-hosted CRM platform built with Django REST and SvelteKit, designed for startups and small businesses. It supports multi-tenant deployments, lead/account/contact management, invoicing, and task tracking with PostgreSQL Row-Level Security for data isolation.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | MicroPyramid/Django-CRM |
| Owner | MicroPyramid |
| Primary language | Python |
| License | MIT — OSI-approved |
| Stars | 2.3k |
| Forks | 1k |
| Open issues | 71 |
| Latest release | 0.46 (2026-06-02) |
| Last updated | 2026-06-20 |
| Source | https://github.com/MicroPyramid/Django-CRM |
What Django-CRM is
Backend uses Django 5.x with DRF, PostgreSQL RLS, Redis, and Celery for async tasks; frontend is SvelteKit 2.x with TailwindCSS and shadcn-svelte. Includes MCP server for AI agent integration, JWT authentication, and AWS SES/S3 integration. Deployed via Docker Compose or manual setup.
Get the Django-CRM source
Clone the repository and explore it locally.
git clone https://github.com/MicroPyramid/Django-CRM.gitcd Django-CRM# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires PostgreSQL 14+, Redis, Python 3.10+, Node.js 18+, and Docker (or manual stack setup). Development velocity depends on team familiarity with Django, SvelteKit, and PostgreSQL RLS.
- RLS configuration is critical for multi-tenant security; verify `manage_rls` commands and test data isolation before production. Misconfiguration can leak cross-tenant data.
- Celery + Redis are required for background tasks (email, async processing). Plan for queue monitoring, dead-letter handling, and worker scaling.
- MCP integration (AI agents) works only with compatible clients (Claude, Cursor, Gemini). Token-based auth inherits user's role and org scope; review permission model before exposing.
- Database migration and upgrade strategy needed as v0.x stabilizes. Breaking changes may occur; test upgrades in staging.
When to avoid it — and what to weigh
- Need enterprise SaaS with vendor support — This is open-source community-maintained software. No commercial support, SLAs, or guaranteed incident response. Use if you can operate and debug it yourself or hire contractors.
- Require native mobile apps — Frontend is web-only (SvelteKit). No iOS/Android native apps. Mobile browser access works but may not match app user experience expectations.
- Complex integrations with legacy ERP/accounting systems — Limited pre-built integrations documented. AWS SES and S3 are primary integrations; other systems require custom development. Evaluate integration needs upfront.
- Need immediate, mature feature parity with Salesforce/HubSpot — Early-stage project (v0.46). Core CRM functions present but advanced features (forecasting, complex workflows, advanced reporting) may be missing or immature.
License & commercial use
MIT License (permissive, OSI-approved). Allows free use, modification, and distribution for any purpose, including commercial, provided the original MIT notice is retained. No copyleft restrictions.
MIT license permits commercial use without restriction. However: (1) you must retain the MIT license text in source and documentation; (2) there is no implied warranty or liability—use at your own risk; (3) no paid support or indemnification from the maintainers. Suitable for building commercial products, but accept full operational responsibility. Review your legal and compliance requirements for production deployments.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
PostgreSQL RLS is the core multi-tenant isolation mechanism; misconfiguration creates severe data leaks. JWT tokens for API auth; no CSRF/CORS details clearly stated—review headers. Email integration requires AWS credentials; manage securely. AI agent access (MCP) relies on personal access tokens; rotate regularly and audit token usage. No security audit or penetration test findings disclosed. Treat as pre-production code until you've reviewed and tested critical paths.
Alternatives to consider
Odoo Community Edition
Mature, self-hosted Python/PostgreSQL ERP/CRM with broader features (accounting, inventory, HR). Much larger codebase and community. Steeper learning curve; heavier deployment footprint.
n8n + Supabase + custom frontend
Low-code/no-code approach: use n8n for workflows, Supabase (PostgreSQL + RLS) for data, and build minimal UI. More flexible than a fixed CRM but requires more integration glue.
Metabase + Nocodb + API gateway
Lightweight, open-source data management. Nocodb provides no-code CRUD; Metabase adds BI. Less feature-rich CRM-wise but highly customizable and lower operational complexity.
Build on Django-CRM with DEV.co software developers
Start with Docker Compose for a 5-minute setup, or consult our implementation guides for production deployments. Need help with customization or RLS configuration? Devco can architect and build your CRM solution.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
Django-CRM FAQ
Can I use Django-CRM in production today?
How does multi-tenancy work? Is my data safe from other tenants?
Can I integrate with Salesforce, HubSpot, or Stripe?
What is the learning curve for customization?
Software development & web development with DEV.co
DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If Django-CRM is part of your open-source crm roadmap, our team can implement, customize, migrate, and maintain it.
Ready to Deploy Django-CRM?
Start with Docker Compose for a 5-minute setup, or consult our implementation guides for production deployments. Need help with customization or RLS configuration? Devco can architect and build your CRM solution.