How to self-host a team chat server: a practical guide

If you have spent any time thinking about where your team's conversations actually live, you have probably arrived at a deceptively simple question: do you want your messages, files, and audit logs on hardware you control, or inside someone else's cloud? Like most things that seem simple on the surface, this is really a decision about trade-offs. And trade-offs are where the interesting thinking begins.

Most people think of self-hosting as something exotic, reserved for the paranoid or the technically obsessive. In practice, the decision is overwhelmingly pragmatic. It is the same reasoning you apply when deciding whether to rent or own a home. When you rent, someone else deals with the boiler and the leaking roof, but you are at the mercy of their schedule, their pricing, and their decision to sell the building out from under you. When you own, you carry the maintenance burden, but the walls are yours and nobody can change the locks.

What it actually means to run your own server

A self-hosted chat server runs on infrastructure you rent or own. In practice this is usually a Linux VM on Hetzner or OVH, sometimes a corporate VMware cluster, occasionally a machine tucked under someone's desk in a server room. Every message, every file, every encryption key stays on that machine. The vendor's job ends at shipping the software and signing updates.

This is fundamentally different from the "private cloud" or "dedicated tenant" model where the vendor still runs the infrastructure. You are renting a fenced-off corner of their garden. Self-hosting means the operational boundary is yours — the freedom and the weight of it.

In 2026, this tends to take one of three shapes. The most common is a single VM — 2 vCPUs, 4 GB of RAM — enough for a 50-person team with voice and video. Postgres and the server live side by side, backups go to object storage. Once you cross about a hundred concurrent users or want high availability without running your own database, you move to a small cluster: two app servers behind a load balancer, Postgres on a managed service.

Then there is a third shape I find particularly interesting — embedded host mode. Some products, TheChatApp among them, let the desktop app run the server inside itself on a laptop, with a QR-code invite. It is specific to very small teams, field deployments, or air-gapped labs, but it removes the server-admin step entirely. There is something elegant about infrastructure as lightweight as the conversation it carries.

The case for keeping the keys

Three outcomes drive most self-hosting decisions. They are worth understanding not as features on a checklist but as expressions of a deeper instinct about control and resilience.

The first is data residency. Your chat history stays on infrastructure you selected, in a region you chose. If your legal team has signed a data-processing agreement that says "data does not leave our server," self-hosting is the only way to mean that literally. No asterisk, no fine print about sub-processors in a data centre you have never heard of. Your machine, your jurisdiction.

The second is cost at scale. This one works like ownership economics in any market. Per-seat cloud pricing is fine when you are small, but past a few dozen people it compounds in a way that feels like a tax on growth. Self-hosted deployments typically carry a one-time licence or an annual fee that does not scale with headcount inside a tier. At fifty or a hundred users the difference is not trivial — it shifts how you think about adding people to a workspace.

The third, and the one I find most underappreciated, is vendor exit. If a vendor changes pricing, kills a product line, or gets acquired by a company whose interests do not align with yours, a self-hosted deployment keeps running. You are not dependent on someone else's quarterly earnings call to read your own messages. In a world where companies pivot, acqui-hire, and sunset products with alarming regularity, there is a quiet power in that.

Where the cloud still makes sense

It would be dishonest to pretend self-hosting is always the right answer. It carries real operational cost, and that cost is not purely financial — it is attentional. You are responsible for backups, OS patches, TLS renewals, disk monitoring, and being the person who gets the call when an upgrade fails at eleven at night. Managed cloud removes all of that in exchange for handing the infrastructure boundary to the vendor. For teams under about fifteen people, or teams without a part-time sysadmin, managed cloud almost always wins on total time cost. Time is the one resource you cannot buy more of.

TheChatApp offers both paths — self-hosted and managed Cloud — built on the same codebase. The product works the same way regardless of which you choose. See pricing for how the two paths split.

What to look for before you commit

If you are evaluating a self-hosted option, a few things are easy to overlook in the excitement of taking control. The installer should be real and documented — a single-file installer or a published Docker Compose stack, not a consulting engagement disguised as a product. Licence terms should be clear about what happens if you stop paying: does the software keep running, or do you lose access to your own messages? End-to-end encryption should be the default, not a premium upsell, because self-hosting with a vendor-readable database gives you data residency but not privacy. And the upgrade path should be versioned — stay on an older release as long as you want, rather than being forced onto the vendor's treadmill.

These seem like small details. They are the details that separate a product built for genuine ownership from one that wears the self-hosted label while keeping the leash short.

Where to start

TheChatApp ships a first-class self-hosted server with a one-time licence and optional annual maintenance. Up to ten users is free. The server runs on Linux, Windows, or macOS, and end-to-end encryption is on by default. If self-hosting is not the right fit, the same product is available as managed Cloud with European hosting.

Take a look at the features overview, review the security documentation, or download the installer and try it on your own infrastructure. The best way to know whether self-hosting is right for you is to experience what it feels like when the server is simply yours.