All bots online · uptime 99.99%
Discord Bot VPS that keeps discord.py & discord.js online 24/7
Root SSH on a headless Linux box, Node.js and Python preinstalled, pm2 and systemd ready to go. Deploy once, watch pm2 restart your bot in seconds if it ever crashes, and stop worrying about your laptop lid.
9–14 ms
Gateway RTT
< 5 s
Restart time
< 5 min
Deploy
modmail-bot
node · discord.js
music-bot
node · discord.js + lavalink
rank-scraper
python · discord.py
stats-webhook
python · aiohttp
LOAD
0.42
RAM
1.1 / 4 GB
RESTARTS
0
Home PCs weren't built for bots
Every ping, every command, every night: a bot has to be there.
Your bot's users don't care that your ISP hiccupped for 40 seconds or that Windows rebooted for updates. Missed messages, missed slash commands, and silent gateway disconnects are how good bots get uninstalled.
Gateway disconnects
Home connections drop the WebSocket every few hours. Discord's resume window is 3 minutes. Miss it and you lose events until a full re-identify.
Power & sleep
Laptops close. Desktops sleep. A single Windows Update reboot at 2am and your bot is offline until you wake up. VPS uptime doesn't blink.
Static IPs & firewalls
Rate limits, IP-locked webhooks, and OAuth callbacks all assume a stable IP. Residential ISPs rotate yours whenever they feel like it.
Auto-restart, not hope
Bot crashed at 3am? pm2 caught it before your users did.
Every plan ships with pm2 (Node) and systemd (Python) ready to go. Configure once with Restart=always, and a crashed process is back online in under five seconds, with rotated logs and a persistent state you can `pm2 status` whenever you want.
- Auto-restart on crash, memory leak, or exit code
- Persistent across VPS reboots via `pm2 startup` / systemd
- Log rotation and per-bot metrics out of the box
$ pm2 start bot.js --name mybot [PM2] Starting bot.js in fork_mode (1 instance) [PM2] Done. $ pm2 startup [PM2] Init system found: systemd [PM2] Bot will auto-launch on boot. $ pm2 save [PM2] Saving current process list... $ pm2 status ┌────┬──────────┬─────────┬────────┬──────┬──────────┐ │ id │ name │ status │ uptime │ cpu │ mem │ ├────┼──────────┼─────────┼────────┼──────┼──────────┤ │ 0 │ mybot │ online │ 24d3h │ 0.4% │ 182 MB │ └────┴──────────┴─────────┴────────┴──────┴──────────┘
Runtimes
Ship in whatever your bot is written in.
Preinstalled or a single apt-get away. Use nvm, pyenv, or asdf. Your VPS, your toolchain.
Node.js
18 · 20 · 22 LTS
discord.js · Eris · Sapphire
Python
3.10 · 3.11 · 3.12
discord.py · Pycord · Nextcord
Go
1.21 · 1.22
discordgo · Disgord
Rust
stable · nightly
serenity · twilight-rs
Peered with Discord's gateway regions
Sub-15 ms to the AWS regions where Discord's gateway and voice servers actually live, so slash commands feel instant.
New York (NY)
AWS us-east-1 · Discord primary
London (UK)
AWS eu-west-2 · Discord EU
Frankfurt (DE)
AWS eu-central-1 · Discord EU
Singapore (SG)
AWS ap-southeast-1 · Discord APAC
Scale as you grow
From one hobby bot to a sharded public deployment.
01
Single bot, one server
A discord.py bot in 5–20 guilds runs happily on Hobby Bot. 2 GB RAM is plenty for member cache off, and a single Node process keeps things simple.
02
Multiple bots or workers
Add a music bot, a modmail bot, a scraping worker. Community gives you 4 GB and 2 vCPU, and pm2 keeps them all supervised on the same VPS.
03
Sharded & public
Past 2,500 guilds Discord requires sharding. Bot Fleet's 8 vCPU / 16 GB comfortably runs AutoShardingManager + Lavalink + Postgres in a Docker compose.
Pricing
Choose Your Plan
All plans include DDoS protection, full admin access, and 24/7 support.
Basic
Entry-level remote desktop
Standard
Balanced performance
Pro
Most popular choice
Advanced
Heavy workloads
Bot developer FAQ
What discord.py & discord.js devs always ask
Three things break in production: your machine isn't awake at 4am when Discord rate-limits your gateway and your bot needs to reconnect, your home ISP assigns a dynamic IP and occasionally drops the WebSocket for a few seconds (Discord marks that as a disconnect and starts a resume window), and Windows Update decides to reboot on Tuesday. A VPS is a headless Linux box with a static IP, systemd, and 99.99% uptime: the same environment every serious public bot runs on.
Don't use nohup or screen. Use a proper process manager. For Node.js, pm2 gives you `pm2 start bot.js --name mybot`, auto-restart on crash, log rotation, and `pm2 startup` for boot persistence. For Python, a systemd unit file (10 lines) with Restart=always and RestartSec=5 is the standard. Both are preinstalled or one apt-get away on our Linux images.
The VPS itself has 99.99% uptime, but your bot process crashing is up to your code, and that's exactly what pm2 and systemd solve. Combined with a Restart=always policy, a crashed bot is back online in under 5 seconds. We can also help you wire up a simple healthcheck endpoint that Uptime Kuma or Better Stack can ping.
A small bot in 20–50 servers with cached members off runs comfortably in 150–300 MB. Enable member cache or presence intents and that climbs quickly: a bot in 1000 guilds with the members intent typically sits at 800 MB–1.5 GB. Music bots with lavalink push another 200–500 MB per node. Hobby Bot is fine for single-server bots; Community and up start making sense once you're sharded or caching members.
Discord requires sharding above 2,500 guilds. discord.js's AutoShardingManager and discord.py's AutoShardedBot handle the split for you. You just need enough CPU cores and RAM to run multiple gateway connections. Bot Studio and Bot Fleet are the plans where sharding starts being a real workload.
Linux, always. Every deployment tool, every logging pipeline, and Discord's own libraries assume Linux. Our default is Ubuntu 22.04 or Debian 12 with Node.js, Python, and Docker preinstalled. We can provision Windows if you're bridging with a Windows-only game server, but it's the wrong tool for a bot.
Yes. Lavalink is a Java process: install openjdk, drop the jar, run behind systemd. Bot Studio (4 vCPU / 8 GB) handles Lavalink plus a discord.js bot serving music to a dozen guilds. For a public music bot serving thousands of guilds, Bot Fleet with dedicated Lavalink nodes is the right sizing.
Our nodes peer directly with AWS us-east-1, eu-west-2, eu-central-1, and ap-southeast-1, the four regions Discord's gateway and voice servers actually live in. Round-trip is 9–14 ms depending on region, which is what you want for real-time slash commands and voice.
Card payments are online in under 5 minutes. Crypto payments (BTC, USDT, XMR) activate on first confirmation, usually 10–20 minutes. You get root SSH credentials the moment the VM is imaged; `git clone && npm install && pm2 start` and you're live.
Your bot deserves a static IP and a real init system.
Spin up a Linux VPS, git clone, pm2 start, and stop refreshing your bot's dashboard hoping it's still online.
99.99% uptime Peered with Discord's gateway Crypto accepted · no KYC