Your bot, running on the same machine as our game servers, with the same console and the same file manager.
Almost every Discord bot is tiny. We would rather sell you the one that fits than invent five tiers to make the middle one look sensible.
Fits the overwhelming majority of bots. Commands, moderation, music for one server.
$3/mo
Billed monthly, cancel anytime
Opening soon — first come, first served
For bots doing real work: many servers, a database, image or audio processing.
$6/mo
Billed monthly, cancel anytime
Opening soon — first come, first served
For a bot that has outgrown one machine's worth of attention: hundreds of servers, heavy media work, or a cache it cannot afford to lose.
$11/mo
Billed monthly, cancel anytime
Opening soon — first come, first served
Prices in USD, billed monthly. No free tier — see below for the honest reason.
| Feature | Flurry | Whiteout | Avalanche |
|---|---|---|---|
| Memory | 512 MB | 1 GB | 2 GB |
| CPU | Up to 0.5 core | Up to 1 core | Up to 2 cores |
| Storage | 5 GB NVMe | 10 GB NVMe | 20 GB NVMe |
| Runtime | Python or Node | Python or Node | Python or Node |
| Availability | Always on | Always on | Always on |
| Backups | Daily, 3 kept | Daily, 3 kept | Daily, 3 kept |
| Price | $3/mo | $6/mo | $11/mo |
If you do not know which you need, take Flurry. A command-and-moderation bot in discord.py or discord.js sits comfortably under 200 MB. Whiteout is for bots that hold a database, process images or audio, or serve a lot of servers at once. Moving up later does not disturb your files.
Our free Minecraft plan works because an empty server sleeps, and a sleeping server costs us almost nothing. A bot cannot sleep — nothing connects to it, and it has to hold its connection to Discord open to hear anything at all. A free bot would mean giving away memory permanently, so we would rather charge $3 than offer a free plan that quietly gets throttled.
A bot token is a full takeover of your bot if it leaks, so it goes in an environment variable rather than in your code. Be aware that anyone you give access to your server in the panel can read it — that is how the panel works, and we would rather you knew than found out. If it ever leaks, regenerate it in the Discord developer portal immediately.
Bots that serve your community: yes. Self-bots, mass-DM tools, token checkers, scrapers, proxies and miners: no, and we will suspend for it without much ceremony. This is not boilerplate — that kind of abuse is the single thing most likely to get this product shut down for everyone.
Either upload it through the file manager in the panel, or give us a public Git URL and we clone it. Dependencies come from your requirements.txt or package.json, installed when the server is built and again whenever you ask for a reinstall.
It gets restarted automatically, and the crash stays in the console log so you can actually read what happened. A bot that dies quietly at 3am and is still dead at lunchtime is the main thing people are paying to avoid.
Straight away, on the status page, and from a person rather than a form letter. Your bot restarts itself if it crashes, and anything needing attention at our end gets it from someone who is already looking at the machine.
Ask us. The plan is a Python or Node process that stays running, so plenty of things fit — a scheduled task, a small worker. What does not fit is anything needing an inbound web address, because we do not offer that yet. Websites are a separate thing we have not built.
You should trust us exactly as far as this page earns it. We are telling you the product is not open, why it is not open, and that we have no uptime guarantee. If a host is willing to be dull and specific about its limits before taking your money, that is usually a better signal than a page full of badges.
Tell us what your bot does and roughly how big it is. We will let you know when we can take it, and say so plainly if it is not a good fit.