Your own computer
Fastest for development and testing. The bot disconnects when the computer sleeps, loses internet, updates, or closes the terminal.
Best for: local development
Practical hosting guide
How to host a Discord bot
without guessing.
The host is only one part of the job. A reliable bot also needs reproducible dependencies, protected credentials, correct Gateway intents, a restart plan, and logs you can act on.
Choose a model
Four ways to run the same bot.
There is no universal best host. The right choice depends on how much infrastructure you want to own and what the bot needs to do.
A virtual private server
Flexible and predictable, but you own Linux updates, process supervision, credentials, firewall choices, logs, and deployment automation.
Best for: operators who want control
A general cloud platform
Convenient for many applications, but check whether long-running Gateway connections, sleep policies, storage, and restart behavior fit a Discord bot.
Best for: teams already using the platform
Managed bot hosting
Trades low-level server access for a workflow centered on bot runtimes, secrets, deployments, logs, and keeping one process running.
Best for: shipping the bot, not managing Linux
Step by step
From application token to a verified process.
Create the Discord application
Create an application and bot in the Developer Portal, choose only the permissions and intents it needs, and save the token somewhere private.
Make the project reproducible
For Node.js, commit package.json and its lockfile. For Python, commit requirements.txt or pyproject.toml. Define one clear production start command.
Separate code from secrets
Read credentials from environment variables. Ignore local .env files and rotate any secret that has entered a repository.
Choose a host for a persistent process
Confirm the process can maintain a Gateway connection, restart after failure, expose useful logs, and stay within predictable resource and billing limits.
Verify the production bot
Inspect startup output, confirm the Ready event, test real commands in a private server, and check what happens after a deliberate restart.
What online means
Most event-driven bots maintain a live Gateway connection.
Discord's Gateway is a secure WebSocket connection used to deliver events such as messages, reactions, member changes, and interactions. A traditional bot process remains running so it can receive those events and send heartbeats.
Some interaction-only architectures can use HTTP endpoints instead, but a platform designed for short web requests is not automatically suitable for a long-running Gateway client. Discord's Gateway documentation explains connections, intents, heartbeats, sessions, and identify limits.
Hosting does not replace application correctness. Reconnect storms, missing privileged intents, blocking code, unhandled exceptions, and leaked tokens still need to be fixed in the bot.
Keep reading
Go deeper on the next decision.
bothoster.dev/discord-js-hosting
Hosting a discord.js bot
Prepare a Node.js repository, start script, and token variable.
Read more →bothoster.dev/discord-py-hostingHosting a discord.py bot
Prepare Python dependencies, the entry point, and intents.
Read more →bothoster.dev/guides/keep-discord-bot-online-24-7Keeping a bot online
Design for failures, restarts, health signals, and safe updates.
Read more →Next step
Want the managed path?
BotHoster is building a GitHub-first deployment workflow for Discord bots. Join early access and tell us what your project needs.