Run Shack on your own server
A self-hosted Shack runs on a machine you control. Your people, messages, files and database live there; we get no account on it, no key to it and no copy of anything on it. The server sends us nothing.
How you get it
- Order and choose "We host it ourselves". You'll prove your company's domain with one DNS record, and receive a licence key bound to that domain.
- We set up your Shack workspace. Its owner signs in, then opens Admin → Self-hosting. The installer, the step-by-step guide, your licence key and the commands, already filled in for your domain, are there — and only there.
- Shack emails you a read-only registry token separately. The server images are private and shipped compiled: there is no source code in them.
- Run one command on your server. Ten minutes later it's answering on your own address, with HTTPS certificates it fetched itself.
What you'll need
| A Linux server | Ubuntu 22.04 / 24.04 or Debian 12, x86_64 or ARM64. 2 vCPU, 4 GB RAM and 40 GB disk for up to about 50 people. Root or sudo. |
| A hostname | Such as chat.yourcompany.com, with an A record
pointing at the server. |
| Open ports | 80 and 443 for the app, 3478 and a small UDP range for calls. |
Your apps find it on their own
People sign in by typing your Organization ID — your company's domain. The desktop and phone apps look up your server from it, and everything they send travels over HTTPS only. If your team already uses a hosted Shack workspace, its owner can point that workspace at your new server and every installed app follows it the next time it opens.
Already a customer?
Sign in to your workspace and open Admin → Self-hosting. If you don't have a workspace yet, your order page says where things stand.