Self-Host Mattermost: Team Chat Slack Alternative 2026

TL;DR

Mattermost (MIT, ~31K GitHub stars, Go) is the leading open source Slack alternative for self-hosted teams. Slack charges $7.25/user/month. Mattermost Team Edition is free and includes channels, direct messages, threads, file sharing, search, webhooks, bots, slash commands, and native iOS/Android apps. It's the communication platform used by NASAl, Samsung, and thousands of engineering teams who need to keep data on-premises.

Key Takeaways

• Mattermost: MIT, ~31K stars, Go — Slack alternative with channels, threads, DMs
• Native apps: iOS, Android, Desktop (Windows/Mac/Linux) — all free
• Integrations: Incoming/outgoing webhooks, slash commands, bots, OAuth2
• GitOps integration: Natibe Gitea, GitLab, GitHub notifications and PR previews
• Compliance: Full message export, audit logs, retention policies (Team Edition)
• vs Slack: Mattermost has all core features; Slack wins on third-party app count

---

Mattermost vs Slack vs Rocket.Chat vs Zulip

Feature	Mattermost	Slack	Rocket.Chat	Zulip
License	MIT	Proprietary	MIT	Apache 2.0
GitHub Stars	~31K	—	~40K	~22K
Cost (self-hosted)	Free	$7.25/user/mo	Free	Free
Threads	Yes	Yes	Yes	Yes (topic-based)
Voice/video	Paid only	Yes	Yes	No
Mobile apps	Yes	Yes	Yes	Yes
GitLab/Gitea native	Yes	Via plugin	Via integration	No
Bots/webhooks	Yes	Yes	Yes	Yes
LDAP	Paid (E10)	Yes	Free	Free

---

Part 1: Docker Setup

# docker-compose.yml
services:
  mattermost:
    image: mattermost/mattermost-team-edition:latest
    container_name: mattermost
    restart: unless-stopped
    ports:
      - "8065:8065"
    volumes:
      - mattermost_config:/mattermost/config
      - mattermost_data:/mattermost/data
      - mattermost_logs:/mattermost/logs
      - mattermost_plugins:/mattermost/plugins
      - mattermost_client_plugins:/mattermost/client/plugins
      - mattermost_bleve:/mattermost/bleve-indexes
    environment:
      MM_SQLSETTINGS_DRIVERNAME: "postgres"
      MM_SQLSETTINGS_DATASOURCE: "postgres://mattermost:${POSTGRES_PASSWORD}@postgres:5432/mattermost?sslmode=disable&connect_timeout=10"
      MM_BLEVESETTINGS_INDEXDIR: "/mattermost/bleve-indexes"
      MM_SERVICESETTINGS_SITEURL: "https://chat.yourdomain.com"
      MM_EMAILSETTINGS_SENDEMAILNOTIFICATIONS: "true"
      MM_EMAILSETTINGS_SMTPSERVER: "smtp.yourdomain.com"
      MM_EMAILSETTINGS_SMTPPORT: "587"
      MM_EMAILSETTINGS_SMTPUSERNAME: "${SMTP_USER}"
      MM_EMAILSETTINGS_SMTPPASSWORD: "${SMTP_PASS}"
      MM_EMAILSETTINGS_FEEDBACKEMAIL: "mattermost@yourdomain.com"
    depends_on:
      postgres:
        condition: service_healthy

  postgres:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      POSTGRES_USER: mattermost
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
      POSTGRES_DB: mattermost
    volumes:
      - postgres_data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U mattermost"]
      interval: 10s
      start_period: 20s

volumes:
  mattermost_config:
  mattermost_data:
  mattermost_logs:
  mattermost_plugins:
  mattermost_client_plugins:
  mattermost_bleve:
  postgres_data:

# .env
POSTGRES_PASSWORD=your-secure-db-password

docker compose up -d

Visit http://your-server:8065 → create the admin account.

---

Part 2: HTTPS with Caddy

chat.yourdomain.com {
    reverse_proxy localhost:8065
}

---

Part 3: First-Time Configuration

After creating admin account:

1. System Console → Site Configuration → Site URL: https://chat.yourdomain.com
2. Email settings: Configure SMTP (already set via env vars)
3. Create first team: Name your workspace (e.g., "Engineering Team")
4. Invite users: Team Settings → Invite People → by email or invite link
5. Create channels: #general and #random are auto-created; add project channels

---

Part 4: Incoming Webhooks

Set up webhooks to receive notifications from external services:

1. Integrations → Incoming Webhooks → Add Incoming Webhook
2. Select channel (e.g., #deployments)
3. Copy the webhook URL

# Send a message via webhook:
curl -X POST https://chat.yourdomain.com/hooks/YOUR-WEBHOOK-ID \
  -H "Content-Type: application/json" \
  -d '{"text": "🚀 Deployment to production complete!", "username": "deploy-bot"}'

# With attachment (rich message):
curl -X POST https://chat.yourdomain.com/hooks/YOUR-WEBHOOK-ID \
  -H "Content-Type: application/json" \
  -d '{
    "attachments": [{
      "color": "#36a64f",
      "title": "Build #42 Passed",
      "title_link": "https://ci.yourdomain.com/builds/42",
      "text": "All 347 tests passed in 2m 15s",
      "fields": [
        {"short": true, "title": "Branch", "value": "main"},
        {"short": true, "title": "Commit", "value": "abc1234"}
      ]
    }]
  }'

