Why voice and bots do not belong on shared hosting
Anyone shopping for teamspeak server hosting discord bot setups runs into the same wall: shared hosting cannot do this job. Shared plans run websites, not persistent processes. TeamSpeak needs a daemon listening on UDP port 9987 around the clock, and a Discord bot is a Node.js or Python script that must stay connected to Discord’s gateway forever. The moment shared hosting kills idle processes, your voice server goes silent and your bot goes offline.
That is why the answer for both is a small virtual private server. A VPS gives you root access, a static IP, and processes that run until you stop them. The good news is the requirements are tiny by modern standards: we are talking about workloads that fit comfortably in the smallest VPS anyone sells, which makes this one of the cheapest hosting problems to solve properly (checked 14 Oct 2026).
TeamSpeak: tiny specs, specific ports
TeamSpeak 3 is famously lightweight. The official minimum is 1 GB of RAM and a sliver of disk, and community benchmarks show even 512 MB handling small groups. The free license covers 32 slots, which is plenty for a gaming clan or friend group; larger communities can apply for the free non-profit license at 512 slots. TeamSpeak 6 exists in open beta with a modern client, but TS3 remains the stable production choice.
The fiddly part is networking, not hardware. Open 9987 UDP for voice, 10011 TCP for ServerQuery, and 30033 TCP for file transfers. Run the server as a dedicated non-root user, never as root. The whole install takes about fifteen minutes on Ubuntu: download the server archive, extract it, accept the license, and start it. Set up a systemd service so it survives reboots, because a voice server that does not come back after maintenance is worse than none.
Discord bots: even tinier, always online
A Discord bot is just a script with a websocket connection, and its appetite is almost embarrassingly small. A typical Node.js or Python bot uses a hundred megabytes of RAM doing nothing and maybe double that under load. What it needs is not power but permanence: Discord disconnects bots that drop, and free hosting tiers that sleep after inactivity will get your bot kicked relentlessly.
That permanence requirement rules out the tempting free options. Free tiers that spin down after fifteen idle minutes are fine for a weekend experiment and useless for a bot your server depends on. A five-dollar VPS that never sleeps beats a free tier that naps. Install Node.js or Python, run the bot under a process manager like pm2 or systemd, point it at your bot token, and forget about it.
One security note: your bot token is a password. Never commit it to a public repository; use environment variables. Leaked tokens get hijacked within hours, and a hijacked bot spamming your community is an unpleasant way to learn this lesson.
Teamspeak server hosting discord bot: the setup checklist
Here is the whole job for teamspeak server hosting discord bot duty on a fresh VPS, in order. 1. Point your domain (optional) and note the server IP. 2. Update the OS and create a non-root user for each service. 3. Install TeamSpeak: download the Linux server archive, extract, accept the license, and grab the admin token from first boot. 4. Open firewall ports 9987 UDP, 10011 TCP and 30033 TCP. 5. Create a systemd service so TeamSpeak restarts on boot. 6. Install Node.js or Python, deploy your bot code, and run it under pm2 or systemd with the token in an environment variable. 7. Test from an outside network, not just localhost.
Total hands-on time is under an hour if you have done it once. The VPS hosting overview covers plan choices, and our game server guide goes deeper on voice-adjacent hosting for gaming groups.
Renewal reality: the cheapest honest option
This is refreshingly simple pricing territory. A small VPS is already the cheapest tier, and unlike shared hosting there is no dramatic intro-versus-renewal gap to fear on most VPS lines. What you should check instead: whether the renewal rate is published clearly, and whether you are comfortable with the unmanaged deal.
Unmanaged means updates, firewall rules and backups are your job. For a TeamSpeak server and a bot, that job is about thirty minutes a month once set up. If even that sounds like too much, managed voice hosting exists, but you will pay several times the VPS price for someone else to run the same fifteen-minute install. Check current plan pricing and pick the smallest VPS that fits; you can size up in place later.
When NOT to self-host
Self-hosting voice and bots is easy, but not universally right. If your community already lives on Discord, Discord's own voice channels are free, excellent, and zero maintenance; running TeamSpeak alongside is nostalgia, not engineering. If your bot is mission-critical for a large community, consider a managed bot-hosting platform with redundancy instead of a single VPS that becomes a single point of failure.
And if the words SSH and systemd made your eyes glaze over, that is useful information: pay for managed hosting or recruit the one friend who enjoys this stuff. A neglected VPS running outdated software with open ports is a liability. The right answer is the one you will actually maintain.
| Workload | RAM needed | Key requirement | VPS fit |
|---|---|---|---|
| TeamSpeak 3 (32 slots) | 512 MB - 1 GB | Ports 9987 UDP, 10011 TCP open | KVM 1 easily |
| TeamSpeak (100+ users) | 2 - 4 GB | More bandwidth, MariaDB for large DBs | KVM 2 |
| Discord bot | 100 - 300 MB | Never sleeps, process manager | KVM 1 easily |
| Bot + TeamSpeak together | 1 - 2 GB | Separate users, firewall rules | KVM 1 comfortably |
VPS KVM 2
24-month plan, paid upfront
Renews at $14.99/mo
- 2 vCPU + 8 GB RAM
- 100 GB NVMe storage
- 8 TB bandwidth
- Full root access
- n8n one-click template available
FAQ
No. Shared hosting is built for websites, not for persistent processes. TeamSpeak needs a daemon on UDP port 9987 running constantly, and shared hosts kill long-running processes. You need at least a VPS with root access. The smallest VPS tier is more than enough for both TeamSpeak and Discord bots.
The server itself is nearly free to run: 512 MB of RAM and a single vCPU handle a 32-slot server. Your costs are the VPS itself, which is the smallest tier any host sells, plus your time for setup and updates. There are no per-slot fees on the free license, so a clan voice server is one of the cheapest things you can self-host.
Yes, easily. A Discord bot sips a few hundred megabytes of RAM, and TeamSpeak needs around one gigabyte. A 4 GB VPS runs both with headroom to spare, plus a small website or monitoring on the side. Run them as separate system users and keep their firewall rules independent so one cannot interfere with the other.
Discord bots do not need a domain at all; they connect outbound to Discord's servers. TeamSpeak users can connect by raw IP address. A domain is purely cosmetic for TeamSpeak, though a short memorable hostname is nice for a community. If you want one, any cheap domain works.
Latency, mostly. Voice quality degrades with distance, so pick a VPS location near your players. Hostinger's VPS locations include the US, UK, Germany, France, Netherlands, India, Brazil and others, so choose the closest to your community. A server on the wrong continent turns every conversation into a satellite delay.