sales / agent
DeskcommCRM
An open-source, self-hosted CRM for selling over WhatsApp, with AI agents, a sales pipeline, automations and an install kit for a VPS.
At a glance
- Purpose
- An open-source, self-hosted CRM for selling over WhatsApp, with AI agents, a sales pipeline, automations and an install kit for a VPS.
- Runs in
- Local agent with shell, MCP server, Web service
- Operating systems
- macOS, Linux, Windows
- Needs
- Runtime: Docker; Needs internet: Yes; Needs accounts or API keys beyond your agent: Yes
- Files and data
- Reads files: Yes; Writes files: Yes; Sends data to other services: Yes
- Tool type
- Agent
- Delivery
- From GitHub
- Version
- Latest on the main branch
- Access
- Code on GitHub
- Compatibility
- According to the README: a VPS with Docker, including ARM64 hosts such as Oracle Ampere A1, and hosts that already run their own reverse proxy such as Hostinger, Coolify, Dokploy and CapRover. You connect to the VPS from Terminal on macOS or Linux, or PowerShell on Windows, and its starter script runs on macOS, Linux or WSL. AI providers: OpenRouter, Anthropic and OpenAI are the install choices, and the stack table also lists Requesty and Google. WhatsApp runs through WAHA Plus (NOWEB engine) or the Meta Cloud API. It also names Supabase, Upstash Redis, Sentry and a Nuvemshop integration. The assistant guides load in Claude Code, Codex, Cursor, OpenCode and Antigravity.
- External costs
- The README describes DeskcommCRM as MIT-licensed and self-hosted. The README requires a VPS, domain, Supabase database and an AI provider key, and mentions free Supabase and Upstash tiers. The README promotes HostGator through an infrastructure partnership and a partner link that supports the project; the README says other Docker VPS providers can be used. The README names WAHA Plus and Meta Cloud API for WhatsApp and gives no prices for them. Infrastructure and connected services may have paid tiers or usage charges. Your coding agent or model provider may charge for usage.
- Permissions
- The README shows VPS root SSH and an installer using the operator's Supabase credentials and OpenRouter, Anthropic or OpenAI key. The README says SUPABASE_ACCESS_TOKEN lets the installer create a Supabase project and retrieve its credentials. The README's contribution workflow includes branching, code changes, checks, commits and opening a pull request. The README says AI agents use tenant knowledge, skills/memory, move leads and hand off to people. The README says automation sends WhatsApp messages/webhooks and starts paused until activation. The README says AI-proposed improvements require human approval before being applied as a new version. The README describes destructive Docker-resource uninstall with typed confirmation or --force. The top-level file list includes hooks/ and extensoes/; the README does not explain their behaviour. The README gives computer-side starter and assistant-guide commands that pipe downloaded scripts into bash.
- Usage terms
- MIT License, as stated in the repository. See its LICENSE file for the exact terms.
- Interface
- web
Code on GitHub
melgarafael/DeskcommCRM
MITOpen-source AI sales OS — self-hosted CRM with native AI agents + WhatsApp (WAHA). Open alternative to Kommo, Octadesk & Intercom for any business that sells by chat. MCP-ready, multi-tenant, LGPD.
Topics: ai ai-agents chatbot crm customer-support ecommerce lgpd mcp
Public GitHub data fetched · 0 days old
View on GitHub ↗What it does
The Portuguese README describes DeskcommCRM as a self-hosted CRM for businesses selling over WhatsApp, with AI agents for answering, qualifying and moving leads through a funnel. The README lists English and Spanish versions.The README lists a WhatsApp inbox, Kanban pipeline, contacts, configurable funnels, follow-ups, agent knowledge and memory, skills, webhook intake, automation rules, team settings, audit records and an LGPD area. The README says WhatsApp connects through WAHA QR-code onboarding or Meta Cloud API. The README lists an internal MCP server as delivered and public MCP capabilities as planned.
The README describes an installation kit for installation, updates, backups, restoration, password resets and health checks. The README says assistant guides load in Claude Code, Codex, Cursor, OpenCode and Antigravity for installation, client configuration, metrics, prompt adjustment and contributions.
Who it is for
Businesses that sell by chat on WhatsApp and want to host their own CRM with AI agents, and developers who want to build on it.Example tasks
Install the CRM on your own VPS by cloning the repository and running the installer from the install kit.Connect a WhatsApp number by scanning a QR code during onboarding.
Create a capture source that receives leads by webhook and places them in a chosen funnel stage.
Build an automation rule that starts paused until you review it and turn it on.
Ask an AI coding assistant to install the CRM on your VPS using the repository's assistant guides.
Getting started
The README's main route connects to a VPS with SSH, clones the repository and runs bash hostgator-setup-kit/install.sh. The README says the installer asks for a domain, keys and admin password, validates answers, generates technical secrets, applies the database schema, creates the first admin, starts the HTTPS stack, and installs automation and update-agent cron jobs. The README describes the installer as idempotent and able to resume an interrupted installation. The README gives a non-interactive route using .env.hostgator.example and bash hostgator-setup-kit/install.sh --yes. The README also describes computer-side starter and assistant-guide installers and updates through bash hostgator-setup-kit/update.sh. The README has the exact commands. The README's dev route uses npm to install pnpm globally. The README says assistant guides can be installed outside the checkout and are updated by rerunning installation.Limitations
The README requires a Docker VPS, recommends 4 GB RAM, and says the installer asks before installing missing Docker. The README requires a domain A record, a Supabase database and an OpenRouter, Anthropic or OpenAI key; Supabase can be external or on the same VPS. The README says WhatsApp uses the operator's number through QR onboarding or Meta's channel. The README says the computer-side starter runs on macOS, Linux or WSL, with Windows users using PowerShell for SSH. The README says Supabase's free plan needs separately scheduled backups, restoration requires an empty database, downgrades need --force, and uninstalling removes Docker volumes including local WhatsApp sessions. The README labels support community and as-is, without an SLA or guaranteed support, and says operators are responsible for updates and backups. The README says the instance host is the personal-data controller with associated LGPD obligations. The README's development route uses Node 22 and requires database extensions before applying supabase/baseline.sql; the README warns that the migration chain does not initialize the database. The README is in Portuguese and says public MCP is planned. The repository can change at any time; check its README before you install.Data practices
The README says the app, WhatsApp service and workers run on the operator's VPS, with Supabase either external or on that VPS. The README says WhatsApp media uses a private Supabase Storage bucket and backups include the database and WhatsApp sessions. The README describes selectable AI providers and says the host is the personal-data controller under LGPD. The README describes anonymization, append-only audit records and five-year audit retention.The README says Sentry telemetry is opt-in during installation and is disabled in non-interactive mode when SENTRY_DSN is unset. The README says community Sentry receives error reports and recordings immediately preceding errors, with CPF, phone and email substitutions, sensitive-header removal, redacted webhook and invitation URLs, and masked text and media. The README says performance tracking and continuous session replay are set to zero on that route. The README gives SENTRY_DSN=off to disable telemetry and SENTRY_DSN=<seu-dsn> to send to the operator's own Sentry, where performance and replay are enabled.