CRM: comparación
Django-CRM vs EspoCRM
Precios, funciones documentadas y límites de fuentes oficiales fechadas, lado a lado. Lo desconocido sigue siendo desconocido; con unidades de facturación distintas no se pueden comparar los costes directamente.
Última comprobación de fuentes: 8 nov 2026
Para quién esDjango-CRM is a free, self-hosted CRM built with Python and Django that combines CRM, task management, mailing and CRM analytics in one platform.
Última comprobación de fuentes: 10 nov 2026
Para quién esEspoCRM describes an open-source CRM for leads, contacts and sales opportunities.
Qué responden las fuentes
Una lectura de la documentación oficial revisada de Django-CRM y EspoCRM. No es una prueba práctica, una clasificación ni la recomendación de un producto.
- Preguntas de compra respondidas para ambos
- 2 requisitos
- Documentado solo para uno
- 3 requisitos
- Sin verificar para ninguno
- 4 requisitos
- Precios
- Aún no comparables
Precio
Django-CRM
Plan gratuito · precios de pago sin verificar ·
- Self-hosted: sin cuota de suscripción ·
EspoCRM
Plan gratuito · precios de pago sin verificar ·
- Self-hosted: sin cuota de suscripción ·
Aún no hay una comparación de precios completa en igualdad de condiciones; los próximos pasos indican qué falta.
Preguntas de compra respondidas para ambos
Aunque las etiquetas coincidan, revisa en cada fuente las diferencias de planes, unidades y alcance.
- Roles y permisos
- Django-CRM Predefined roles cover company executives (chiefs), sales managers, operators, superoperators serving several sales departments, co-workers, task operators and accountants.
- EspoCRM For the MCP extension, the MCP scope has to be enabled in Roles, and the role must grant access to all the scopes the endpoint is intended to use.
- Integraciones
- Django-CRM Built-in VoIP calling integrates with the provider Zadarma; other providers need their own integration files.
- EspoCRM A REST API lets EspoCRM be integrated with other applications.
Límites que revisar
- Django-CRM Django-CRM runs on Django Admin and has no built-in standalone REST API; a REST API has to be added with third-party packages designed for Django Admin.
- Django-CRM The README lists compatibility with Django 6.0+, Python 3.12+, MySQL 8.0.11+ and PostgreSQL 14+; a version compatible with Django 5.2.11 LTS is kept on a separate branch.
- EspoCRM The captured EspoCRM README lists PHP 8.3–8.5 and named database options for the documented installation.
- EspoCRM Documented installation routes are manual installation, an installation script, Docker and Docker with Traefik.
Aún sin verificar
No hay fuentes revisadas para ninguno de los productos sobre: usuarios, usuarios mínimos, límites de registros y límites de automatización.
Documentado solo para un producto, en la tabla de abajo: Django-CRM: embudos y cargos por llamadas, SMS y email; EspoCRM: complementos.
«Sin verificar» significa que nuestras fuentes revisadas no lo establecen. No significa que a un producto le falte la función ni que no cueste nada.
Evidencia lado a lado
Valores documentados con sus fuentes y fechas de comprobación; los requisitos que las fuentes no establecen quedan marcados.
- Documentado como compatible
- Documentado como no compatible
- Sin verificar Las fuentes no lo establecen
- No aplica
| Requisito | Django-CRM | EspoCRM |
|---|---|---|
| Precios | Plan gratuito · precios de pago sin verificar | Plan gratuito · precios de pago sin verificar |
| Para quién | Django-CRM is a free, self-hosted CRM built with Python and Django that combines CRM, task management, mailing and CRM analytics in one platform. Comprobado el 6 nov 2026 · Django-CRM: django-crm-project | EspoCRM describes an open-source CRM for leads, contacts and sales opportunities. Comprobado el 3 nov 2026 · EspoCRM: espocrm-readme |
| Límites de cobertura | Django-CRM runs on Django Admin and has no built-in standalone REST API; a REST API has to be added with third-party packages designed for Django Admin. Comprobado el 6 nov 2026 · Django-CRM: django-crm-project
| The captured EspoCRM README lists PHP 8.3–8.5 and named database options for the documented installation. Comprobado el 3 nov 2026 · EspoCRM: espocrm-readme
|
| Embudos | Deals are tracked as the sales pipeline, alongside requests, leads and opportunities, and companies and contact persons. Dated publisher project README at release v3.1.0 (commit e182a34) captured 8 November 2026; supplier feature description, not a hands-on test. The number of pipelines or stages is not stated; the analytics app lists sales funnel analysis. Comprobado el 8 nov 2026 · Django-CRM: django-crm-project | Sin verificar |
| Roles y permisos | Predefined roles cover company executives (chiefs), sales managers, operators, superoperators serving several sales departments, co-workers, task operators and accountants. Publisher documentation (Adding Django CRM users) in the official repository at release v3.1.0, captured 8 November 2026; supplier description, not a hands-on test. The same page says add, view, change and delete permissions can be assigned to individual users or groups, and that sales managers see only objects of their own department. Comprobado el 8 nov 2026 · Django-CRM: django-crm-users-project | For the MCP extension, the MCP scope has to be enabled in Roles, and the role must grant access to all the scopes the endpoint is intended to use. Dated README of the official ext-mcp repository at release 0.3.0 (commit e4dc1d1, AGPL-3.0) captured on 9 November 2026; supplier description, not a deployment or independent test. This describes access to the optional MCP extension, not EspoCRM’s whole role model. Comprobado el 10 nov 2026 · EspoCRM: espocrm-mcp-project |
| Cargos por llamadas, SMS y email | Newsletters go out through sales managers’ own configured email accounts; mailings from the main sales manager account reach only recipients marked VIP, to avoid spam filters. Publisher documentation (CRM email marketing) in the official repository at release v3.1.0, captured 8 November 2026; supplier description, not a hands-on test. No per-email charge or sending allowance is stated. The page recommends additional email accounts for recipients who are not VIP, and says a sales manager can mail only the recipients, and only through the mail accounts, assigned to them. Comprobado el 8 nov 2026 · Django-CRM: django-crm-mailing-project | Sin verificar |
| Complementos | Sin verificar | EspoCRM can act as an MCP server for AI agents once the official MCP extension is installed. Dated README of the official ext-mcp repository at release 0.3.0 (commit e4dc1d1, AGPL-3.0) captured on 9 November 2026; supplier description, not a deployment or independent test. The README states no price for the extension; the MCP protocol version it supports is 2026-07-28 only. Comprobado el 10 nov 2026 · EspoCRM: espocrm-mcp-project |
| Integraciones | Built-in VoIP calling integrates with the provider Zadarma; other providers need their own integration files. Publisher documentation (VoIP and messengers) in the official repository at release v3.1.0, captured 8 November 2026; supplier description, not a hands-on test. Zadarma is a separate service whose call charges were not captured. The same page says messages through Viber or WhatsApp need those apps installed on the user’s device. Comprobado el 8 nov 2026 · Django-CRM: django-crm-voip-project | A REST API lets EspoCRM be integrated with other applications. Dated publisher project README at release 10.1.0 (commit c344502) captured on 9 November 2026; supplier description, not a deployment or independent test. Hosted services, extensions and support are not covered by this passage; their prices were not captured. The API reference, authentication methods and rate limits were not captured. Comprobado el 10 nov 2026 · EspoCRM: espocrm-project |
| Nota de cobertura | Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms. | Project repository README captured 3 November 2026; SuiteCRM requirements in this evidence concern the 7.15.2 README, not every SuiteCRM release. Hosted terms, support, migration and software behavior were not tested. |
4 requisitos sin evidencia revisada aquí
Sin verificar significa que las fuentes revisadas no lo establecen; no significa que el producto no lo tenga ni que no cueste nada.
- Usuarios Django-CRM: sin verificar · EspoCRM: sin verificar
- Usuarios mínimos Django-CRM: sin verificar · EspoCRM: sin verificar
- Límites de registros Django-CRM: sin verificar · EspoCRM: sin verificar
- Límites de automatización Django-CRM: sin verificar · EspoCRM: sin verificar
Próximos pasos
- Confirma los precios de los planes de pago, el plazo de facturación y los impuestos de Django-CRM en su página oficial de precios; aquí solo está verificado su plan gratuito.
- Confirma los precios de los planes de pago, el plazo de facturación y los impuestos de EspoCRM en su página oficial de precios; aquí solo está verificado su plan gratuito.
- Pregunta a Django-CRM por estos puntos: usuarios, usuarios mínimos y límites de registros. Nuestras fuentes aún no los confirman.
- Pregunta a EspoCRM por estos puntos: usuarios, usuarios mínimos y límites de registros. Nuestras fuentes aún no los confirman.
- Django-CRMIr a Django-CRMPerfil y planes
- EspoCRMIr a EspoCRMPerfil y planes
Las comisiones nunca cambian los costes, la idoneidad ni el orden.