Use a VPS or a managed platform if your Discord bot must stay online around the clock. Shared web hosting normally cannot keep the persistent WebSocket connection that Discord requires. A home server costs little beyond electricity, but outages, reboots and residential internet make it the least reliable option. Managed platforms reduce administration, while a VPS gives you the most control and predictable always-on behavior.
The figures below are vendor-stated estimates rather than independent uptime research. Check the provider’s current pricing, suspension rules and resource limits before paying.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What a Discord bot actually needs from its host
A Discord bot is a long-running application, not a webpage that runs only when someone visits it. It connects to Discord’s Gateway over a WebSocket and keeps that session alive while receiving events and sending commands.
When the connection opens, Discord sends a Hello event (opcode 10) containing a heartbeat interval. Your bot must send heartbeats on that schedule. Discord answers each one with a Heartbeat ACK (opcode 11). If acknowledgements stop arriving, the client should close the socket and reconnect. After the initial handshake, the bot sends Identify (opcode 2), or Resume (opcode 6) when it can continue an interrupted session.
#1 Best Overall
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (8GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
That protocol creates three hosting requirements:
- A process that can run continuously for hours or days.
- Outbound WebSocket access and a network connection that does not terminate idle-looking sessions.
- A way to restart the process after a crash, host reboot or deployment.
HTTP-only hosting, short-lived serverless functions and ordinary scheduled tasks do not meet those requirements by themselves. A webhook can handle a narrow, event-driven integration, but it is not a replacement for a full Gateway bot that listens for events continuously.
Discord bot hosting compared at a glance
| Option | Typical monthly cost | Reliability | Administration | Best use |
|---|---|---|---|---|
| Shared web hosting | Not a practical choice for a Gateway bot | Connection is usually blocked or terminated | Low, but with restrictive runtime rules | Bot website, documentation or control panel only |
| Entry VPS | About $2.50–$5, vendor-stated | Data-center service is often advertised around 99.9% uptime; this is not an independent statistic | Moderate to high: Linux, updates and process supervision are yours | One or several lightweight production bots |
| VPS with backups and monitoring | About $7–$14, vendor-stated estimates | Better recovery and visibility than a bare entry plan | High, but operational work is manageable | Important bots, databases and multiple services |
| Home server | Roughly $1–$3 in electricity per month for one cited setup; hardware and internet are extra | Depends on household power, hardware and ISP | Highest: machine, operating system, router and security | Development, testing and hobby bots |
| Managed or PaaS host | Free tiers may sleep; Discord-focused paid plans start around $2, vendor-stated | Varies by plan; free services commonly suspend idle workloads | Lowest | Fast deployment when you do not want server administration |
No independent survey establishes uptime by hosting type. Treat the percentages and prices as marketing or guide estimates, not guarantees.
Recommended Free Tools
Can you host a Discord bot on shared hosting?
Generally, no. Traditional shared hosting is designed for PHP pages, databases and occasional scripts. Accounts commonly lack a process manager, restrict long-running programs, or kill connections that remain open. A Discord Gateway session therefore disconnects even if the bot works during a brief test.
Some shared plans advertise Node.js or Python support. That label alone is not enough. Before attempting deployment, ask the host whether your plan permits all of the following:
Rank #2
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (4GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- CanaKit Mega Heat Sink - Black Anodized
- A continuously running Node.js, Python or other process without a request triggering it.
- Persistent outbound WebSocket connections.
- Background process supervision and automatic restart.
- Required native packages, voice libraries and sufficient memory.
If any answer is no, use the account for a dashboard or landing page and run the bot elsewhere. Repeatedly using cron to relaunch a killed process is fragile and can violate the provider’s terms.
Why a VPS is the practical 24/7 choice
A virtual private server supplies an always-on Linux instance with shell access, dedicated allocations and control over the runtime. It sits in a data center rather than behind your household router, so a local power cut or Wi-Fi outage does not stop the bot.
Baseline resources for a lightweight bot
Guides commonly quote 1 GB of RAM, one virtual CPU, 20–40 GB of SSD storage and about 1 TB of monthly transfer as a starting point. A quiet moderation or utility bot may use only a fraction of that. Traffic is often modest; one estimate puts a busy bot at roughly 20–100 GB per month, depending on commands, logs, downloads and API usage.
Plan for 2 GB of RAM when the application also runs a database, dashboard, cache or several bots. Music bots need more headroom because audio processing and voice connections are heavier; one guide suggests two CPU cores and 1–2 GB of RAM for a single active voice channel. Actual use depends on the library, codecs and number of simultaneous guilds.
Rank #3
- CanaKit Raspberry Pi 5 Essentials Starter Kit
What the advertised price does and does not include
Entry VPS offers are often cited at $2.50–$5 per month. A production setup with automated backups, monitoring, extra storage or more memory is more realistically estimated at $7–$14. These are vendor-stated ranges captured in guides, not fixed market prices; billing currency, tax, IPv4 fees, backups and overage policies can change the total.
A dedicated IPv4 address is sometimes claimed to be mandatory for the Discord Gateway, but that requirement was not confirmed by Discord’s official documentation. Do not pay for one solely because of that assertion. Ask the provider whether your application needs a public address for another service, such as a web dashboard, and verify the current Discord requirements.
VPS deployment checklist
- Create and harden the server. Choose a current long-term-support Linux image, create a non-root administrator, apply updates and configure a firewall that allows only the services you actually use. The bot normally needs outbound HTTPS and WebSocket traffic; do not open arbitrary inbound ports.
- Install the runtime. Install the version of Node.js, Python or another runtime required by your bot, then copy the application with a private Git repository, secure file transfer or your deployment pipeline. Keep the bot token in environment variables or a secret manager, never in a public repository.
- Install dependencies and test interactively. Run the dependency installer, start the bot in a shell and confirm that it logs in, receives the Gateway Hello, sends heartbeats and receives acknowledgements. Fix intents, permissions and library-version errors before daemonizing it.
- Run it under a supervisor. PM2 and systemd are common choices. Configure automatic startup after reboot, restart on failure, a working directory, environment variables and log handling. A supervisor is more dependable than leaving an SSH terminal open.
- Add observability. Watch memory, CPU, disk space, process restarts and Gateway disconnects. Set an alert for a stopped process and rotate logs so they cannot fill the disk.
- Back up what is irreplaceable. Store database dumps and configuration backups outside the VPS. A snapshot helps recovery from a bad update but is not a substitute for an independently stored backup.
Home server: lowest cash cost, highest dependency on your house
A desktop, mini-PC or Raspberry Pi can run a bot without a hosting bill. The ongoing electricity estimate in one comparison is about $1–$3 per month for a single low-power setup, but hardware purchase, battery backup and internet service make the real cost higher for many households.
The bot is online only while the computer is powered, healthy and connected. A reboot for updates, a sleeping laptop, router failure, ISP outage or a household power cut all become bot downtime. Residential connections can also use changing public addresses or carrier-grade NAT, which complicates any web dashboard or inbound service.
Rank #4
- Includes Raspberry Pi 5 16GB with 2.4Ghz 64-bit quad-core CPU (16GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
Safer home deployment
- Use a machine that can run continuously and disable sleep or hibernation.
- Install security updates and enable a host firewall. Run the bot as an unprivileged user.
- Keep the bot’s outbound connection working without exposing administrative services to the internet.
- If you publish a dashboard, reverse proxy or webhook endpoint, use HTTPS, strong authentication and narrowly scoped router forwarding. Do not expose SSH, database ports or the entire home network.
- Consider a small UPS for the computer and router, and configure automatic startup after power returns.
- Use systemd or another supervisor so the bot restarts after a crash.
One comparison specifically warns that a home server exposes the household’s public IP address. That privacy and attack-surface cost matters even when the bot itself is harmless. For that reason, home hosting is best for development, testing and hobby communities rather than a bot with uptime commitments.
Managed and PaaS hosting
Managed platforms such as Railway, Render and Fly.io can build from a repository, inject secrets and restart an application without requiring you to administer a full Linux server. Discord-focused hosts offer a similar experience with plans reported from about $2 per month.
Read the runtime policy carefully. Free tiers commonly pause services that appear idle, impose sleep timers or produce cold starts. One guide reports suspension after 15 minutes on a free tier, while another warns that sleeping services must boot again before handling work. A sleeping process cannot maintain a Gateway session, so a “free” plan may be unsuitable for a bot expected to respond instantly.
Questions to answer before choosing a managed plan
- Does the service allow a continuously running worker rather than only request-based web processes?
- Will it suspend, restart or throttle the container after inactivity?
- Are outbound WebSockets supported, and are voice connections allowed if the bot needs them?
- How are secrets stored, and can you view application logs and restart history?
- What are the memory, CPU, bandwidth and build limits?
- Is persistent disk included, or must the database live on a separate service?
Managed hosting is usually the best fit when your priority is a quick deployment and minimal server maintenance. A paid always-on worker is more appropriate than a free web tier for a Gateway bot.
Best Value
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (8GB RAM)
- Includes 32GB EVO+ Micro SD Card pre-loaded with 64-bit Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit 45W PD Power Supply for the Raspberry Pi 5
- Display Cable - 6 foot (Supports up to 4K 60p)
How to choose between VPS, managed hosting and home server
Choose a VPS when
- You need predictable 24/7 operation and can administer Linux.
- You want to run a database, dashboard or several bots together.
- You need control over libraries, system packages, process supervision and logs.
Choose managed hosting when
- You prefer Git-based deployment and platform-managed restarts.
- You do not want to patch an operating system or configure a firewall.
- The paid plan explicitly keeps a worker awake and supports your bot’s connections.
Choose a home server when
- You are developing, experimenting or serving a small hobby community.
- Brief outages are acceptable and you already own suitable hardware.
- You understand the privacy and security implications of exposing services from home.
For most production bots, the decision is between a small VPS and an always-on managed worker. Compare total cost, not the headline price: include backups, monitoring, database storage, taxes, bandwidth overages and the time you will spend maintaining the system.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteKeeping a bot online: failure checks and recovery
The bot disconnects repeatedly
Inspect logs for missed Heartbeat ACKs, authentication failures, invalid intents and rate-limit responses. Check host CPU, memory and network loss. A supervisor should restart the process, but repeated restarts usually indicate a configuration or dependency problem that needs fixing rather than a shorter restart interval.
The process stops after deployment
Confirm that the platform treats it as a worker, not a request-triggered web service. On a VPS, check the systemd unit or PM2 process list, environment-variable names and the working directory. On a managed plan, look for sleep, quota or failed-health-check events.
The bot vanishes after a server reboot
Enable the supervisor’s boot-time startup and test it deliberately. A deployment is not complete until the bot returns after a reboot without an SSH session or manual command.
The server runs out of memory or disk
Measure the process before upgrading. Reduce unbounded logs, set rotation, remove unused packages and inspect database growth. Upgrade RAM when garbage collection, swapping or multiple services make restarts frequent; music workloads and several bots can exceed a 1 GB plan quickly.
Bottom-line recommendation
Shared hosting is generally the wrong product for a Discord Gateway bot. Use a managed platform with an explicitly always-on worker if you want the least maintenance, or choose a VPS for control and dependable uptime. Keep a home server for learning, testing and low-stakes communities where household outages are acceptable. Because the cited prices and uptime figures come from vendor material, verify live terms before committing and budget for backups, monitoring and the resources your bot actually consumes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
