SSD Nodes Learn Hosting plans →
Guides Matt ConnorBy Matt Connor

Self-hosted Slack alternatives compared

Mattermost, Rocket.Chat, Synapse and Zulip compared on RAM, database, mobile push, SSO, upgrades and licence, using each vendor's own sizing figures.

Which self-hosted Slack alternative should you run

The self-hosted Slack alternatives worth a small team's time are Mattermost, Rocket.Chat, Matrix with Synapse, and Zulip. For an internal team tool on one server, run Mattermost. For a public community, run Zulip. Run Matrix with Synapse when you have to talk to servers other people own, and only then, because federation is the one thing the others cannot copy and it is also the thing that changes your job as an administrator.

Feature lists will not separate these four. They all do channels, threads, search, file uploads and mobile apps. What separates them is what they ask of you every month: memory, a database you have to keep alive, a mobile push path you may not control, and a licence that decides whether the feature you need sits behind a payment. The comparison below runs on those axes, at ten users and at a hundred.

What each of the four actually is

Mattermost is a Go server with a PostgreSQL database. One binary, one database, one configuration file. It behaves like Slack, threads and slash commands included, and it is the least interesting of the four to operate, which is a compliment.

Rocket.Chat is a Node.js application on MongoDB. It carries the widest feature set here, including voice and video calls, and an omnichannel inbox that pulls customer conversations from email and social channels into the same interface. If that inbox is the reason you are looking, weigh it against a dedicated Chatwoot support desk first, because a chat server doing support work is a different job from a chat server doing team work.

Matrix is a protocol, not a product. Synapse is the reference server (Python, PostgreSQL) and Element is the client most people use. This is the only option here where your server can speak to servers you do not run.

Zulip is a Python server (Django plus Tornado) with PostgreSQL, RabbitMQ, memcached and Redis behind it, installed as one unit by its own script. Its model is topics inside channels, so a conversation from Tuesday is still findable on Friday. Version 12.0 landed in April 2026.

How much RAM and which database, at 10 users and at 100

Every number in the chart below comes from the project's own documentation, read again on 27 October 2026. None of it is a measurement of mine and none of it is invented. The basis is the same for every row: the smallest configuration that project publishes, with the database counted when the project sizes it separately.

ChartRAM in the smallest deployment each project documents (vendor figures, October 2026)
The data behind this chart
[
  {
    "label": "Synapse",
    "published_ram_gb": 1,
    "notes": "Synapse install docs: at least 1 GB free RAM if you want to join large public rooms. PostgreSQL is required for production and is not sized."
  },
  {
    "label": "Mattermost",
    "published_ram_gb": 2,
    "notes": "Mattermost requirements: 1 to 1,000 users on 1 vCPU and 2 GB RAM, single server."
  },
  {
    "label": "Zulip",
    "published_ram_gb": 2,
    "notes": "Zulip requirements: under 100 users on 1 CPU, 2 GB RAM and 2 GB swap. 100 users and above needs 2 CPUs and 4 GB."
  },
  {
    "label": "Rocket.Chat",
    "published_ram_gb": 8,
    "notes": "Rocket.Chat requirements: smallest published tier is 4 GiB for the app plus 4 GiB for MongoDB, rated up to 500 concurrent users."
  }
]

The rows are not the same shape, and that is the first useful finding. Synapse's 1 GB is a floor for the Synapse process with a condition attached: the docs ask for at least that much free RAM if you want to join large public rooms. PostgreSQL sits outside that figure. Mattermost's 2 GB is a single-server figure that covers 1 to 1,000 users on a single vCPU, though the requirements page does not say whether PostgreSQL shares that server. Zulip documents 2 GB and one CPU below 100 users, plus 2 GB of swap, then 4 GB and two CPUs at 100 users and above. Rocket.Chat publishes the largest number here, 8 GB, because it sizes the application at 4 GiB and MongoDB at 4 GiB, and that tier is rated for up to 500 concurrent users.

At ten users, all 4 of them run on hardware you would not think about twice. At a hundred the answers separate: Mattermost is still inside its 2 GB tier, Zulip wants 4 GB and a second CPU, and Rocket.Chat's smallest documented tier is unchanged at 8 GB, because MongoDB's memory appetite is set by the machine rather than by your user count.

The database choice decides your future upgrades more than your daily performance. Mattermost v12.0, released on 16 October 2026, needs PostgreSQL 15 or newer and drops support for PostgreSQL 14 and earlier; the v11.7 ESR still accepts PostgreSQL 14. Support for MySQL ended with v11.0 in October 2025, so a MySQL install has to migrate to PostgreSQL to stay on a supported release. Synapse runs on SQLite and its own docs say plainly that SQLite is acceptable only for testing, because it performs badly in large rooms. Rocket.Chat 8 requires MongoDB 8.0, which means the database upgrade and the chat upgrade are one project rather than two.

