Plan 2 of 4 Most popular
Slash 1 GB Discord bot hosting
The plan a real bot starts on.
One gigabyte, two databases and two backup slots. Slash is where a bot stops being a script and starts being a service other people depend on.
The specs
What you get with Slash
- DDR5 memory
- 1 GBWhere your bot, its cache and its dependencies live.
- NVMe storage
- 10 GBGen4 NVMe for code, dependencies and logs.
- CPU
- 1 vCoreShared Ryzen 9700X threads for commands and workers.
- Databases
- 2For levels, settings and whatever else you save.
- Backups
- 2Snapshots 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 Slash can run
What actually runs on it
- A bot across five to ten servers with real caching
- Slash commands with a database behind them
- A single voice connection for light audio
- A moderation bot with logs, warnings and appeals
What it will not run
- A music bot playing in several guilds at once
- A Lavalink node alongside the bot itself
- Bots caching very large member lists
If music is the point, Guild doubles this again and is the smallest plan we would run Lavalink on.
See GuildIn detail
A gigabyte gives a discord.js process room to cache what it needs across a handful of guilds without you tuning sweep intervals. Two databases mean the bot and, say, a dashboard or a second project each get their own rather than sharing a schema.
It is also the first plan where light audio is realistic. A single voice connection through ffmpeg fits here; a music bot serving several guilds at once does not, and pretending otherwise produces stuttering playback rather than an error message.
Two backup slots is the quiet upgrade. Bots accumulate state — economy balances, warning histories, configuration — and losing that is worse than a few minutes of downtime.
The whole ladder