Deploy DeskcommCRM

Open-source WhatsApp sales CRM with AI agents, on self-hosted Supabase

Deploy DeskcommCRM

Just deployed

/var/lib/postgresql/data

Just deployed

/data

/app/.sessions

/var/lib/storage

Deploy and Host DeskcommCRM on Railway

DeskcommCRM is an open-source (MIT) sales CRM for businesses that sell over WhatsApp. It combines a shared inbox, sales pipelines, contacts and proposals with AI agents that answer, qualify and follow up leads. It runs on Supabase and connects to WhatsApp through WAHA, as an open alternative to Kommo, Octadesk and Intercom.

About Hosting DeskcommCRM

Self-hosting DeskcommCRM means running the Next.js web app, an AI agent worker and a cron scheduler, plus a full Supabase backend: Postgres, Auth, PostgREST, Realtime, Storage and an API gateway. WhatsApp runs through WAHA, and Redis with an Upstash-compatible REST bridge handles rate limits. Upstream's installer applies a large SQL schema, seeds encryption keys and creates the first owner from a shell. This template does those steps at first boot, generates every secret, keeps the database, uploaded files and WhatsApp sessions on volumes, and makes public sign-up invite-only. You enter your e-mail, and the template creates the owner account from it.

Common Use Cases

  • A shared WhatsApp inbox where a sales team answers, assigns and follows up leads
  • AI agents that reply to customers, qualify leads and schedule follow-ups around the clock
  • Sales pipelines, proposals and cadences for small and medium businesses that sell by chat

Dependencies for DeskcommCRM Hosting

  • Supabase (Postgres 17, Auth, PostgREST, Realtime, Storage), included in the template
  • WAHA for WhatsApp, Redis and an Upstash-compatible REST bridge, included in the template

Deployment Dependencies

Implementation Details

The template deploys 12 services. Two have public domains: DeskcommCRM (the CRM) and Supabase (the API gateway the browser uses for sign-in, data, Realtime and uploads). The gateway serves only the Auth, REST, GraphQL, Realtime and Storage routes; there is no Studio. The first boot takes a few minutes because it applies the schema.

After the deploy, open the DeskcommCRM domain and sign in with OWNER_EMAIL and the generated OWNER_PASSWORD from the DeskcommCRM service's Variables tab. Change the password, then connect WhatsApp by scanning the QR code and add an AI key. Sign-up is invite-only (SIGNUP_MODE=so_convite), and error reports to upstream's Sentry are off. Optional: OWNER_ORG_NAME, APP_LOCALE (pt-BR or es), ANTHROPIC_API_KEY or OPENAI_API_KEY, and SMTP_* or RESEND_API_KEY for e-mail, on DeskcommCRM and Worker. WhatsApp voice calls and the Asterisk phone line need UDP and are not included.

Every service except Redis builds from the template repository, so new DeskcommCRM releases reach you as an update notice in Railway. Read CHANGELOG.md before you apply one.

Why Deploy DeskcommCRM on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying DeskcommCRM on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.


Template Content

More templates in this category

View Template
N8N Main + Worker
Deploy and Host N8N with Inactive worker.

jakemerson
121
View Template
Evolution API with n8n
Automate WhatsApp workflows with Evolution API, n8n, and Postgres.

codestorm
113
View Template
Postgres Backup
Cron-based PostgreSQL backup to bucket storage

Railway Templates
865