What does a 2 GB VPS really get you

The 2 GB plan is the entry size at most providers, and it is a real answer for two of these four.

  • Mattermost fits. Its vendor documents that exact size for 1 to 1,000 users on a single server, the widest user range any of the four puts on 2 GB. Ten people on 2 GB is comfortable.
  • Zulip fits, with swap. Its vendor documents 2 GB as well, for fewer than 100 users, and requires swap on anything under 5 GB, recommending 2 GB of it. The upgrade docs warn that machines with the minimal RAM can run out of memory during an upgrade, especially when upgrading from Git, and that tools/webpack is generally the step that fails; stopping the server before the upgrade frees the memory. That is a failure you can meet at upgrade time, not at install time.
  • Synapse fits while it is quiet. The idle cost is small. The spike is the problem, and the section on federation below explains where it comes from.
  • Rocket.Chat is the one to avoid at 2 GB, and the cause is MongoDB's storage engine. WiredTiger sizes its internal cache at the larger of 50% of (RAM minus 1 GB) or 256 MB, so on a 2 GB machine the cache may grow to roughly 512 MB alongside Node.js. That figure is a ceiling rather than an upfront reservation, and the cache fills toward it as history grows. The result is not a clean refusal. It installs, it runs, it slows down as history grows, and eventually the kernel out of memory killer stops whichever process was largest at the time.

Check what you actually have before you decide, because providers count RAM differently from free:

free -h
swapon --show

Remember that the chat server is not the only thing on the box. TLS (transport layer security) termination, backups and a container runtime all want memory. Put whichever server you choose behind a reverse proxy you understand, Nginx, Caddy or Traefik, and if you deploy with containers, the Docker Compose basics for a VPS are the part worth getting right first.

Do the mobile apps need your own push server

This is the axis people discover after they deploy, and it is the one that most often decides the answer.

Here is the mechanism. Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM) accept a notification only from whoever holds the signing credentials for that specific app. Your server cannot push to an app you did not build. So a self-hosted chat server using the vendor's App Store build must hand its notifications to the vendor's gateway, and the vendor sets the terms.

  • Mattermost. The free path is the Test Push Notification Service (TPNS). The docs now offer it to non-commercial self-hosted customers only, do not recommend it for production, and say it carries no service level agreement (SLA). It works only with the App Store and Play Store builds. The Hosted Push Notification Service (HPNS) is production grade and is offered to Professional, Enterprise and Cloud customers. The third route is compiling the push proxy yourself, which then requires your own app builds with your own APNs and FCM credentials.
  • Rocket.Chat. Push requires registering the workspace with Rocket.Chat Cloud, and community workspaces are capped at 10,000 push notifications per month. That is about 330 a day for the whole workspace. When the quota is spent, notifications stop arriving until the month resets, which reads to users as the app being broken. The free Starter plan, for up to 50 users, lists push notifications as unlimited.
  • Matrix with Element. Synapse sends notifications to a push gateway, and the official Element apps are pointed at the gateway matrix.org runs at https://matrix.org/_matrix/push/v1/notify. The payload carries the event and room identifiers rather than the message text, and the app fetches the content from your server, so the gateway sees metadata rather than conversations. Running your own Sygnal gateway is supported and means building and distributing your own apps. On Android there is a middle road: UnifiedPush with an ntfy server you host.
  • Zulip. The free self-hosted plan includes the mobile push service for up to 10 users. Above 10 users you need a paid plan, unless your organisation qualifies for free unlimited notifications as a community, open source project, small non-profit or similar group. Zulip 12.0, in April 2026, made end to end encrypted push notifications generally available, switched on when both the server and the app are recent enough.

At ten users every one of these gives you working notifications at no cost, with one exception: a commercial Mattermost install does not qualify for the test service. At a hundred, the picture changes: Zulip requires a paid plan unless your organisation qualifies for free community use, a non-commercial Mattermost keeps working on the test service with no SLA and no support, Rocket.Chat's monthly cap becomes the constraint and its free Community plan is itself documented for up to 100 concurrent users, and Matrix is unaffected because the gateway is free to use.

Which ones give you single sign-on for free

