Built-in cluster server network support for self-hosted servers - let multiple people host the same server to increase uptime

General Discussion
1

I’d like to propose a feature aimed at improving the resilience of self-hosted TeamSpeak servers, particularly for communities that value full ownership of their infrastructure.

The Problem:
Self-hosted TeamSpeak servers have a single point of failure. If the host machine goes down, the entire community loses access until it’s manually restored. For communities that don’t want to rely on paid hosting providers or cloud infrastructure, there’s currently no built-in way to handle this gracefully.

The Idea:
A built-in failover system where designated admins can act as backup server nodes. The core concept is simple — if there’s an admin online, there’s a server available.

How it could work:

Server admins opt in to being failover nodes through the TeamSpeak client or a lightweight background service.

The primary server periodically syncs a snapshot (channels, permissions, config) to these failover nodes.

If the primary becomes unreachable, the highest-priority available node automatically (or manually) spins up a local instance using the latest snapshot.

The TeamSpeak client is aware of the failover pool and can automatically reconnect to the new active node without the user needing to update bookmarks or know a new IP.

The last point is the key piece that would need to be built into the client. A simple fallback list of trusted IPs or addresses — maintained server-side and synced to connected clients — would allow the client to try the next node in the list if the current server becomes unreachable.

Why this matters:
This would be a standout feature for TeamSpeak’s self-hosting story. It leans into what already makes TeamSpeak unique — community ownership and independence from centralized platforms. No other voice platform offers anything like this. It turns every dedicated admin into a piece of the infrastructure, making communities genuinely resilient without needing cloud services, third-party tools, or technical workarounds.

I’d love to hear if this is something the team has considered or would be open to exploring.

2

Every virtual server at the hosting provider has 99.9% availability. It is highly unlikely that a self-created server will be unavailable. Since this is not critical infrastructure, I do not see any use case for failover.

3

You’re right that VPS-hosted servers don’t really need this — datacenter uptime is solid. But this is aimed at true self-hosting, running on hardware at home. Home internet, power outages, PC reboots, ISP IP changes — that stuff happens regularly and you’re nowhere near 99.9% uptime.

It doesn’t need to be critical infrastructure to be worth keeping online. If your community’s server goes down every time someone’s router restarts, that’s a real problem this would solve.

4

This would need pretty much a full redesign of the server and client infrastructure and is not something that is feasible for us to tackle with such a small and niece audience this would target.

3 Likes