Cloud VPS 6 GB
Most popularA private music library manager for one collection.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy Beets hosting and run a self-hosted music library manager that tags, organises and catalogs your collection from MusicBrainz data, on your own domain. xCloud starts the pinned LinuxServer image behind a Caddy gateway that asks for a username and password on every request, mounts volumes for config, music and downloads and publishes it over HTTPS. You import music from the command line, not the browser.
Beets is a media library management system for music collectors, released under the MIT licence. Upstream says it catalogs your collection and improves its metadata as it goes, getting tags from MusicBrainz, Discogs and Beatport, fetching album art and lyrics through plugins, checking for duplicates and missing tracks, and offering a web interface plus MPD support. Self-hosted Beets is the option for people who would otherwise tidy their library by hand in a desktop player such as iTunes.
On xCloud the template runs the LinuxServer Beets 2.14.1 image, pinned by digest, behind a Caddy gateway with HTTP Basic Authentication, because the web plugin has no login of its own. Three volumes hold settings and the library database, the organised music, and files waiting to import. The library starts empty and the browser cannot import; you run beet import over SSH. Browser playback returns an error in 2.14.1.
A Beets setup normally means a container, a way to protect a web interface that has no login, volumes for the library, a domain and a certificate before the first import. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick Beets from the OneClick catalog. Choose your domain and server, set a timezone and a username — a strong password is generated for you.
Step 02
One click. We bring up the pinned LinuxServer Beets image with the beets_config, beets_music and beets_downloads volumes mounted, put a Caddy authentication gateway in front of it, and publish the gateway over HTTPS on your domain. Beets itself is not published on the host.
Step 03
Save the password from the protected credentials card and sign in at your HTTPS URL. The library starts empty: copy audio files into the downloads volume, SSH to the server and run beet import /downloads. Imported files are copied into the music volume and appear in the web interface.
Beets runs here as a command-line tagger and library catalog with a browsable web interface on your own domain, behind a password.
Beets catalogs your collection and improves its metadata as it imports; upstream gets metadata from MusicBrainz, Discogs and Beatport, or can guess it from filenames or acoustic fingerprints.
The web interface lists your library and lets you search it and open an item's metadata, over HTTPS.
Beets has no sign-in of its own, so a Caddy gateway puts HTTP Basic Authentication in front of the whole site, including the JSON API, with a generated 32-character password.
The web interface is read-only out of the box, so a signed-in visitor cannot edit or delete library entries. Setting web.readonly to no in config.yaml changes that.
Import runs from the command line with beet import /downloads, copying organized files into the music volume. Upstream plugins add album art, lyrics, genres, ReplayGain levels and duplicate checks.
Settings, the library database and log live on beets_config, organized music on beets_music and incoming files on beets_downloads, and survive an xCloud Restart.
Managed hosting for Beets, so the parts that keep it online are not your problem.
Import a folder of ripped albums, let Beets match them against MusicBrainz and correct titles, artists and track numbers, then review what changed.
Have Beets copy imported files into /music in a consistent layout, while the originals stay in /downloads until you decide to delete them.
Use the duplicate and missing-track checks upstream lists to see which albums are incomplete or stored twice.
Keep a well-tagged library on a volume that another music server can read, with Beets doing the cataloguing and the other tool doing the playback.



Dedicated Cloud VPS sizes, pre-configured for Beets hosting. Pick the one that fits, and resize any time.
A private music library manager for one collection.
$24.99per month
More headroom if Beets sits alongside other media apps.
$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. Beets itself is licensed by its maintainers under the MIT license.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Beets 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.
Beets 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.
Beets is used to get a music collection into order. It imports audio files, matches them against MusicBrainz and other catalogs, fixes the tags, files them into a tidy folder structure and keeps a database of the library. Plugins add album art, lyrics, genres and checks for duplicates or missing tracks.
Yes. Beets is open source under the MIT licence, so there is no licence fee. The xCloud price covers the Cloud VPS and the deployment. Your music collection has to be yours to store, and the disk on the server limits how much you can keep there.
Yes. For Beets Docker hosting the template runs the LinuxServer beets 2.14.1 image, pinned by digest, with three named volumes behind a Caddy Basic Authentication gateway and HTTPS on your domain. Settings live in a config file in the volume, not in environment variables, so you edit that file for plugins.
Beets's manifest floor is 256 MB of RAM, one core and 5 GB of disk. Memory is no concern on the 6 GB tier sold on this page. Disk is the real limit, because the music library, the downloads folder waiting for import and the database all grow with your collection.
The web interface cannot import. Copy audio files into the beets_downloads volume, mounted at /downloads, then connect to the server over SSH and run beet import on that folder as the app user, answering the prompts. Files are copied into /music and appear in the web interface, and the originals stay in /downloads.
Not in version 2.14.1. The web plugin's audio play and download endpoint returns an error, because the upstream plugin resolves library-relative paths against its own install directory. Browsing, searching and metadata work, and the files stay intact in /music. Beets' core job is importing and tagging, not streaming.
The Beets web interface and JSON API have no login of their own, so the template puts a Caddy gateway with HTTP Basic Authentication in front of the whole site, including audio downloads. The username and generated password are on your credentials card. Change them in the Environment editor, then restart.
A Beets backup covers beets_config, beets_music and beets_downloads together. The configuration volume holds the SQLite library database, which records paths into /music, so restoring one without the other breaks the library. Keep copies off-server, remember that music takes space, and test a restore.
Beets 2.14.1 is fixed by tag and digest. Before moving on, back up /config, read the Beets changelog, and choose a later template version. Whatever you edited in config.yaml remains in the volume, because the image writes its default file only the first time it starts.
Not by default, because the web interface is read-only unless you set web.readonly to no. Still, treat anyone with the password as trusted: one Basic Authentication login protects the whole site, including the JSON API, with no separate roles. Use a long password, and add xCloud IP management if you want to limit who can reach the address at all.
Yes. Beets cloud hosting places the app and its gateway on a dedicated Cloud VPS, with your domain and certificate attached. Another provider's server can join as self-managed, deploying the same template from the same dashboard, and you import music over SSH.
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.