Plan 1 of 4
Ping 512 MB Discord bot hosting
One bot, a few commands, always awake.
Half a gigabyte on the same Ryzen 7 9700X as everything else. Ping exists so a small bot can stop living on your laptop.
The specs
What you get with Ping
- DDR5 memory
- 512 MBWhere your bot, its cache and its dependencies live.
- NVMe storage
- 5 GBGen4 NVMe for code, dependencies and logs.
- CPU
- 0.5 vCoresShared Ryzen 9700X threads for commands and workers.
- Databases
- 1For levels, settings and whatever else you save.
- Backups
- 1Snapshots you take and roll back yourself.
- Never sleeps
- Node.js, Python or Java
- DDoS protection
- 24/7 support
- 99% uptime SLA
Is it the right size?
What Ping can run
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.
See SlashIn detail
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.
The whole ladder