Single sign-on (SSO) is where the open core business model shows itself most clearly.

  • Zulip includes SAML (security assertion markup language) and LDAP (lightweight directory access protocol) in the self-hosted server at no cost. There is no separate tier to buy.
  • Synapse supports OpenID Connect (OIDC), SAML and CAS in its own configuration file, free. Newer deployments increasingly use the Matrix Authentication Service, a separate service with a one way migration from classic Synapse authentication, so plan that move rather than discovering it.
  • Rocket.Chat keeps directory login and SSO out of its free Community plan, but a small team can still get them without paying. Its plans page lists only basic identity management for Community and places Active Directory and LDAP authentication, single sign-on and multi-factor authentication in the Starter plan, which is free and self-managed for up to 50 users. The paid plans are Commercial, Government and Defense. The authentication docs add a deadline: from version 9.0.0, LDAP, SAML and Custom OAuth are available on Starter workspaces and on the paid plans, and not on Community workspaces. A Community workspace that signs users in one of those ways therefore has to move to Starter or a paid plan, or move those users to another login method, before it updates. Version 9.0.0 had not shipped as of 27 October 2026, so treat LDAP and SAML on Community as something you will lose, not something to build on.
  • Mattermost changed its free offer with v11.0 in October 2025. The open source Team Edition no longer has SSO at all: GitLab SSO was removed from it, and it is aimed at teams under 250 activated users. The free Mattermost Entry build does include SAML, AD/LDAP and OpenID Connect, but Mattermost pitches it at teams under 50 users and limits it to the latest 10,000 channel messages in history. Beyond those limits, SSO means a paid plan.

If you plan to run several services behind one login, put a self-hosted Authentik identity provider in front of them and check which of the four can actually talk to it on the licence you hold.

What federation really costs you

Federation is Matrix's reason to exist. Your user joins a room hosted on someone else's server and talks to people whose accounts live there, the way mail servers exchange mail. No other option here does this. If you need it, nothing else on this page is a substitute.

It is also the reason Synapse is a different kind of workload. When your user joins a federated room, your server takes on a copy of that room's state and its events, and it caches the media that users on other servers post: avatars, images and files. Your disk use is then driven by rooms you did not create and by people who do not have accounts on your server. This is why Synapse installs grow a media store far larger than the volume of messages their own users sent. It is also why joining a large public room is the specific operation the docs attach a memory condition to.

Set the retention policy on day one rather than the day the disk fills:

media_retention:
  local_media_lifetime: 90d
  remote_media_lifetime: 14d

Synapse gained media_retention in version 1.61, with separate lifetimes for local and remote media. Remote media is a cache, so if a user asks for a purged file again, Synapse re-requests it from the server it came from. Local media is not a cache, so a short local_media_lifetime deletes your own users' uploads permanently.

The honest summary: if your users only ever talk to each other, federation gives you nothing and charges you disk, bandwidth and a heavier upgrade path. Turn it off, or pick a different server.

How do upgrades go

Zulip is the easiest. One script, and the documented downtime is under 30 seconds unless a large database migration is involved. Install and upgrade look like this, run by you on the server:

cd $(mktemp -d)
curl -fLO https://download.zulip.com/server/zulip-server-latest.tar.gz
tar -xf zulip-server-latest.tar.gz

Run the installer as root. The --push-notifications flag registers the server with the mobile push service during install, and it asks you to accept the terms of service at that moment, so read them before you start.

sudo ./zulip-server-*/scripts/setup/install --push-notifications --certbot \
    --email=YOUR_EMAIL --hostname=YOUR_HOSTNAME

Later upgrades are the same tarball plus one command:

curl -fLO https://download.zulip.com/server/zulip-server-latest.tar.gz
sudo /home/zulip/deployments/current/scripts/upgrade-zulip zulip-server-latest.tar.gz

Mattermost is predictable. Replace the binary, restart, and migrations run at startup. The Extended Support Release (ESR) track ships every 9 months with 12 months of support, and ESR to ESR upgrades are the tested path. Skipping several ESRs at once is supported but not tested, which in practice means you are the one testing it.

Rocket.Chat couples three upgrades together. As of October 2026 the 8.x line is current, with 8.9.0 released on 5 October 2026, and it requires MongoDB 8.0 and a matching Node.js version. Skipping a major version is how people end up with a database the application refuses to open. Before the next major, 9.0.0, check how your users sign in, because that release takes LDAP, SAML and Custom OAuth away from the free Community plan and keeps them only on Starter and the paid plans. The Rocket.Chat Docker Compose install guide pins these together for you, which is the main argument for the container route here.

Synapse needs reading. Every release has upgrade notes, and you must read the notes for each version you pass through, not only the one you land on. After the upgrade, Synapse runs background updates against the database. On a small server these can keep the machine slow for hours, and that is expected behaviour rather than a fault.

Licence terms, in plain words

