How to Self-Host Rocket.Chat 2026

Q: When to Choose Rocket.Chat vs Mattermost?

Choose Rocket.Chat if: You run a customer support team (omnichannel is unique to Rocket.Chat) You need a live chat widget for your website You need WhatsApp/email integration in the same platform as internal chat You want a large app marketplace You're running an enterprise with complex compliance requirements Choose Mattermost if: Pure internal team messaging (no customer communication) Simpler setup and lower RAM footprint You prefer PostgreSQL over MongoDB You want a more Slack-identical UX

TL;DR

Rocket.Chat (MIT, ~39K GitHub stars, Node.js/Meteor) is a comprehensive self-hosted messaging platform that goes beyond Slack-style team chat. Its standout feature is omnichannel — a single inbox for customer communications via live chat widget, WhatsApp, email, SMS, Telegram, and more. For pure team messaging: Mattermost is simpler. For teams that also run customer support: Rocket.Chat is unmatched. Community Edition is free; Enterprise Edition adds compliance and advanced omnichannel features.

Key Takeaways

Rocket.Chat: MIT, ~39K stars, Node.js — team chat + omnichannel customer support
Omnichannel: Live chat widget, WhatsApp, email, SMS, Telegram — all in one inbox
Marketplace: 100+ apps and integrations (Jira, GitHub, Trello, Zapier, etc.)
Federation: Connect with Matrix homeservers (experimental) and other Rocket.Chat instances
Mobile apps: iOS and Android (free)
RAM: ~1–2GB — heavier than Mattermost

Rocket.Chat vs Mattermost vs Matrix

Feature	Rocket.Chat CE	Mattermost CE	Matrix + Synapse
License	MIT	MIT	Apache 2.0
GitHub Stars	~39K	~30K	~12K
Omnichannel	Yes (live chat, email, WA)	No	No
Marketplace/Apps	100+	Limited	No
Federation	Matrix (beta)	No	Yes
Video calls	Jitsi integration	Calls plugin	Element Call
E2EE	Yes	Beta	Yes
RAM (idle)	~1–2GB	~500MB	~500MB–1GB

Part 1: Docker Setup

# docker-compose.yml
services:
  rocketchat:
    image: rocketchat/rocket.chat:latest
    container_name: rocketchat
    restart: unless-stopped
    ports:
      - "3000:3000"
    depends_on:
      - mongodb
    environment:
      MONGO_URL: "mongodb://mongodb:27017/rocketchat"
      MONGO_OPLOG_URL: "mongodb://mongodb:27017/local"
      ROOT_URL: "https://chat.yourdomain.com"
      PORT: "3000"
      DEPLOY_PLATFORM: docker

  mongodb:
    image: mongo:6.0
    container_name: rocketchat-mongo
    restart: unless-stopped
    volumes:
      - mongodb_data:/data/db
    command: mongod --oplogSize 128 --replSet rs0
    healthcheck:
      test: echo 'db.runCommand("ping").ok' | mongosh localhost:27017/test --quiet
      interval: 10s

  # Initialize MongoDB replica set (required for Rocket.Chat):
  mongo-init-replica:
    image: mongo:6.0
    restart: on-failure
    command: >
      mongosh --host mongodb:27017 --eval
      "rs.initiate({_id: 'rs0', members: [{_id: 0, host: 'mongodb:27017'}]})"
    depends_on:
      - mongodb

volumes:
  mongodb_data:

docker compose up -d

# Wait for MongoDB replica set to initialize (~30 seconds), then:
docker compose restart rocketchat

Visit https://chat.yourdomain.com → setup wizard.

Part 2: HTTPS with Caddy

chat.yourdomain.com {
    reverse_proxy localhost:3000
}

Part 3: Setup Wizard

Admin Info: Create admin username and email
Organization Info: Company name, size, industry
Site Info: Site name, default language
Server Registration: Skip (or register for push notifications)

Part 4: Channels and Rooms

Room Types

