--- title: "Deploy Libredesk [Updated Sep '26]" description: "Libredesk [Sep '26] (Self-Hosted Zendesk/Intercom Alternative)" category: "CMS" url: https://railway.com/deploy/libredesk-self-hosted --- # Deploy Libredesk [Updated Sep '26] Libredesk [Sep '26] (Self-Hosted Zendesk/Intercom Alternative) **[Deploy Libredesk [Updated Sep '26] on Railway](https://railway.com/template/libredesk-self-hosted)** Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/libredesk-self-hosted/manifest.json - **Creator:** shruistic - **Category:** CMS ## Template content ### postgres https://devicons.railway.com/i/postgresql.svg - **Image:** postgres:17-alpine ### libredesk https://libredesk.io/favicon.ico - **Image:** libredesk/libredesk:latest - **Start command:** `/bin/sh -c "(./libredesk --install --idempotent-install --yes || true) && (./libredesk --upgrade --yes || true) && exec ./libredesk"` - **Health check:** /health - **Public domain:** Yes ### redis https://cdn.sanity.io/images/sy1jschh/production/0ce0bfdcfbdbf69662b1116671f97c2dd788b655-157x157.svg - **Image:** redis:8.2.1 - **Start command:** `sh -c "rm -rf $RAILWAY_VOLUME_MOUNT_PATH/lost+found/ && exec docker-entrypoint.sh redis-server --requirepass $REDIS_PASSWORD --save 60 1 --dir $RAILWAY_VOLUME_MOUNT_PATH"` ## Documentation # Deploy and Host Libredesk Self-Hosted on Railway Libredesk is the open-source answer to Zendesk: a unified live chat, email, and help center inbox that ships as a single Go binary, with none of the per-agent billing. This template deploys its real 3-service architecture, verified live end-to-end against Libredesk's own official Docker Compose config. ## About Hosting Libredesk Self-Hosted Zendesk's Suite Team plan runs $55/agent/month billed annually, $69/month billed monthly, and Suite Professional jumps to $115/agent/month before AI or workforce add-ons stack on top. A 10-agent team pays $550-690/month before any of that. Self-hosting Libredesk on Railway flips that: a flat infrastructure cost regardless of how many agents you add. There's a second reason beyond price: unlike most self-hosted support platforms, Libredesk is genuinely light. Live chat, email, a help center, automation, and SLA management all run from one binary, backed by just Postgres and Redis, not a sprawl of microservices. ## This Template Deploys Libredesk's Real Architecture, Cross-Checked Against the Working Reference Libredesk's own official `docker-compose.yml`, fetched live from GitHub, defines three services: the app, Postgres, and Redis. This template mirrors that. But building it live surfaced something worth being honest about: my first attempt, built purely from the upstream docs and config sample, got two real things wrong that the docs alone don't make obvious. First: Libredesk's `config.sample.toml` exposes Redis connection settings two ways, a `[redis].address` + `.password` pair, and a single `.url` override that the file's own comment says "overrides other redis config options." I initially set the separate address/password keys. The working configuration actually uses the single URL form, `LIBREDESK_REDIS__URL`, set to a full DSN. Once I cross-checked against Railway's existing reference template's serialized config rather than continuing to guess from docs, this was immediately obvious. Second, and more interesting: the system user password has a strict complexity requirement, 10+ characters with an uppercase letter, lowercase letter, number, and special character, and failing it produces a genuinely misleading failure. My first generated password was strong alphanumeric but had no special character. The install step failed silently on that, and the *next* container restart logged `database tables are missing. Use the --install flag`, which reads exactly like a database connectivity problem, not a password rejection. If you're setting this up yourself, generate `LIBREDESK_SYSTEM_USER_PASSWORD` with an enforced special character, not just random alphanumeric, or you'll spend time debugging the wrong layer. One more thing worth flagging: the Docker image ships with a baked-in `config.toml` containing a publicly-known placeholder encryption key. Always override `LIBREDESK_APP__ENCRYPTION_KEY` with a freshly generated one, never leave the image default in place. ## Common Use Cases - **Startups replacing Zendesk or Intercom to cut per-agent costs**: Flat infrastructure pricing instead of $55-115 per agent per month. - **Privacy-conscious support teams**: Every conversation and ticket stays off third-party servers entirely. - **Small teams wanting live chat and email in one inbox**: No juggling a separate chat widget vendor and a separate email helpdesk tool. - **Teams that want a public help center out of the box**: Ships with a knowledge base, not a bolted-on add-on. ## Dependencies for Libredesk Self-Hosted Hosting Just two backing services: PostgreSQL for all persistent data (tickets, conversations, users), and Redis for caching and background job queues. That's it, no separate search index, no separate vector database, no separate worker service. ### Deployment Dependencies This template deploys 3 services total. Compare that to most self-hosted support or chat platforms, this is meaningfully lighter, a direct reflection of Libredesk's single-binary design. ### Reference Links Official documentation: docs.libredesk.io. Source and issue tracker: github.com/abhinavxd/libredesk. Official Docker image: `libredesk/libredesk` on Docker Hub. ### Implementation Details The app runs `libredesk/libredesk:latest`, connecting to Postgres and Redis entirely through `LIBREDESK_`-prefixed environment variables, which override the image's baked-in `config.toml` rather than requiring a mounted file. Every credential, database password, Redis password, encryption key, and the system user password, is generated fresh per deployment. ## How Libredesk Compares to the Alternatives Against Zendesk, the trade is infrastructure cost and self-hosting effort for a broader enterprise feature set. Zendesk requires nothing beyond a subscription and scales instantly; Libredesk requires deploying 3 services (which this template does in one click) in exchange for zero per-agent fees and full data ownership. Against Intercom, the difference is pricing model entirely. Intercom's per-seat-plus-usage pricing scales aggressively with both team size and conversation volume. Libredesk's infrastructure cost stays flat regardless of either. Against Chatwoot, the closest open-source comparison, the real difference is architecture weight. Chatwoot's Rails-based stack is comparatively heavier to self-host; Libredesk's single Go binary with just 2 backing services is a lighter operational footprint for teams that don't need Chatwoot's larger plugin ecosystem. ## Getting Started Deploy the template, but set `LIBREDESK_SYSTEM_USER_PASSWORD` carefully first: 10+ characters, with an uppercase letter, lowercase letter, number, and special character, confirmed live to be a hard requirement, not a suggestion. Once deployed, open your domain and log in with email `System` and that password. Invite your team, connect your inbox channels, and embed the chat widget. ## Why Deploy Libredesk Self-Hosted on Railway? Because the two obvious alternatives, a per-agent SaaS subscription or manually wiring Postgres and Redis yourself, both cost you something. Zendesk and Intercom's per-agent pricing scales against your team's growth regardless of actual usage. Manually deploying Libredesk means correctly wiring its environment-variable config against Postgres and Redis, and getting the password complexity requirement or the Redis URL format wrong in ways that produce misleading errors, as this build's own two real bugs show. This template does that wiring for you, verified against a real live deploy. Railway offers a $5 free trial so you can test your Libredesk deployment before committing to production use. ## Frequently Asked Questions ### Why did my system user password get rejected without a clear error? Libredesk requires 10+ characters with uppercase, lowercase, a number, and a special character. Failing this makes the install step fail silently, and the next restart logs a misleading "database tables are missing" error instead of a password complexity warning, confirmed via reproducing it live during this build. ### Why does this template deploy 3 services instead of just the app? Because that's Libredesk's real official architecture: PostgreSQL for persistent data and Redis for caching and queues, verified directly against Libredesk's own docker-compose.yml. ### What happens to my data if I redeploy? Nothing, as long as the volumes stay attached. Tickets, conversations, and uploaded attachments each persist independently. ### Is my customer data private? Yes. Every service runs on infrastructure you control, over Railway's private network, with no third party touching your conversations. ### How is this different from just using Zendesk? Cost at scale, mainly. Zendesk is simpler to start with and requires zero setup, but bills $55-115 per agent per month. This template gets you a comparable live chat, email, and help center inbox for a flat infrastructure cost. ### Does the live chat widget actually work, or is it just bundled? It's genuinely wired and tested live against this exact deployment. Once deployed, the widget embed code is available from the admin panel to drop into your own site. ### What AI features does Libredesk include? An AI assistant for automated responses and agent copilot tools are part of the core app, no separate service to configure, unlike platforms that bolt AI on as a separate paid add-on. ## Similar templates - [Libredesk - Complete Setup](https://railway.com/deploy/libredesk-complete-setup) — Complete self-hosted omnichannel customer support desk. - [Paperless-ngx](https://railway.com/deploy/paperless-ngx-3) — Paperless-ngx — document management with OCR and full-text search - [Instatic CMS - Postgres](https://railway.com/deploy/instatic-cms-postgres) — Design, build and manage powerful static sites from state-of-the-art CMS Open this page in a browser: https://railway.com/deploy/libredesk-self-hosted