Order a VPS
Pick Ubuntu or Debian on gc.nano unless you already know you need more RAM. Typical deploy is under 60 seconds.
Discord bots
Always-on Discord bots, billed by the hour.
Keep Python, Node, or Go bots online when the laptop sleeps. Full root, included DDoS mitigation, from $2.50/month.
Why a VPS
A real machine that stays up when Discord does.
Shared bot hosts sleep, throttle, or hide the process behind a panel. A LayerOne VPS is a KVM instance with root, so the gateway connection is yours to keep alive.
No cold starts
systemd or Docker keep the process running across reboots. There is no sleep timer and no platform that freezes the bot when traffic is quiet.
gc.nano covers most bots
A single-process Python, Node, or Go bot usually fits gc.nano at $3/mo. Audio, large caches, or ML inference should start on gc.micro.
DDoS included
Gateway traffic stays protected without a separate mitigation product. L3/L4 mitigation is on for every IP, on every plan.
Your runtime, your deploy
Install the language, the venv, and the unit file you already use. Nothing is locked to a bot-hosting SKU or a one-click template.
How it works
From order to a bot that survives reboot.
Most people are online in a few minutes. The long part is copying the token into the environment file, not waiting on provisioning.
Install the runtime
apt install python3, node, or golang. Create a venv or a directory under /opt and copy the bot in over SSH.
Run it under systemd
A unit file with Restart=always is enough. Docker Compose works the same way if that is already your workflow.
Keep a copy off the box
Take a snapshot or copy the bot and its secrets off the server before an upgrade. The token still lives in your secret store, not only on the disk.
The unit file from step 3
# /etc/systemd/system/discord-bot.service
[Unit]
Description=Discord bot
After=network-online.target
Wants=network-online.target
[Service]
User=discordbot
WorkingDirectory=/opt/discord-bot/app
EnvironmentFile=/etc/discord-bot.env
ExecStart=/opt/discord-bot/venv/bin/python bot.py
Restart=always
RestartSec=5
[Install]
WantedBy=multi-user.targetsudo systemctl daemon-reload
sudo systemctl enable --now discord-bot
journalctl -u discord-bot -fThe token lives in /etc/discord-bot.env with mode 600, not in the repository. The full walkthrough, with the service user and the venv, is Deploy a Discord Bot in 5 Minutes. Harden the server first with Your first hour on a new server.
Plan fit
Start small. Resize when the bot actually needs it.
CPU and RAM decide the plan. Most Discord bots never leave gc.nano.
gc.nano
Single-process bots
Python, Node, or Go workers with modest traffic. The usual first size.
- 1 vCPU
- 1 GB RAM
- 20 GB SAS SSD
gc.micro
Audio, caches, or several bots
Voice, larger in-memory caches, or a few processes on one host.
- 1 vCPU
- 2 GB RAM
- 40 GB SAS SSD
gc.medium
Heavy inference or many shards
ML features, large caches, or a fleet of bots that should not share a gc.nano.
- 4 vCPU
- 8 GB RAM
- 160 GB SAS SSD
Sized example: gc.nano
One Python or Node bot, always on
A single bot process keeps one gateway connection open and waits for events most of the time, so 1 GB of RAM covers the runtime, its dependencies, and routine package upgrades. Move to gc.micro when you add voice, a large in-memory cache, or a second bot.
Deploy gc.nano- 1 vCPU
- 1 GB RAM
- 20 GB SAS SSD
- $3.00/mo ($0.0041/hr)
Need exact specs and order links?
View plans
FAQ
Full FAQ
Frequently asked questions
Straight answers on billing, the platform, and what is included on every plan.
Which plan fits a Discord bot?
gc.nano ($3/mo equivalent) is enough for most Python, Node, or Go bots with modest traffic.
Can I run multiple bots on one VPS?
Yes. Use systemd, Docker, or pm2 to run several processes on the same instance.
Do you block Discord API traffic?
No. Outbound HTTPS to Discord gateways is allowed on all plans.
Ready to deploy a VPS?
Tampa is live. Pick a plan, pick an OS, and the server is online in under a minute.