Channel (#general, #engineering): Public group chat
Private Group: Invite-only team channel
Direct Message: 1:1 private chat
Omnichannel Room: Customer-facing live chat

Recommended Setup

#general — Company-wide announcements
#engineering — Engineering team
#random — Off-topic
#ops — DevOps and infrastructure
#customer-support — Via omnichannel inbox

Part 5: Omnichannel — Live Chat on Your Website

Add a live chat widget to your website:

Admin → Omnichannel → Installation
Toggle Enable Omnichannel: On
Livechat → Widget Appearance → customize colors and greeting
Get the embed code:

<script type="text/javascript">
(function(w, d, s, u) {
    w.RocketChat = function(c) { w.RocketChat._.push(c) };
    w.RocketChat._ = [];
    w.RocketChat.url = u;
    var h = d.getElementsByTagName(s)[0],
        j = d.createElement(s);
    j.async = true;
    j.src = u + '/livechat/rocketchat-livechat.min.js?_=201903240000';
    h.parentNode.insertBefore(j, h);
})(window, document, 'script', 'https://chat.yourdomain.com');
</script>

Paste into your website's <body>
Customer messages appear in the Omnichannel → Chats queue

Route Chats to Agents

Omnichannel → Departments → Create department: Sales, Support
Omnichannel → Agents → Assign agents to departments
New chats are automatically routed to available agents

Part 6: Integrations

GitHub Notifications

Admin → Integrations → New → Incoming WebHook
Channel: #engineering
Copy webhook URL
In GitHub → Settings → Webhooks → Add → paste URL
Select events: push, pull requests, issues

# Webhook payload format configured in Rocket.Chat script field:
# Maps GitHub events to Rocket.Chat message format

Jira

Admin → Marketplace → Install Jira Integration (from marketplace):

Connect Jira Cloud or Server
/jira slash commands: /jira create, /jira search, /jira assign

Zapier / n8n

Use Incoming Webhooks to connect Rocket.Chat to any automation:

curl -X POST https://chat.yourdomain.com/hooks/YOUR_HOOK_ID/YOUR_TOKEN \
  -H 'Content-Type: application/json' \
  -d '{"text": "New lead from Typeform: John Smith", "channel": "#sales"}'

Part 7: Video Calls via Jitsi

Admin → Video Conference → Default Provider: Jitsi
Jitsi Domain: meet.jit.si (public) or your self-hosted Jitsi instance
Start a call: Click the camera icon in any channel

For self-hosted Jitsi:

services:
  jitsi-web:
    image: jitsi/web:stable
    # ... (Jitsi has its own full Docker Compose setup)

Part 8: LDAP / OIDC SSO

LDAP (Admin → Workspace → LDAP):

LDAP Host: ldap.yourdomain.com
Port: 636 (LDAPS)
Bind DN: cn=readonly,dc=yourdomain,dc=com
Base DN: dc=yourdomain,dc=com

OIDC/OAuth2 via Authentik: Admin → Workspace → OAuth → Add Custom OAuth:

URL: https://auth.yourdomain.com/application/o/rocketchat/
Client ID + Secret from Authentik
Token endpoint, userinfo endpoint, scope: openid profile email

Maintenance

# Update Rocket.Chat:
docker compose pull
docker compose up -d

# Backup MongoDB:
docker exec rocketchat-mongo mongodump --archive | gzip \
  > rocketchat-backup-$(date +%Y%m%d).gz

# Restore:
cat rocketchat-backup-20260309.gz | docker exec -i rocketchat-mongo mongorestore --archive

# Logs:
docker compose logs -f rocketchat

# Rocket.Chat CLI (admin tasks):
docker exec rocketchat node /app/bundle/programs/server/app.js --help

When to Choose Rocket.Chat vs Mattermost

Choose Rocket.Chat if:

You run a customer support team (omnichannel is unique to Rocket.Chat)
You need a live chat widget for your website
You need WhatsApp/email integration in the same platform as internal chat
You want a large app marketplace
You're running an enterprise with complex compliance requirements

Choose Mattermost if:

Pure internal team messaging (no customer communication)
Simpler setup and lower RAM footprint
You prefer PostgreSQL over MongoDB
You want a more Slack-identical UX

Why Self-Host Rocket.Chat?

The case for self-hosting Rocket.Chat comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Rocket.Chat means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Rocket.Chat, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Rocket.Chat headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Rocket.Chat data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Rocket.Chat without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Rocket.Chat's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Rocket.Chat backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Rocket.Chat's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Rocket.Chat's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Rocket.Chat's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Rocket.Chat's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f rocketchat

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Rocket.Chat's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

Confirm the container is running: docker compose ps
Test locally on the server: curl -I http://localhost:PORT
If local access works but external doesn't, check your firewall: ufw status
If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats rocketchat. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Rocket.Chat Updated

Rocket.Chat follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Rocket.Chat is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See all open source team communication tools at OSSAlt.com/alternatives/slack.

See open source alternatives to Rocket Chat on OSSAlt.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)