How to run a Discord bot 24/7 on a VPS

Why a VPS (not free hosting)

Free tiers and "always-on" hobby platforms tend to sleep idle apps, cap your hours, or change terms. A bot needs to be actually running 24/7. A small VPS gives you a real always-on machine with full control for the price of a coffee — and your bot doesn't share fate with a free platform's policy changes.

How much VPS do you need?

Most bots are light. A 1 GB Starter handles a typical bot comfortably; size up only for big bots, music streaming, or databases. Discord bots make outbound connections to Discord's API, so NAT IPv4 is a non-issue — you don't need a dedicated IP (see NAT IPv4 vs dedicated IP).

Step 1 — Get your VPS & basics

1. Deploy an Ubuntu LTS VPS; root credentials arrive by email in minutes.
2. SSH in (on your dedicated port), create a non-root user, and update: apt update && apt upgrade.
3. Install your runtime — nodejs/npm for a JS bot, or python3/pip/venv for a Python one.

Step 2 — Deploy your bot

Clone your code (git) or upload it, install dependencies (npm install or pip install -r requirements.txt), and put your bot token in an environment variable or a .env file — never hard-code it. Test that it starts and connects.

Step 3 — Keep it alive

You want the bot to restart on crash and on reboot. Two standard ways:

• pm2 (Node, but works for any process): pm2 start bot.js, then pm2 startup and pm2 save so it survives reboots. Great logs and restarts built in.
• systemd (any language): write a small service unit with Restart=always and enable it. The most robust, OS-native option.

Avoid running the bot in a bare screen/tmux long-term — it won't survive a reboot. pm2 or systemd is the right tool.

Step 4 — Maintain

Check logs (pm2 logs or journalctl -u yourbot), keep the system updated, and take a snapshot before big changes. That's it — a bot that's genuinely online 24/7.