Team chat hosting for Mattermost, Rocket.Chat and Matrix
Give your team channels, threads, file sharing and calls on a chat server you control. Choose Mattermost for technical and operations teams, Rocket.Chat for chat with omnichannel customer service, or Matrix with Element for encrypted, federated chat. Run it on a HyperDC server, preinstalled as an app option or with our guide.
- Mattermost, Rocket.Chat or Matrix with Element
- Desktop and mobile apps for every platform
- End-to-end encryption and federation with Matrix
- Your messages and files on your own server
- Install
- Packages, Docker Compose or Docker images
- StackMattermost is written in Go with PostgreSQL 14+, Rocket.Chat in Node.js with MongoDB 8, and the Synapse Matrix server in Python with PostgreSQL.
- Go · Node.js and MongoDB · Python
- Default portsClients connect on 443. Mattermost Calls uses 8443 UDP and TCP; Matrix federation uses 8448 unless you delegate it with .well-known.
- 443 · 8443/UDP for calls · 8448 federation
- MinimumRocket.Chat asks for 2 vCPU and 4 GB each for the app and MongoDB. Synapse wants at least 1 GB of free RAM.
- Mattermost: 1 vCPU and 2 GB for up to 1,000 users
- Official docs
- docs.mattermost.com · docs.rocket.chat · element-hq.github.io
- Current release
- Mattermost 11.11 · Rocket.Chat 8.9 · Synapse 1.162
Platforms and features
- Mattermost
- Rocket.Chat
- Matrix
- Element
- Synapse
- Threads
- Voice and video calls
- Bridges
- Webhooks
- Mobile apps
Facts from the project’s official website, documentation and repository, checked in October 2026.
Team chat plans are being prepared
Tell us which platform you prefer and how many people will chat, and our team will reply with the right server. Or start today on a Linux VPS and install Team chat with our guide.
How big a server does team chat need?
Chat itself is light. Files, search history, calls and federation are what grow with your team.
| Feature |
Small team
Up to 25 people
|
Recommended Company
Up to 250 people
|
Large
250+ people or busy federation
|
|---|---|---|---|
| vCPUVirtual processor cores of the server. | 2 | 4 | 8 |
| MemoryMemory for the app, its database and the operating system. | 4 GB | 8 GB | 16 GB+ |
| DiskNVMe or SSD storage for the app, its data and local backups. | 40 GB | 80 GB | 160 GB+ |
| CallsBuilt-in calls suit small groups; large meetings run better on a Jitsi Meet server of their own. | Built-in calls | Built-in calls and Jitsi Meet | Jitsi Meet on its own server |
-
Small team
Up to 25 people
- vCPUVirtual processor cores of the server.
- 2
- MemoryMemory for the app, its database and the operating system.
- 4 GB
- DiskNVMe or SSD storage for the app, its data and local backups.
- 40 GB
- CallsBuilt-in calls suit small groups; large meetings run better on a Jitsi Meet server of their own.
- Built-in calls
-
Recommended
Company
Up to 250 people
- vCPUVirtual processor cores of the server.
- 4
- MemoryMemory for the app, its database and the operating system.
- 8 GB
- DiskNVMe or SSD storage for the app, its data and local backups.
- 80 GB
- CallsBuilt-in calls suit small groups; large meetings run better on a Jitsi Meet server of their own.
- Built-in calls and Jitsi Meet
-
Large
250+ people or busy federation
- vCPUVirtual processor cores of the server.
- 8
- MemoryMemory for the app, its database and the operating system.
- 16 GB+
- DiskNVMe or SSD storage for the app, its data and local backups.
- 160 GB+
- CallsBuilt-in calls suit small groups; large meetings run better on a Jitsi Meet server of their own.
- Jitsi Meet on its own server
From the projects’ requirements: Mattermost lists 1 vCPU and 2 GB of RAM for up to 1,000 users, Rocket.Chat 2 vCPU and 4 GB each for the app and MongoDB, and Synapse at least 1 GB of free RAM. Files and calls add to it.
Team chat that stays inside the company
Decisions, files and incident chats are company knowledge. Keep them on a server you control, with the retention you choose.
Channels and threads
Public and private channels, direct messages and threads keep conversations organised by team, project or incident.
Encryption and federation
Matrix with Element encrypts private rooms end to end and can federate with partner organisations on their own servers.
Calls built in
Mattermost Calls and Element Call add voice, video and screen sharing; run Jitsi Meet next to them for larger meetings.
Integrations
Webhooks, bots and slash commands connect chat to your monitoring, Git server and automation tools such as n8n.
Your data on your server
Customer records, conversations and reports stay on a server you control, in the location you choose.
Root access, your rules
Every Linux VPS, VDS and dedicated server comes with full root access: you choose the versions, the add-ons and the security settings.
Backups included
Free weekly and monthly backups come with every VPS and VDS plan. For data that changes every day, keep copies of your own as well.
Locations on three continents
Run your server in the United States, Europe or Asia, close to the people who use it. The order form estimates the latency from where you are to each location.
Set up team chat in four steps
Order the app preinstalled on your server, or install it yourself with our guide.
-
Choose your server
Pick a VPS, VDS or dedicated server in the size from the table above and the location closest to your users.
-
Install the chat server
Choose it as an app option, or follow our guide: Mattermost from its packages, Rocket.Chat with Docker Compose, or Synapse with Element Web.
-
Add your domain and TLS
Point a subdomain such as app.example.com at the server’s IP address and serve the app over HTTPS with a free Let’s Encrypt certificate.
-
Invite your team
Create the admin account, connect SMTP for invitations, open the ports for calls and federation if you use them, and share the invite link.
Step-by-step setup guides
Install, secure and update the app with our guides, written for current Ubuntu and Debian releases.
-
How to install Docker Engine on Ubuntu 24.04 and 26.04
Install Docker Engine, Buildx and Compose from Docker's official apt repository on Ubuntu LTS, run it without sudo, rotate logs and keep published ports private.
15 min Beginner -
How to set up Caddy as a reverse proxy with automatic HTTPS
Install Caddy from the official repository, point your domains at the server and serve every self-hosted app over HTTPS with a two-line site block, plus headers, password protection, logs and backups.
30 min Beginner -
How to install Mattermost on Ubuntu with PostgreSQL and HTTPS
Set up a self-hosted Mattermost team chat server from Mattermost's apt repository, with PostgreSQL, Caddy for HTTPS and WebSockets, a locked-down sign-up and a tested backup and upgrade routine.
40 min Intermediate
Related solutions
Frequently asked questions
Mattermost, Rocket.Chat or Matrix: which should I choose?
Mattermost for engineering and operations teams who want a Slack-like workspace with many integrations. Rocket.Chat when chat should also handle customer conversations through its omnichannel features. Matrix with Element when you need end-to-end encryption, federation with other organisations or bridges to other chat networks.
Can I import our history from Slack?
Mattermost and Rocket.Chat can import a Slack export with their import tools, including channels, users and messages. Matrix connects to Slack and other networks through bridges instead. Test the import on a staging server first.
How is Mattermost installed for production?
From Mattermost’s packages for Ubuntu, Debian and RHEL or from its tarball, with PostgreSQL 14 or newer and a reverse proxy in front. Mattermost does not support Docker Compose for production, and MySQL is deprecated since version 11.
What does Rocket.Chat need?
Docker Compose with Rocket.Chat and MongoDB 8, set up as a replica set, with ROOT_URL set to your full https address. Rocket.Chat recommends 2 vCPU and 4 GB of RAM each for the app and the database, and Ubuntu 24.04. Never expose MongoDB’s port 27017 to the internet.
What should I know before starting a Matrix server?
The server name becomes part of every user ID and cannot be changed later, so choose it first; with .well-known delegation, IDs can use your main domain while Synapse runs on a subdomain. Use PostgreSQL rather than SQLite, and serve Element Web as the browser client.
Do mobile push notifications work on a self-hosted server?
Yes. Notifications to iOS and Android go through each project’s push gateway, because only the app makers can talk to Apple’s and Google’s push services. Each project documents how to set up its push notifications.
Ready to bring your team chat home?
Tell us what you want to run and for how many people, and we will help you pick the right server.