Kerit Cloud

Self-Managed Lavalink

Your Node. Your Rules.

We give you the server. You install, configure, and control Lavalink exactly as you want. Full JVM access, your own plugins, your own application.yml.

View Plans Root SSH access · AMD EPYC NVMe · 14 Global Regions
1 Choose plan & region 2 SSH in — your credentials 3 Upload & run Lavalink
Root full server access
NVMe AMD EPYC storage
100%your config — total control JVM SSH v4 24/7
✦ Self-managed plans

The server is yours.
Do what you want with it.

Root SSH access, AMD EPYC NVMe, DDoS protection. All plans include a pre-configured Ubuntu install and Java 17 ready to go.

Need more resources? ★

Scaling to 500–1,000+ concurrent players? Custom RAM, more vCPUs, private networking, or a dedicated bare-metal node — just ask support and we build it.

Talk to Sales → · Custom billing available
15% Off

Prices auto-convert to your region · conversions are indicative

Basic

Start here

Small Lavalink node for personal bots and testing.

₹49/ month/ year
  • 1 GB RAM
  • 100% CPU (AMD EPYC)
  • 5 GB NVMe SSD
  • Root SSH Access
  • Java 17 Pre-installed
  • Ubuntu 22.04 LTS
  • DDoS Protection
Bandwidth1 TB
Guaranteed Uptime99.9%
Choose Basic

Pro

Most Popular

Plenty of RAM for LavaSrc and a full plugin stack.

₹99/ month/ year
  • 2 GB RAM
  • 150% CPU (AMD EPYC)
  • 10 GB NVMe SSD
  • Root SSH Access
  • Java 17 Pre-installed
  • Ubuntu 22.04 LTS
  • Priority Network
Bandwidth2 TB
Guaranteed Uptime99.9%
Choose Pro

Ultra

High traffic

For public bots with hundreds of simultaneous players.

₹299/ month/ year
  • 4 GB RAM
  • 200% CPU (AMD EPYC)
  • 20 GB NVMe SSD
  • Root SSH Access
  • Java 17 Pre-installed
  • Dedicated Bandwidth
  • Priority Support
Bandwidth5 TB
Guaranteed Uptime99.99%
Choose Ultra

3-day money-back guarantee on all plans · UPI, PayPal & cards accepted · Ubuntu or Debian available on request

Which is right for you?

Managed vs Self-Managed

Two paths, same hardware. Pick managed if you want zero ops overhead. Pick self-managed if you need total control.

Managed

  • Zero setup — credentials delivered ready
  • LavaSrc + SponsorBlock + Lyrics pre-installed
  • Auto-restart, monitoring, and upgrades handled
  • Ideal for devs who just want music working
  • No SSH — config managed by us
  • Custom plugin installs need a ticket
View Managed Plans

Self-Managed

  • Root SSH — full server access
  • Your application.yml, your JVM flags
  • Install any plugin from the Lavalink ecosystem
  • Run multiple Lavalink instances on one server
  • You manage updates and restarts
  • Requires Linux/Java knowledge to set up
View Self-Managed Plans
Quick start

Up in minutes.

SSH in, upload the JAR, drop your config, start. That's the whole setup. Here's a minimal working config to get you going.

“Self-managed gave us full control over LavaSrc and our plugin stack — something no other host let us touch.”

Lead Developer
Mid-size music bot, 40k+ servers
yaml 
# application.yml — place in same directory as Lavalink.jar
server:
  port: 2333
  address: 0.0.0.0

lavalink:
  server:
    password: "youshallnotpass"
    sources:
      youtube: true
      bandcamp: true
      soundcloud: true
      twitch: true
      vimeo: true
      http: true
      local: false
    bufferDurationMs: 400
    youtubePlaylistLoadLimit: 6
    opusEncodingQuality: 10
    resamplingQuality: LOW

metrics:
  prometheus:
    enabled: false
    endpoint: /metrics

logging:
  level:
    root: INFO
    lavalink: DEBUG
