SELF-HOSTING
One server. Your server.
Smack runs as a Docker Compose stack on a Linux server you choose: in your office, your data centre or your cloud account. You own the box, the data and the update schedule.
What you need.
| Need | Details |
|---|---|
| A Linux server | 4 vCPU and 8 GB RAM to start; more for larger teams and parallel recordings1 |
| Docker | Docker Engine with the Compose plugin |
| A domain | e.g. chat.yourcompany.com, with TLS at your reverse proxy |
| Storage | MinIO on the same server, or any S3-compatible bucket |
| Email (optional) | Your SMTP server, for invites and notification email |
| Open ports | HTTPS, plus the UDP range for calls (we give you the list) |
WHAT RUNS
Everything in one Compose stack.
webthe Smack app (Next.js)
apibusiness logic (Laravel)
reverbrealtime connections
postgresmessages, users, audit log
redisqueues and presence
miniofiles and recordings (optional if you use your own bucket)
livekitcalls and meetings
egressrecording
coturnthe TURN relay for calls behind firewalls
Install, update, back up.
Install.
Clone the release, set your domain and storage in
.env, thenmake upandmake smack-install. The installer creates your company and the first admin.make upmake smack-installUpdate.
Pull the new release and run
make up. Migrations run automatically. Desktop apps pick up new versions from your server.make upBack up.
Back up the Postgres database and your storage bucket with the tools you already use. That’s all of Smack’s state.
What you own vs. what we do.
You run
- the server and its operating system
- TLS certificates
- backups
- when to update
We provide
- releases and release notes
- an installation service if you want it
- help sizing your server
Questions.
Something else? Talk to us →
Can Smack run without internet access?
It runs on your network. Some features use the internet: Web Push for browser notifications, link previews and email to outside addresses. Talk to us about closed-network setups.
Which Linux distributions work?
Any that runs current Docker Engine with Compose.
Do we get the source code?
Talk to us about your requirements.
Can we use our own Postgres or S3?
Storage, yes: any S3-compatible bucket. The database runs in the stack.
Who updates it?
You do, when you choose. Each release has notes and an upgrade step.
INSTALL ONCE. OWN IT.
Talk to us about sizing, installation and your first day.
Docker Compose · Postgres · your S3 bucket · your domain