Can Slack be self-hosted? What to use instead
Slack has no self-hosted edition. Here is what that means, and the self-hosted team chat options that exist.
The short answer
No. Slack is a hosted service run by Slack. There is no edition you can install on your own server, so your messages and files always live in Slack's cloud, under Slack's plans and prices.
If what you want is to keep chat on a server you control, avoid a per-seat bill, or move off Slack without losing history, you need a different product. The rest of this post lists what exists and how to choose.
Why teams ask
The question usually comes from one of four places:
Cost. Slack charges per person per month, so the bill grows with headcount. Paid plans have been quoted at roughly $7 to $18 per user per month depending on tier and billing; check Slack's pricing page for today's numbers.
Data control. Some teams must keep messages on their own infrastructure, or just prefer to.
Limits. Free workspaces have history and feature limits that push teams to upgrade.
Everything else in one place. Chat is only one of the tools a team pays for. Meetings, docs and tasks are usually separate subscriptions.
Self-hosted team chat options
| Option | What it is | Worth knowing |
|---|---|---|
| Mattermost | Open-source team chat, self-hosted or cloud | Strong on chat and integrations; some features are paid editions |
| Rocket.Chat | Open-source team chat, self-hosted or cloud | Wide channel support; self-hosted or cloud |
| Zulip | Open-source chat built around topics | Topic threading is a different habit from Slack channels |
| Dock | Self-hosted workspace: chat, video meetings, docs, tasks, drive and AI agents in one app | One Node process and one SQLite file; no per-seat fee; younger ecosystem |
What you take on when you self-host
Self-hosting trades a monthly bill for some upkeep. You run the server, keep it updated, set up HTTPS and take backups. For a small team that is usually a modest job, but it is real, and a hosted tool will always have the bigger integration marketplace.
A fair rule: if nobody on the team is comfortable running a small server, stay hosted. If someone is, self-hosting often pays for itself quickly once you pass a handful of seats.
Where Dock fits
Dock is built for teams that want to leave per-seat chat without assembling five tools. It has channels and DMs with threads and search, video meetings in the same app, real-time docs, tables, calendar, tasks and a drive. There is a Lark history import, and an MCP server so AI agents such as Claude Code can read and post in your channels.
It runs as one Node process with one SQLite database file, so moving or backing up is copying a file. There is no per-seat licence; your cost is the server. See Dock vs Slack for a side-by-side, or the Slack alternative page.
How to try a move without risk
Run it beside Slack
Install Dock for one team or project. Keep Slack for everyone else.
Move one channel's worth of habits
Use Dock for meetings and docs first; they are the easiest wins.
Decide with real usage
After two weeks, compare the bill and what the team actually used.
Questions
Is there an official self-hosted Slack?
No. Slack is only offered as a hosted service.
What is the best self-hosted Slack alternative?
It depends on the team. Mattermost and Rocket.Chat are chat-first; Zulip suits topic-heavy discussion; Dock suits small teams that also want meetings, docs and tasks in one app.
Can I import my Slack history?
Dock has a Lark import today. A Slack import is not built; check the roadmap before planning a migration.
Is self-hosted chat cheaper?
Usually, once you pass a few seats, because cost follows your server instead of headcount. You also take on the upkeep.