Close vs DeskcommCRM
DeskcommCRM is a plausible replacement for teams whose sales process is centered on WhatsApp and that want an MIT-licensed, self-hosted CRM with AI agents, pipelines, follow-up automation, and human handoff. It is not a like-for-like Close replacement: the supplied documentation does not establish native voice calling, integrated email/SMS outreach, meeting capture, or equivalent breadth in sales reporting. Choose it

Decision guide
The practical reasons to choose either option, based on documented capabilities.
Choose DeskcommCRM if
- WhatsApp-led sales teams needing shared conversations, lead qualification, pipelines, and follow-up
- Organizations requiring self-hosting and control over the VPS location
- Teams willing to operate Docker infrastructure, Supabase, WhatsApp connectivity, and AI-provider credentials directly
Stay with Close if
- Representatives depend on native inbound and outbound calling, call recording, voicemail drops, or power and predictive dialers
- Sales sequences must combine integrated email, SMS, calls, and tasks rather than focus primarily on WhatsApp
- Teams require documented meeting capture, transcripts, summaries, and action items inside the CRM service
Deployment and operations
DeskcommCRM is MIT-licensed and self-hosted on a Docker-capable VPS; 4 GB RAM is recommended. The documented installation clones the repository and runs a shell installer. Production setup also requires a domain, Supabase credentials, an OpenRouter, Anthropic, or OpenAI key, and a WhatsApp number or Meta channel. Operators remain responsible for infrastructure and backups; the README warns that free Supabase plans do not back up automatically. Documented update tooling backs up the database,更新es
Feature fit
What DeskcommCRM covers
- Lead and contact records
- Configurable deal pipelines
- Conversation-linked sales workflows
- Trigger-based follow-up automation
- Lead assignment and routing
- Pipeline and representative performance views
- AI-assisted qualification and CRM updates
What’s different or missing
- Native voice calling not documented
- Power or predictive dialing not documented
- Integrated email outreach not documented
- SMS outreach not documented
- Meeting transcription and notes not documented
- Embeddable no-code forms not documented
- Close-compatible data import not documented
Project snapshot
- GitHub stars
- 570
- Contributors
- 16
- Language
- TypeScript
- Last commit
- Aug 17, 2026
- Latest release
- Aug 13, 2026
Categories: Sales Intelligence, Workflow Automation, Business Intelligence, Customer Relationship Management, Customer Data Platforms, Marketing Automation, Customer Support
Sources and editorial review11 linked sources
Public documentation supports this comparison. Automation assists collection and classification; editorial standards and corrections remain the responsibility of Kris.
Open-source AI sales OS — self-hosted CRM with native AI agents + WhatsApp (WAHA).
repository description · github.comAgentes de IA que atendem, qualificam e vendem no WhatsApp — dentro de um CRM open source rodando no seu servidor.
readme · github.comCRM | Kanban ... Contatos ... Funis
readme · github.comautomações: regras no formato QUANDO/SE/ENTÃO que disparam ações como adicionar tag, mover o lead no funil, atribuir a um atendente, mandar uma mensagem de WhatsApp ou avisar outro sistema via webhook de saída.
readme · github.comAbra `https://<seu-domínio>` ... entre com o admin
readme · github.comVPS com Docker ... App + WhatsApp + workers na sua máquina
readme · github.comOpen-source AI sales OS — self-hosted CRM with native AI agents + WhatsApp (WAHA).
verdict · github.comagentes de IA com RAG por tenant atendem, qualificam, movem leads no funil, disparam automações e sabem a hora de passar pra um humano
shared feature · github.comVPS com Docker. 4 GB de RAM recomendados
deployment · github.comgit clone https://github.com/melgarafael/DeskcommCRM.git cd DeskcommCRM bash hostgator-setup-kit/install.sh
deployment · github.como plano grátis do Supabase **não faz backup sozinho**. Vale agendar > `backup.sh` no cron diariamente.
deployment · github.com