Mattermost distributes its compiled Team Edition builds under the MIT licence, while the source is offered under AGPLv3 or a commercial licence, with parts of the repository under the Mattermost Source Available License that requires a paid licence to run in production. Rocket.Chat is MIT except for the ee/ directories, which carry their own enterprise licence. Synapse moved from Apache 2.0 to AGPLv3 with version 1.99.0, and contributors sign a CLA that lets Element sell exceptions to that licence. Zulip is Apache 2.0 with no enterprise directory, which is why its SSO story has no asterisk.

The practical reading: AGPL asks something of you when you modify the server and let others use it over a network, or when you pass copies of it on to anyone, modified or not, because the source then has to go with them. Running it unmodified for your own team triggers neither. What matters far more to a small team is the open core line, meaning which features are missing from the free build. Zulip has the fewest, Mattermost has the most.

Which one should you pick

An internal team tool. Mattermost. It covers the widest range of users on a 2 GB machine, has the most boring upgrades, and offers a familiar interface that needs no explaining. Plan for Mattermost Entry or a paid plan on the day SSO becomes a requirement, because that day arrives for most teams and Team Edition no longer offers any SSO.

A community server. Zulip. Topics keep a busy public channel readable months later, SAML and LDAP cost nothing, and upgrading is one command. If your community is closer to posts and replies than to live chat, compare self-hosted forum software first, since a forum indexes better in search and needs no push infrastructure at all. Pick Rocket.Chat instead when you want the voice, video and omnichannel features, and can give it the 8 GB its own documentation asks for.

A network that must interoperate. Matrix with Synapse and Element. Accept the media growth, set retention on day one, give it PostgreSQL and more disk than you think, and get real value from talking to servers you do not control. Choosing Synapse for a team that never federates is paying that cost for nothing.

FAQ

What is the best self-hosted Slack alternative for a small team?

Mattermost, for most internal teams. Its documentation covers 1 to 1,000 users on a single server with one vCPU and 2 GB of RAM, so it fits the entry-size VPS plan that most providers sell. The catch is single sign-on: since v11.0 the open source Team Edition has none, and SAML, AD/LDAP and OpenID Connect come either with a paid plan or with the free Mattermost Entry build, which is aimed at teams under 50 users and limits message history to the latest 10,000 channel messages. If free SSO without those limits matters more than the Slack-like interface, run Zulip instead.

Can I run a self-hosted chat server on a 2 GB VPS?

Mattermost yes, and Zulip yes below 100 users if you add swap, which Zulip's own docs require below 5 GB. Rocket.Chat is the one that will disappoint you, because MongoDB's WiredTiger engine lets its cache grow to the larger of 50% of (RAM minus 1 GB) or 256 MB. On a 2 GB box that means roughly 512 MB can go to the cache as history builds up, on top of the application itself. It will install and then degrade as history grows, ending in an out of memory kill. Rocket.Chat's smallest published tier is 4 GiB for the app plus 4 GiB for MongoDB.

Do self-hosted chat servers need their own mobile push notification server?

Usually no, because Apple's APNs and Google's FCM only accept notifications from whoever signed the app, so the vendor's app uses the vendor's gateway. The terms differ. Mattermost offers non-commercial self-hosted users a free test service with no SLA, and offers a paid hosted service. Rocket.Chat caps community workspaces at 10,000 push notifications per month, after which delivery stops until the month resets. Zulip includes push free for up to 10 users and requires a paid plan above that, unless the organisation qualifies for free community use. Matrix homeservers push through the gateway used by the Element apps at no cost. You only need your own gateway if you also ship your own app builds.

Should I self-host Matrix and Synapse for a team that never talks to other servers?

No. Federation is what Synapse is for, and it is also what makes it heavier to run. Joining rooms on other servers pulls their state and caches their media onto your disk, so storage grows for reasons unrelated to your own users. Set media_retention with a short remote_media_lifetime before that happens. A team that only talks to itself gets the operational cost and none of the benefit, and Mattermost or Zulip will do the same job on less hardware.

Which self-hosted Slack alternative has free single sign-on?

Zulip and Synapse, with no strings attached. Zulip includes SAML and LDAP in the self-hosted server at no cost, and Synapse supports OpenID Connect, SAML and CAS in its configuration, with newer installs moving to the separate Matrix Authentication Service. Mattermost's free Entry build includes SAML, AD/LDAP and OpenID Connect but is aimed at teams under 50 users and limits message history, while its open source Team Edition has had no SSO since v11.0. Rocket.Chat lists only basic identity management on its free Community plan and puts LDAP and single sign-on in its Starter plan, which is free and self-managed for up to 50 users. Its docs also say that from version 9.0.0, LDAP, SAML and Custom OAuth are available on Starter and on the paid Commercial, Government and Defense plans, but not on Community.

Was this article useful?