Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

Discord bot hosting

Canadian hosting for Discord bots

Keep your bot running as a service on a Linux VPS. Plan token storage, restarts, logs and any database it uses.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

Runtime and processes

Check a Discord bot that needs a persistent process, token handling, API rate-limit awareness, logs, restarts, dependency updates, and enough headroom for background work.

02

Data to protect

Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.

03

Network access

List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.

04

Deployment and maintenance

Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.

Field guide

A small process that must never sleep

A Discord bot is a long lived process holding a websocket connection to Discord's gateway, so the hosting requirement is continuity: a process supervisor that restarts it after crashes and reboots, and enough memory for the bot plus its dependency runtime. Most bots run comfortably in a few hundred megabytes.

The failure modes are Discord specific: the token leaks into a public repository, the bot hits gateway rate limits during a reconnect storm, or a library update changes event intents so commands silently stop arriving. Keep the token in an environment variable, enable only the gateway intents your bot uses, and log reconnects and errors to a file you review.

01

Token storage rule

Load the bot token from an environment variable or a secrets file outside the code repository. If a token ever reaches a public commit, reset it in the developer portal immediately.

02

Intent configuration check

Match the privileged gateway intents enabled in the developer portal with the intents requested in code. A mismatch shows up as missing message content or members who never appear.

03

Restart behaviour test

Kill the process once and reboot the server once, and confirm the bot reconnects without manual steps both times. A bot that needs a manual start will eventually be found offline.

Planning

Access, backups and handover

Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.

Free guide

Canadian hosting for Discord bots: planning checklist

Use the detailed checklist to plan setup, access, migration and recovery with your team.

Download PDF →
Help choosing

Tell us about your project.

Send us the software you use, your storage needs and your launch or moving date.

Ask about hosting

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move