# application.yml — plugins block, your own versions
lavalink:
  plugins:
    - dependency: "com.github.topi314.lavasrc:lavasrc-plugin:4.2.0"
      repository: "https://maven.lavalink.dev/releases"
    - dependency: "com.github.topi314.sponsorblock:sponsorblock-plugin:3.0.1"
    - dependency: "dev.lavalink.youtube:youtube-plugin:1.7.2"

# drop custom .jar plugins straight into ./plugins — no rebuild needed
ls ./plugins
lavasrc-plugin-4.2.0.jar  sponsorblock-plugin-3.0.1.jar
# docker-compose.yml
version: "3.9"
services:
  lavalink:
    image: ghcr.io/lavalink-devs/lavalink:4
    container_name: lavalink
    restart: unless-stopped
    ports:
      - "2333:2333"
    volumes:
      - ./application.yml:/opt/Lavalink/application.yml
      - ./plugins:/opt/Lavalink/plugins
    environment:
      _JAVA_OPTIONS: "-Xmx400m"

# Start
docker compose up -d
Full control

Every knob. Your way.

Root access means you configure the entire stack — from JVM flags to plugin JARs to systemd services. No restrictions, no permission requests.

Full JVM Access

Set heap size, choose GC algorithm, add tuning flags. Run on Java 11, 17, or 21 — your choice, your optimisation.

Custom application.yml

Every config option exposed — sources, buffer sizes, encoding quality, prometheus metrics, logging levels, filter settings.

Any Plugin You Want

Drop any JAR from the Lavalink plugin ecosystem into /plugins and restart. LavaSrc, SponsorBlock, custom forks — no approval needed.

Multiple Instances

Run several Lavalink nodes on one server with different ports and configs. Scale horizontally on a single plan with no extra cost.

Custom Monitoring

Enable the Prometheus endpoint and scrape metrics with your own Grafana setup. Full visibility into CPU, memory, players, and track load.

Process Management

Use systemd, PM2, screen, or Docker — manage your own restart policies, log rotation, and process supervision exactly as you prefer.

Global network

14 regions. Place your node
where your bot needs it.

All regions run on AMD EPYC NVMe with up to 10 Gbps uplink. Pick the region closest to your Discord voice servers for minimum audio latency.

🇮🇳MumbaiIndia — South Asia
🇮🇳DelhiIndia — South Asia
🇺🇸VirginiaUSA — East Coast
🇺🇸AshburnUSA — East Coast
🇺🇸Washington DCUSA — Mid-Atlantic
🇺🇸New YorkUSA — Northeast
🇺🇸KansasUSA — Central
🇺🇸Los AngelesUSA — West Coast
🇺🇸MiamiUSA — Southeast
🇨🇦CanadaNorth America
🇩🇪FrankfurtEurope — Central
🇩🇪NurembergEurope — Central
🇸🇬SingaporeAsia — Southeast
🇲🇾JohorMalaysia — Southeast Asia
Frequently asked questions

Self-managed answers

Questions about setup, Linux, Java, or what "self-managed" actually means here. Still stuck? Ask on Discord.

01What does "self-managed" mean exactly?

We give you a clean Linux VPS with Java 17 installed. You upload Lavalink.jar and your application.yml, then start the process. We don't touch your Lavalink config — that's fully yours.

02Do I need Linux experience?

Basic comfort with SSH and the command line is enough. You need to be able to upload files (via SCP or SFTP), navigate directories, and run a Java command. Our quick-start guide walks through every step.

03Can I run other things on the same server?

Yes — it's your VPS. Run a Discord bot, database, web server, or anything else alongside Lavalink. Just be mindful of RAM usage, especially on the Basic plan.

04Which Java version should I use?

Lavalink v4 requires Java 17 or newer. We pre-install Java 17 on all plans. You can install Java 21 yourself if you prefer — it generally offers better GC performance with larger heap sizes.

05How do I add plugins like LavaSrc?

Create a plugins/ folder next to Lavalink.jar, drop the plugin JAR in, add the plugin config to application.yml, and restart. No special permissions or approval needed.

06Can I upgrade from self-managed to managed?

Yes — open a ticket on Discord. We'll migrate you to a managed plan and transfer your credentials and config. Your bot won't need to change its connection settings.

Your node.
Your rules.

[ VIEW PLANS ] root access · 14 regions · AMD EPYC