Discord Bot and Node.js VDS Guide 2026 | SistemDC

If you have built a moderation, music or support bot for your Discord community, the next step is clear: the bot needs to be hosted on a server that runs 24/7 — when your computer shuts down, the bot goes offline. That is why developers choose a Node.js VDS for the job. In this guide we cover setting up an approved bot through the Discord Developer Portal, the discord.js deployment steps, keeping it running with PM2, and choosing a SistemDC Ryzen VDS (9950X infrastructure) plan.

Why Should a Discord Bot Run on a VDS?

Discord bots keep a WebSocket connection open continuously in the background. Problems you run into on a local computer or on free PaaS platforms:

• Uptime: When the PC shuts down the bot goes offline — community moderation stops.
• Performance: CPU throttling on shared free tiers — command latency increases.
• Security: The bot token is at risk on a personal machine; a VDS gives you an isolated environment.
• Scalability: As the number of servers grows, RAM and CPU needs grow too.

A Ryzen VDS (9950X infrastructure) runs the Node.js event loop efficiently thanks to low latency and dedicated vCores. Ping guide: Turkey Location Ping

How Many Resources Does Each Bot Need?

discord.js Setup Steps (Linux VDS)

A typical setup with Ubuntu/Debian on SistemDC Ryzen VDS plans:

1. Discord Developer Portal (discord.com/developers) → New Application → Bot tab → create a Token. Never commit the token to a public repo.
2. Privileged Gateway Intents: Enable Server Members Intent for a moderation bot; Message Content Intent for reading messages (if needed).
3. Node.js LTS: curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash - → apt install nodejs
4. Project: npm init → npm install discord.js dotenv
5. .env file: DISCORD_TOKEN=your_bot_token_here — add it to .gitignore.
6. OAuth2 invite: Developer Portal → OAuth2 → URL Generator → bot scope + the required permissions.

24/7 Uptime with PM2

Use PM2 to restart automatically when the bot crashes:

After a server reboot the bot starts automatically. Follow the logs: pm2 logs discord-bot · Memory limit: pm2 start index.js --max-memory-restart 512M

Bot Token and Server Security

• Keep the token in the .env file; do not upload it to GitHub.
• If the token has leaked, run Reset Token from the Developer Portal — it is invalidated instantly.
• Use SSH key authentication; disable root password login.
• UFW firewall: leave only the SSH port (22) open — a Discord bot uses outbound connections, so no inbound port is needed.
• Stormwall DDoS protection is standard on SistemDC plans: DDoS guide

Node.js API + Discord Bot on the Same VDS

Many projects run the bot together with a web dashboard. Manage the two processes with a PM2 ecosystem file:

For an Express/Fastify API, add a reverse proxy (Nginx) + Let's Encrypt SSL. Webhook endpoints require HTTPS. 2 GB+ of RAM (RYZ-M) is the recommended minimum for this scenario.

Music Bots: A Note on Lavalink

Music bots consume extra RAM/CPU with FFmpeg and a Lavalink node. The bot and Lavalink can run on the same VDS; for 50+ concurrent voice channels consider RYZ-L or a separate Lavalink server. Java-based Lavalink requires JRE 17+ on the server.

Frequently Asked Questions

Windows or Linux for a Discord bot?
Linux (Ubuntu/Debian) is recommended — it uses less RAM and PM2 runs reliably. A Windows VDS is preferred only for .NET bot projects.

Why a VDS instead of free hosting?
Free-tier platforms put the bot to sleep after inactivity; for production community bots, a VDS with guaranteed 24/7 operation is a must.

Does ping matter for a Discord bot VDS?
Bot command latency depends on the gateway ping. For communities in Turkey, the Istanbul location delivers 5–20 ms.

Can multiple bots run on the same VDS?
Yes. With PM2 each bot is a separate process; keep an eye on total RAM. 3–4 small bots run comfortably on RYZ-M.

Related SistemDC Guides

• 9950X Dedicated vs VDS
• Ryzen Game Server
• Linux SSH Security
• Docker Microservices Guide