Ping
One bot, a few commands, always awake.
What you get
- DDR5 RAMWhere your bot, its cache and its deps live.512 MB
- NVMe SSDGen4 NVMe for code, dependencies and logs.5 GB
- Shared vCoresRyzen 9700X threads for commands and workers.0.5
- DatabasesFor levels, settings and whatever you persist.1
- BackupsSnapshots you take and roll back yourself.1
- AMD Ryzen 7 9700XThe same 9700X on every plan. No slower tier.
- 24/7 DDoS ProtectionFiltered upstream, always on, never an add-on.
- Instant SetupLive about sixty seconds after payment clears.
- Premium SupportHumans on tickets and Discord. Not a reply bot.
- 99% UptimeProven on a public status page, not just claimed.
Half a gigabyte on the same Ryzen 7 9700X as everything else. Ping exists so a small bot can stop living on your laptop.
This is the plan for the bot you wrote for one server: some slash commands, a welcome message, maybe a reaction role handler. A discord.js process idles around 100–150 MB and a discord.py one lower still, so half a gigabyte is genuinely comfortable for that shape of bot.
What you are really buying is uptime. No more restarting because your machine slept, and no more explaining to your server why the bot went offline when you closed your laptop.
It is not a music plan. Audio streaming through ffmpeg or Lavalink will use more memory than this plan has on its own, and that is the single most common reason people outgrow it on day one.
What actually runs on it
- A discord.js or discord.py bot on one or two servers
- Slash commands, welcome messages, reaction roles
- A logging or moderation bot with a small database
- A personal project you want online permanently
What it will not run
- Music playback — ffmpeg and Lavalink need more headroom
- Bots caching thousands of members across many guilds
- Several bots sharing one instance
Adding music, or growing past a couple of servers? Slash doubles the memory for $0.75 more.