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.
Discord bot hosting
Keep your bot running as a service on a Linux VPS. Plan token storage, restarts, logs and any database it uses.
Hosting options
Shared hosting for websites, email and PHP applications, with Virtualmin included.
See Web hosting →02Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
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.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
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 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.
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.
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.
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
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour 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.