Managed vs Self-Managed Lavalink: Which Should You Choose?

Once you’ve decided your music bot needs Lavalink, the next decision is how to run it. You can manage the node yourself on a server with root access, or have it managed for you. Both use the same software and can run on the same hardware; the difference is who does the work and how much control you keep.

What “managed” means

With managed Lavalink, the provider installs Lavalink, configures the JVM, installs and updates plugins, monitors the node and restarts it if needed. You never SSH into anything. After ordering, you receive a host, port and password to put into your bot’s Lavalink client.

On Kerit Cloud, managed plans include LavaSrc (Spotify, Apple Music, Deezer and more) and SponsorBlock on every tier, add LavaSearch from Premium and the Lyrics plugin from Elite, and allow custom plugins on Apex and Enterprise.

What “self-managed” means

With self-managed Lavalink, you get a clean Linux server with root SSH. You upload Lavalink.jar, write your own application.yml, choose plugins and JVM flags, and handle updates and restarts yourself — typically with systemd, PM2, screen or Docker.

On Kerit Cloud, self-managed plans come with Ubuntu 22.04 LTS and Java 17 pre-installed, so you can start immediately. The provider doesn’t touch your Lavalink configuration.

Side-by-side

The cost comparison

Kerit Cloud’s entry points are close:

Self-managed plans give you more raw vCPU and storage for the money, because you’re doing the operations work. Managed plans cost a little more per resource and include plugins, configuration, updates and monitoring. The real cost difference is your time.

Choose managed if…

• You want music working, not a server to run. You’d rather spend evenings on bot features than JVM flags and plugin updates.
• You’re not comfortable with Linux. No SSH, no systemd, no Java installation.
• The standard plugins cover you. LavaSrc, SponsorBlock, LavaSearch and lyrics handle what most music bots need.
• You want someone else watching it. If the node crashes at 3 am, it’s restarted without you.
• Sources keep changing. Platforms change how they serve media, and source plugins need updating. On a managed node, keeping them current is the provider’s job — a big advantage given how often YouTube support changes (see the YouTube source plugin).

Choose self-managed if…

• You need full control. Custom application.yml settings, particular plugin versions, specific JVM tuning.
• You use unusual plugins or your own forks, and don’t want to wait for approval.
• You want several nodes on one server — different ports and configs for different bots or load balancing.
• You want to run other things alongside, like your bot itself or a database, on the same machine.
• You want your own monitoring — Prometheus metrics into your own Grafana.
• You enjoy operations and are happy to own updates and restarts.

The lead developer of a mid-size music bot with more than 40,000 servers put it this way on our self-managed page: self-managed gave them full control over LavaSrc and their plugin stack.

Hybrid approaches

It doesn’t have to be one or the other:

• Managed for production, self-managed for experiments. Test new plugins and versions on a cheap self-managed node before asking for them on your managed one.
• Start managed, move to self-managed later when your needs become specialised — or the reverse. On Kerit Cloud, you can move from self-managed to managed by opening a ticket; the team migrates your credentials and config, and your bot doesn’t need to change its connection settings.
• Several nodes of different kinds for resilience, which client libraries can balance across. See running multiple Lavalink nodes.

Questions to ask yourself

1. Can I SSH into a server, edit YAML and restart a Java process confidently? If not, managed.
2. Do I need a plugin or setting that isn’t standard? If yes, self-managed (or a higher managed tier that supports custom plugins).
3. Who fixes it when it breaks at night? If the answer should be “not me”, managed.
4. Do I want to run more than Lavalink on this server? If yes, self-managed.
5. Is my time or my money scarcer? Managed saves time; self-managed stretches money.

Summary

Managed and self-managed Lavalink run the same software on the same hardware. Managed trades a little cost for zero operations work: credentials ready in minutes, plugins pre-installed, updates and restarts handled. Self-managed trades your time for complete control: root access, any plugin, your own config and JVM flags, multiple instances and room for other software. Pick managed if you want music to just work, self-managed if you want every knob — and remember you can switch later.