Skip to main content

Deploy the Mattermost server

All three deployment methods below install the same Mattermost Server. They differ in how you provision and operate the host, whether high availability is available, and which Mattermost plan you need. Choose one, then follow its install path.

Before you get here, work through Plan to size the deployment, and Prepare to stand up the database, file storage, reverse proxy, and TLS.

Kubernetes

Deploy with the Mattermost Operator. Recommended for production: high availability, rolling upgrades, and infrastructure as code.

Linux

Install directly on a 64-bit Linux host from the APT repository or the release tarball. The most common choice for self-hosted and private-cloud deployments.

Containers

Run Mattermost with Docker Compose. For evaluation, testing, and development only. Not supported for production.

Deployment options​

Kubernetes​

Deploying with the Mattermost Kubernetes Operator is our recommended approach for production, because it offers:

  • High availability and horizontal scaling across multiple app nodes
  • Automated updates and rollbacks
  • Infrastructure as code
  • Built-in monitoring and logging
  • Integration with existing DevOps workflows

The Operator works on any conformant cluster. Mattermost publishes a dedicated guide for Oracle Kubernetes Engine (OKE); guidance for Azure Kubernetes Service has been withdrawn, so deploy on AKS with the Operator as you would on any other cluster.

Linux​

Installing directly on Linux gives you full control over the host and doesn't require a container platform. Choose it when:

  • Containers or Kubernetes aren't available or aren't preferred in your environment
  • You want a straightforward setup on a host you already manage
  • You're deploying into an air-gapped enclave from the release tarball

High availability is available on this path too, but you configure and operate the cluster yourself. See High availability cluster-based deployment.

Install methods: Ubuntu/Debian, RHEL and derivatives, manual tarball, and Azure Native VM from the Azure Marketplace.

Containers​

Docker Compose deployments get a Mattermost instance running quickly without provisioning the infrastructure yourself. Use this path for exploring functionality, testing, and development.

A FIPS-compliant, STIG-hardened variant of every container image is published for regulated environments. See FIPS and STIG container builds.

Don't want to deploy it yourself?​

Third-party and community-maintained solutions can deploy and upgrade Mattermost for you. See Deployment Solution Programs for the recognition tiers and what each commits to.

What's next​

After the server is running: