Bot 1
Perfect for starter or community bots
One bot, one server
£1.00/mo
billed annually
- 50% CPU Xeon
- 1GB DDR4 RAM
- 5GB SSD storage
- 1 MySQL database
Plans
Discord bot hosting plans
Pick by how much memory your bot needs. Every plan runs 24/7 with no forced sleep, and you can move up at any time without redeploying.
On every plan
No forced sleep
Full SFTP access
Custom start command
Daily backups
DDoS protection
Instant setup
/
Bot 2
Great for multi-purpose or growing bots
Slash commands and music
£2.00/mo
excl VAT
- 150% CPU Xeon
- 2GB DDR4 RAM
- 10GB SSD storage
- 5 MySQL databases
Bot 3
Optimised for large or multi-bot setups
Several bots, one plan
£4.00/mo
excl VAT
- 250% CPU Xeon
- 4GB DDR4 RAM
- 40GB SSD storage
- 10 MySQL databases
Bot 4
Built for high-traffic and premium bots
Thousands of guilds
£10.00/mo
excl VAT
- 500% CPU Xeon
- 8GB DDR4 RAM
- 100GB SSD storage
- 50 MySQL databases
- Semi-managed support
Uptime
A bot that sleeps is a bot that is not there
Free tiers idle your process out after a period of inactivity and cold start it again on the next request, which is exactly when someone runs a command. Here the container simply keeps running.
- EUGameHost container
- Free tier with forced sleep
Scroll the chart sideways to see the full day
-
01
No idle timeout
The container runs continuously. There is no inactivity policy to work around and no keep-alive ping to set up.
-
02
No cold start
A slash command is answered by a process that is already running, not one that has to be woken up first.
-
03
Restarts on your terms
If you want the bot restarted, you schedule it in the panel. Nothing else decides that for you.
Runtimes
Pick the language you already wrote it in
There is one start command field and it takes whatever you type into it. Choose your runtime to see the command and the libraries it is normally used with.
The way most Discord bots are written. Push the project, point the start command at your entry file, and the container runs it exactly the way your machine does.
Startup command
node index.js
- Discord.jsThe reference library. v13 and v14 both run unchanged.
- ErisLighter and closer to the gateway, for bots counting every megabyte.
- Sapphire and other handlersCommand frameworks built on top of Discord.js.
Cogs, slash commands and background tasks behave the same here as they do locally. Point the start command at your module or your script, whichever you use.
Startup command
python3 -m bot
- discord.pyThe original, and still the most common Python library.
- Nextcord and PycordBoth forks run as they are, no changes needed.
- HikariFor bots written against the raw gateway.
Upload the shaded jar and set the heap flag to match the memory on your plan. Nothing else about the command changes between here and your laptop.
Startup command
java -Xmx1G -jar bot.jar
- JDAThe most widely used Java library for Discord.
- Discord4JReactive, for bots built on Project Reactor.
- JavacordA lighter option with a simpler API surface.
Upload the binary you already built and run it. A compiled Go bot is the smallest thing on this page, which is why the £1.00 plan is usually plenty.
Startup command
./bot
- DiscordGoThe standard Go binding for the Discord API.
- DisgordCache-first, for bots holding a lot of guild state.
- Anything elseIf it is a binary and it starts, the start command will run it.
-
One field, your commandChange the entry point whenever you like, no ticket and no redeploy.
-
Secrets stay in the panelDISCORD_TOKEN is an environment variable, not a line in your repository.
-
Push over SFTPUpload the project straight from your editor. No proprietary deploy step.
The panel
This is what you get, not a mock-up
Live console, file manager, schedules, databases, backups and subusers. The same panel that runs our game servers, with a container sized for a bot.
Console
Watch it boot, and type into it
Standard output streams live, and you can send a command straight into the running process. CPU, memory, disk and network sit alongside it.
- Live stdout, no log download required
- Start, restart and stop controls
- CPU, memory and network counters
Live console
Backups
Roll back a bad commit
Files, configs and databases are backed up daily, and you can take one on demand before deploying something you are unsure about.
- Daily automated backups
- Take one on demand before a deploy
- Lock a backup so it cannot be deleted
One-click restore
Subusers
Let a co-maintainer in, carefully
Invite someone by email and tick exactly what they can do. Console access without file access, or file access without the power controls.
- Per-permission access, not all or nothing
- Separate control, file and user rights
- Remove access again in one click
Fine-grained rights
Control
The things you actually do every week
Deploy, restart, read the console, edit a config file, roll back a bad commit. The panel covers all of it, and SFTP is there when you would rather not use a browser.
Deploying
- Full SFTP access, push files directly
- Custom start command for any entry point
- Environment variables kept out of your repo
- Free migration from your current host
Running
- Pterodactyl panel with a live console
- Scheduled restarts from the panel
- Cron tasks for timed jobs
- Package split for several bots on one plan
Storing
- Free MySQL database included
- Daily backups of files and configs
- One-click restore to any of the last 30 days
- NVMe SSD storage behind the container
Protecting
- Cosmic Firewall DDoS filtering
- Your own allocated resources
- Subuser permissions, not shared logins
- 24/7 UK-based support
Platform
What the bot is actually running on
A bot is a long-lived process making a lot of small API calls. It wants consistent CPU, fast disk and a network that is not congested, not a huge instance.
EPYCand Xeon
Consistent CPU
Allocated to you, not borrowed from a pool
24/7
No idle timeout
The process is never stopped for you
10Gbps+
UK uplink
ISO 27001 certified UK data centres
The specification, written down
- Processors
- EPYC and Xeon
- Storage
- NVMe SSD
- Network
- 10Gbps+
- Location
- ISO 27001 certified UK data centres
- Attack filtering
- Cosmic Firewall DDoS protection
- Isolation
- Your bot runs on its own allocated resources
- Support
- 24/7, UK-based
Compare
Against the platforms people usually start on
Most bots begin life on a free tier and then hit the same wall: the process sleeps, there is no file access, and nobody answers when it breaks.
| Feature | EUGameHost | Heroku | Replit | PebbleHost |
|---|---|---|---|---|
| 24/7 UK-based support | Yes | No | No | No |
| Instant bot startup | Yes | No | No | Yes |
| Free backups | Yes | No | No | No |
| Low ping UK hosting | Yes | No | No | Yes |
| Full SFTP access | Yes | No | No | Yes |
| Custom start commands | Yes | Yes | Yes | Yes |
| DDoS protection | Yes | No | No | Yes |
| Package split | Yes | No | No | No |
Also useful: Database hosting UK VPS hosting DDoS protection Game servers
Who it suits
From one moderation bot to a whole fleet
-
Community managers
Keep moderation, welcome and utility bots online 24/7.
-
Bot developers
Test, deploy and scale with full file access and no downtime worries.
-
Multi-bot projects
Use package split to run several bots from one plan.
-
Large bot networks
Handle spikes in users or traffic without slowing down or crashing.