melgarafael/DeskcommCRM

DeskcommCRM is a self-hosted CRM for businesses that sell through WhatsApp: AI agents handle conversations, qualify leads, move them through a pipeline, and hand off to a person when needed. It targets teams replacing hosted tools such as Kommo, Octadesk and Intercom with an installation they run on their own server. The main path is a Docker VPS install; the code itself is MIT-licensed, but running it means owning the operation.

What it does

The product combines an inbox, a Kanban pipeline, contacts and per-niche pipeline vocabulary with a set of AI-agent screens. The distinguishing part is that the agent is not a separate chat toy: it can execute skills during a conversation, draw on tenant-scoped RAG knowledge, create follow-ups for cold conversations, and appear as a first-class assignee in the CRM with an audit trail for AI-to-human handoff. Spending caps per organization limit model cost. A screen called Evolução da IA reports where the agent errs, and suggested improvements require human approval before becoming a new version. WhatsApp connectivity is either QR-code based through WAHA (with throttling, jitter and a sending window to reduce ban risk) or Meta's official Cloud API with approved templates.

Automation is built around inbound webhook lead sources (landing pages, Zapier, n8n) and WHEN/IF/THEN rules that can tag, move, assign, message or call out to another system. Events queue in a database table and are drained by a cron route that the installer configures; the README warns that without that cron, automations are created but never run.

Running it

The documented path is a VPS with Docker (4 GB RAM recommended), a domain with an A record, a Supabase project, and a key from OpenRouter, Anthropic or OpenAI. The installer generates secrets, applies the schema, creates the first admin, brings up the stack with HTTPS and installs the automation cron and updater. ARM64 hosts are supported. A dev setup exists for contributors, but the README explicitly says it is not the way to use the product, and that the real schema lives in baseline.sql rather than the stub migrations — a point that matters if you intend to modify it. Setup instructions are in the hostgator-setup-kit and setup guide: setup kit, development and integrations guide. The project is MIT-licensed and can be used commercially, including resale/white-label scenarios license, white-label guide.

Constraints and responsibilities

Support is community-based with no SLA, and the operator is responsible for the instance. Updates are manual (a UI button or update.sh), which backs up the database first and targets tagged releases, not main; a rollback via restore.sh only works into an empty database, not over a live one updating guide. The free Supabase plan does not back up automatically, so the README recommends scheduling the backup script. Telemetry via Sentry is opt-in and scrubbed; error reports can include masked recent-session capture unless disabled. The hosting party is the data controller under LGPD, and the maintainers have no access to the database, WhatsApp or storage. A Discord-less community model means issues and discussions are the support channel.

HotRepo's take

Board tracking shows a burst of daily gains in mid-September 2026 and a smaller gain on 2026-10-31; the supplied sample covers only recorded board days, so it indicates attention, not durable adoption or production reliability.