Slash
The plan a real bot starts on.
What you get
- DDR5 RAMWhere your bot, its cache and its deps live.1 GB
- NVMe SSDGen4 NVMe for code, dependencies and logs.10 GB
- Shared vCoresRyzen 9700X threads for commands and workers.1
- DatabasesFor levels, settings and whatever you persist.2
- BackupsSnapshots you take and roll back yourself.2
- 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.
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.
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.
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.