Plan 3 of 4
Guild 2 GB Discord bot hosting
Music, or a bot that many servers rely on.
Two gigabytes, four databases and three backups. Guild is the smallest plan we would run Lavalink on, and the point where one bot can comfortably serve dozens of servers.
The specs
What you get with Guild
- DDR5 memory
- 2 GBWhere your bot, its cache and its dependencies live.
- NVMe storage
- 20 GBGen4 NVMe for code, dependencies and logs.
- CPU
- 1.5 vCoresShared Ryzen 9700X threads for commands and workers.
- Databases
- 4For levels, settings and whatever else you save.
- Backups
- 3Snapshots 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 Guild can run
What actually runs on it
- A music bot with Lavalink serving several guilds
- A bot across 30–40 servers with real caching
- A bot plus a small web dashboard on the same plan
- An economy or levelling bot with a busy database
What it will not run
- A music bot playing in dozens of voice channels at once
- Several large bots on a single instance
- Heavy media processing like video transcoding
Developer doubles it again to 4 GB with six databases — the plan for running more than one serious bot side by side.
See DeveloperIn detail
Audio is the reason most people arrive here. A Lavalink node plus the bot itself will not fit in a gigabyte once more than one guild is listening, and the symptom of trying is choppy playback that looks like a network problem and is not.
It is equally the caching plan. A bot across thirty or forty servers holds a lot of member and channel state, and two gigabytes is where you stop trading features for sweep intervals.
Four databases and three backups let the pieces stay separate: the bot, its dashboard, a metrics store, a staging copy. That separation is what makes a growing bot maintainable instead of a single fragile process.
The whole ladder