---

Part 5: Gitea/GitHub Integration

Receive notifications from your Git forge:

Gitea webhook

In Gitea: Repo → Settings → Webhooks → Add Webhook → Gitea

• Payload URL: https://chat.yourdomain.com/hooks/YOUR-WEBHOOK-ID
• Content type: application/json
• Events: Push, PR, Issues — select what you need

Mattermost auto-formats Gitea push events:

[repo] main: alice pushed 3 commits
  • abc1234 fix: resolve login bug
  • def5678 feat: add dark mode

GitHub app plugin

Install from Marketplace: https://chat.yourdomain.com/admin_console/integrations/marketplace Search "GitHub" → install → configure with GitHub personal token

---

Part 6: Bots and Slash Commands

Create a bot account

1. Integrations → Bot Accounts → Add Bot Account
2. Username: deploy-bot
3. Role: Member
4. Copy the access token

# Use the bot token to post messages:
import requests

MATTERMOST_URL = "https://chat.yourdomain.com"
BOT_TOKEN = "your-bot-token"
CHANNEL_ID = "channelid123"

def post_message(text):
    requests.post(
        f"{MATTERMOST_URL}/api/v4/posts",
        headers={"Authorization": f"Bearer {BOT_TOKEN}"},
        json={"channel_id": CHANNEL_ID, "message": text}
    )

post_message("🔴 Production alert: Database CPU > 90%")

Custom slash command

1. Integrations → Slash Commands → Add Slash Command
2. Command: /deploy
3. Request URL: https://your-backend.com/deploy-webhook
4. Response username: deploy-bot

When a user types /deploy staging, Mattermost POSTs to your backend with the command and arguments.

---

Part 7: LDAP / Active Directory (E10 feature)

For enterprises needing SSO — requires Enterprise Edition. For Team Edition, use GitLab/Gitea OAuth2:

environment:
  # GitLab OAuth2 (free):
  MM_GITLABSETTINGS_ENABLE: "true"
  MM_GITLABSETTINGS_SECRET: "${GITLAB_SECRET}"
  MM_GITLABSETTINGS_ID: "${GITLAB_CLIENT_ID}"
  MM_GITLABSETTINGS_AUTHENDPOINT: "https://gitlab.yourdomain.com/oauth/authorize"
  MM_GITLABSETTINGS_TOKENENDPOINT: "https://gitlab.yourdomain.com/oauth/token"
  MM_GITLABSETTINGS_USERAPIENDPOINT: "https://gitlab.yourdomain.com/api/v4/user"

For Authentik OIDC, use the GitLab OAuth2 settings with Authentik endpoints.

---

Part 8: Mobile and Desktop Apps

Mobile (iOS/Android)

1. Install Mattermost from App Store or Google Play
2. + Add Server → https://chat.yourdomain.com
3. Push notifications work via Mattermost's HPNS (push proxy) or self-hosted push server

Self-hosted push notifications

# Add push proxy to docker-compose.yml:
services:
  push-proxy:
    image: mattermost/mattermost-push-proxy:latest
    container_name: mm_push_proxy
    ports:
      - "8066:8066"
    volumes:
      - ./push-proxy.json:/go/src/github.com/mattermost/mattermost-push-proxy/config/mattermost-push-proxy.json

# System Console → Push Notification Server:
environment:
  MM_EMAILSETTINGS_PUSHNOTIFICATIONSERVER: "https://push.yourdomain.com"

---

Maintenance

# Update Mattermost:
docker compose pull
docker compose up -d

# Backup:
docker exec mattermost-postgres-1 pg_dump -U mattermost mattermost \
  | gzip > mattermost-db-$(date +%Y%m%d).sql.gz
tar -czf mattermost-data-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect mattermost_mattermost_data --format '{{.Mountpoint}}')

# Logs:
docker compose logs -f mattermost

# CLI admin commands:
docker exec mattermost mattermost user create --email admin@yourdomain.com --username admin --password secret --system-admin
docker exec mattermost mattermost channel list myteam

Why Self-Host Mattermost?

The case for self-hosting Mattermost 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 Mattermost 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 Mattermost, 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 Mattermost 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 Mattermost 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 Mattermost 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 Mattermost'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 Mattermost 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 Mattermost's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Mattermost'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 Mattermost'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 Mattermost'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 mattermost

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 Mattermost's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

1. Confirm the container is running: docker compose ps
2. Test locally on the server: curl -I http://localhost:PORT
3. If local access works but external doesn't, check your firewall: ufw status
4. 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 mattermost. 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 Mattermost Updated

Mattermost 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 Mattermost 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/categories/communication.

See open source alternatives to Mattermost on OSSAlt.