Host your Discord bot 24/7 (without babysitting a terminal)

Every Discord bot starts the same way: it runs beautifully in a terminal on your PC, right up until you close the lid. Rehosting it somewhere permanent is the moment a project becomes a service - and it needs far less than people think.

What a bot actually needs

Bots are gateway clients, not web servers: they hold one WebSocket to Discord and react to events. That means tiny CPU, modest RAM, no inbound ports at all - a small instance hosts a bot serving thousands of members. What bots do need is what a laptop cannot give: a stable 24/7 network, a process supervisor that restarts them on a crash, and automatic start after host maintenance.

The managed way

Our Discord bot hosting is purpose-built for exactly this: pick your runtime - Node.js, Python, Java, Go, Rust and friends - upload your code, set your token as an environment variable, hit start. Logs stream to the panel, crashes restart automatically, and start/stop/restart also works from the API, so a redeploy can be one line at the end of your CI.

The DIY way

Prefer full control? Any small KVM VPS does the job with a systemd unit:

[Unit]
Description=my-bot
After=network-online.target

[Service]
WorkingDirectory=/opt/my-bot
ExecStart=/usr/bin/node index.js
Restart=always
RestartSec=5
User=bot

[Install]
WantedBy=multi-user.target

Restart=always is the entire secret of "five nines for a hobby project". Add the ten-minute hardening and you are done.

One rule either way

Treat the bot token like a password: environment variable, never in the repository. If it ever leaks, regenerate it in the Discord developer portal first and investigate second. And give your bot a health signal - a heartbeat log line or an Uptime Kuma push - because the only thing worse than a crashed bot is discovering it three days later from an annoyed member.