Cloud VPS 6 GB
Most popularAn audio node for one bot or community.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy Lavalink hosting and run a self-hosted Discord music bot server of your own: a private audio node on your own domain that your bot connects to instead of processing audio itself. xCloud runs the pinned image as a single container, generates the Authorization password, mounts persistent plugin and log volumes and publishes the REST and WebSocket endpoints over HTTPS.
Lavalink is a free, open-source standalone audio sending node for music bots, based on Lavaplayer and Koe and released under the MIT licence. Your bot asks it to load and play audio, and it sends that audio itself, so the audio never reaches your bot's own shards. It offers a REST API, a WebSocket event system, statistics for load balancing, Prometheus metrics and plugin support. Self-hosted Lavalink replaces renting a hosted node.
On xCloud the template runs Lavalink 4.2.2 as a single container, pinned by digest, with no database. It has no web interface: you point a Lavalink client at the HTTPS address, send the generated 32-character password as the Authorization header and open the v4 WebSocket. Plugin files live on lavalink_plugins and logs on lavalink_logs. Voice to Discord uses outbound UDP from the node.
A Lavalink node normally means a Java runtime or container, a config file, a password, volumes, a domain and a certificate before your bot can connect. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick Lavalink from the OneClick catalog. Choose your domain and target server — there are no extra fields to fill in.
Step 02
One click. We bring up the official Lavalink image, pinned by immutable digest, as a single container with no separate database, mount the lavalink_plugins and lavalink_logs volumes, generate the Authorization password, and publish port 2333 over HTTPS on your domain. Give the JVM about a minute to boot.
Step 03
Save the Authorization password shown in the protected installation credentials. In your Lavalink client, use your HTTPS URL, send the password as the Authorization header, and connect to wss://your-domain/v4/websocket with a User-Id header. There is no browser admin to open.
Lavalink runs in full here: an authenticated audio node for your bot, reachable over HTTPS and WebSocket on a server you own.
Lavalink is a standalone audio sending node based on Lavaplayer, so audio is sent without ever reaching any of your shards.
Resolve tracks and control players over REST, and connect clients over the v4 WebSocket endpoint, both published through HTTPS.
Every REST and WebSocket route needs the generated 32-character password: requests without it get 401 and a wrong password gets 403.
The plugins directory is a persistent volume, so extra sources, such as the youtube-source plugin, can be added through environment keys.
Upstream includes Prometheus metrics, and GET /metrics serves read-only JVM and player counters for monitoring.
Upstream lists statistics as a feature, useful for spreading players across more than one node.
Managed hosting for Lavalink, so the parts that keep it online are not your problem.
Offload audio processing from the bot process to a node you control, and let the bot connect to it as a Lavalink client.
Every REST and WebSocket route requires the generated password, and the documented example password is not used.
Install extra sources, for example the youtube-source plugin, through environment keys; plugin JARs stay on a persistent volume across a Restart.
Scrape the metrics endpoint to track player and JVM counters, and use the statistics to decide when a busy bot needs another node.
Dedicated Cloud VPS sizes, pre-configured for Lavalink hosting. Pick the one that fits, and resize any time.
An audio node for one bot or community.
$24.99per month
More headroom for a busy node with many players.
$59.99per month
Every size is a dedicated Cloud VPS we provision, patch, monitor and restore. Billed monthly with no lock-in — delete the server and the unused balance comes back to your account. Lavalink itself is licensed by its maintainers under MIT.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Lavalink on it through the same panel, for a per-server management fee instead of a Cloud VPS rental.
Start your journey without cost.
$0forever
Your rate with 2–5 servers connected.
$5per server / month
The same platform, discounted at 6–10 servers.
$4per server / month
The same platform, discounted at 11+ servers.
$3per server / month
Priced per connected server, so your rate adjusts automatically as you add or remove servers. You pay your own provider for the server itself.
Lavalink on xCloud runs on a dedicated Cloud VPS that we provision, patch, monitor and restore. Deploy faster. Own the server. Stay in control.
Deploy faster using an xCloud Managed Server built with optimized stacks and high-speed SSDs.
Protect your infrastructure with a free SSL certificate and more advanced security features at no additional cost.
From Server creation to application deployment, everything can be managed from our intuitive control panel.
See why agencies, developers, startups, and growing businesses choose xCloud to power their projects.
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising. Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Brian GeovannyI've been with runcloud for the last 3 years. However, after trying xcloud for the last month, I'm switching over. They are on a roll with their setup.
Kevin PinedaI'm moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud! #xCloud #wordpress #hosting
Leo KooHow Cloud Nine Web Elevated Client Experience While Streamlining Hosting Operations using xCloud
Ed EllinghamxCloud is like having an expert server team on call — without the big agency costs. It's given me back my time and given my clients peace of mind. Highly recommended for freelancers and small teams who want reliable performance and security.
Dumitru ButucelxCloud isn't just a solution. It's like one of that friend who got your back when you screw things up pretty bad.
Waqar AhmedTrust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahul SinghSo far my experience has been smooth like silk. I didn't imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included). For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation. I'm sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Massimo VillaCame from cloudways then to runcloud then to xcloud. Looks like I'm staying here.
Gerson ElI've recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud. I have to say, I'm really impressed with xCloud so far! The interface is definitely the standout feature for me.
Tony LewisI came from Cloudways and won't go back. Highly impressed with xCloud. Glad I gave them a chance.
Jared McDowellI like xCloud better than RunCloud, but one thing I'll point out is that some years ago RunCloud was hungry for business, the support was outstanding, and the community was active and helped each other. Maybe it was sold, there was a change in management, or they stopped being hungry, but the quality of the RunCloud offering declined and it hasn't been moving forward quickly. My point is that currently the xCloud team has the edge and it is theirs to keep or lose
David McCanHow Kevin Heinrichs Cut Hosting Costs by 84% While Running WooCommerce & Node.js Sites Efficiently
Kevin HeinrichsI had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
Dan SpinozaDear xCloud Team, I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It's a fantastic service, and my experience so far has been very positive. Successful migrated 5 sites on a single server. Xcloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Rahil MaknojiaCame from runcloud. Tried xcloud and never came back.
Karl FanegaHow Advanced Web Strategies Saved Over $2,000 & Recovered 56 Hours per Month Managing 70+ Client Websites
Gary MoodyxCloud gave me what no other hosting platform could: the flexibility of a VPS with the convenience of managed WordPress. As a solo founder running an entire business on one server, that combination is an important unfair advantage.
Jorge de los Reyes MartínezI use Server Avatar and xCloud and I'll sooner use xCloud than Server Avatar personally.
Jay PaganoHow Newman Web Solutions Ensured Perfect Uptime and Seamless Scaling For 120+ WordPress Sites with xCloud
Lori NewmanI too have moved over to xCloud. It's pretty sweet. One click n8n and uptime Kuma apps
John ApertureI went from Cloudways to xCloud. No intention on switching in the foreseeable future.
Blaine MooreFeel free to contact us with any questions or concerns you may have.
Pick Lavalink in the OneClick catalog, choose a domain and a server, and deploy. xCloud starts the pinned container, generates the Authorization password and publishes the node over HTTPS. Give the JVM about a minute to boot. Voice to Discord uses outbound UDP from the node; no inbound UDP port is published.
Yes. Lavalink is free, open-source software under the MIT licence, so there is no licence fee for the node. On xCloud you pay for the dedicated Cloud VPS it runs on and the deployment around it. Keep upstream's copyright and licence notices if you redistribute the image.
Upstream requires Java 17 LTS or newer for a hand-run JAR. You do not install one here: the pinned 4.2.2 image already contains the runtime and starts Lavalink.jar for you. If you change the image later, check the new release's requirements before you redeploy.
In your Lavalink client, use your HTTPS URL and send the generated password as the Authorization header. WebSocket clients connect to wss://your-domain/v4/websocket and also send a User-Id header. Requests without the password get 401 and a wrong password gets 403.
Yes. For Lavalink Docker hosting this template runs the official ghcr.io/lavalink-devs image, pinned by digest, as one container with its plugin and log volumes mounted. You do not write the compose file, set the password or put a certificate in front of port 2333.
Add plugin coordinates through the LAVALINK_PLUGINS_0_DEPENDENCY environment key, then redeploy. Lavalink downloads the JAR into the lavalink_plugins volume, so it stays after a restart. Environment keys are read on every start, and there is no in-app settings screen.
Not out of the box. The built-in YouTube source is deprecated and switched off in this template, and no youtube-source plugin is installed by default. Upstream lists YouTube stream support through that plugin, so add it with the plugin environment key if your bot needs YouTube.
Lavalink 4.2.2 is pinned by digest, so it only changes when you choose. Read the upstream release notes, back up the plugin volume and your environment values, then bump the tag and digest together through a newer template version. Existing installs are not upgraded by a template change.
A backup is a copy of the lavalink_plugins volume (downloaded plugin JARs) and of lavalink_logs (log files), plus your environment values, including the generated password, kept somewhere safe. There is no database. Do not run docker compose down -v on an installation you want to keep, because it deletes the volumes.
The template manifest asks for 2048 MB of RAM, 1 CPU core and 8 GB of disk. QA measured about 266 MiB idle and 294 MiB after a test round-trip, but a busy node with many players needs more. The 6 GB Cloud VPS sold here covers that.
Yes. For Lavalink cloud use, xCloud sets up a dedicated Cloud VPS, deploys the node and attaches your domain and certificate. Prefer your own hardware or another provider? Attach that machine as a self-managed server and the node deploys onto it.
Yes. There is no lock-in — cancel any time. Hosting is billed monthly and charged for what you actually use, so when you delete the server the unused balance is refunded to your account, less up to 10% in payment-processing fees.
Connect your first server in minutes. No plan you have to grow into.