Cloud VPS 6 GB
Most popularOne address in front of your Jellyfin servers.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy Jellyswarrm hosting and run a self-hosted Jellyfin reverse proxy that merges several Jellyfin servers into one library behind a single address. xCloud starts the pinned image with SQLite, a persistent data volume and HTTPS on your domain, and sets the admin password for the admin UI at /ui. You add your own Jellyfin servers there; no media or Jellyfin server is included, and upstream still calls the project early development.
Jellyswarrm is a reverse proxy, released under the GPL-2.0 licence, that combines multiple Jellyfin servers into one place. Upstream lists unified library access, direct playback from the original server, user mapping across servers, an API that looks like a normal Jellyfin server so existing apps still work, and a user page. It also warns that the project is in early development, with QuickConnect, SyncPlay websockets, audio streaming and bitrate adjustment still in progress. A self-hosted Jellyswarrm suits libraries spread across several locations.
On xCloud the template runs the upstream ghcr.io/llukas22/jellyswarrm 0.3.1 image, pinned by digest, as one container with SQLite in a single volume, jellyswarrm_data. It ships the Jellyfin web client and an admin UI. For each backend you choose Redirect, which sends the client straight to that server, or Proxy, which relays media through this server.
Fronting several Jellyfin servers normally means a container, a persistent volume, an admin password, a domain and a certificate before the first backend is added. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick Jellyswarrm from the OneClick catalog. Choose your domain and target server, and optionally set the admin password (12-64 letters, digits, - or _) — leave it empty and one is generated.
Step 02
One click. We bring up the Jellyswarrm 0.3.1 image as a single container, pinned by immutable digest, mount the jellyswarrm_data volume that holds its configuration and database, apply your admin password, and publish it over HTTPS on your domain.
Step 03
Open https://your-domain/ui and sign in as admin with the password from your installation credentials. Add your Jellyfin servers under Servers, set the public address in Settings, then point your Jellyfin apps at your domain.
Jellyswarrm runs in full here: a Jellyfin-compatible proxy on your own domain that merges the servers you already have.
Browse media from several Jellyfin servers in one place, with libraries of the same name merged into a single virtual library.
Jellyswarrm presents itself as a standard Jellyfin server, so existing Jellyfin apps can point at one URL. Upstream notes not every client has been tested.
The Jellyfin web client is served from the same address, so a browser needs nothing beyond your domain.
Add backend servers, map users to them and adjust settings from one admin interface, protected by the admin password.
Choose per backend server whether the client is sent straight to that server (Redirect) or all traffic is relayed through this one (Proxy).
The server list, users and configuration live on the jellyswarrm_data volume and survived a container restart in QA.
Managed hosting for Jellyswarrm, so the parts that keep it online are not your problem.
Combine Jellyfin servers in different locations into a single library behind one address.
Point current clients at the proxy, since it appears as a normal Jellyfin server.
Map users between backends so each person signs in once.
Pick Redirect to send viewers straight to a backend, or Proxy to relay media through this server.


Dedicated Cloud VPS sizes, pre-configured for Jellyswarrm hosting. Pick the one that fits, and resize any time.
One address in front of your Jellyfin servers.
$24.99per month
More headroom if Jellyswarrm sits alongside other media tools.
$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. Jellyswarrm itself is licensed by its maintainers under GPL-2.0.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Jellyswarrm 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.
Jellyswarrm 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.
Yes. For Jellyswarrm Docker hosting, the template runs the upstream ghcr.io/llukas22/jellyswarrm 0.3.1 image, pinned by digest, as one container on port 3000. It serves the Jellyfin API, web client, admin UI and WebSocket, and keeps SQLite in a single volume. xCloud's nginx adds HTTPS.
Jellyswarrm is open source under the GPL-2.0 licence, so the proxy carries no licence fee. xCloud's bill covers the Cloud VPS and the deployment. Your backend Jellyfin servers and their storage are separate, and Proxy mode spends this server's bandwidth on relayed media.
The manifest sets 512 MB of RAM, one core and 2 GB of disk; upstream states no figure of its own. It is one Rust process with SQLite. Redirect mode uses little, and Proxy mode costs CPU and bandwidth rather than memory. The 6 GB plan gives wide headroom.
No. Jellyswarrm only fronts Jellyfin servers you already run, and no media storage or Jellyfin server is installed. In the admin UI you add each backend and choose Redirect, where the backend must be reachable from the viewer's device, or Proxy, where this server relays everything.
Open /ui on your HTTPS domain and sign in as admin with the password on your credentials panel. Whoever registers first does not become admin. Change the password in the environment editor and redeploy, not in the admin UI. The session cookie is not marked Secure, so use a long password.
Back up jellyswarrm_data, which holds jellyswarrm.toml, the SQLite database of users, servers and mappings, and logs. The toml contains the session key and the admin password in plain text, so keep the copy off-server and private, and stop the container before copying.
Your install stays on 0.3.1 because the digest is pinned and catalog changes apply to new sites only. Copy jellyswarrm_data first, skim the upstream notes, then choose a newer template version. The session key in the data volume must never change, since it derives the key protecting stored backend credentials.
Upstream describes it as early development: it works, but QuickConnect, SyncPlay websockets, audio streaming and automatic bitrate adjustment are in progress, and media management is not implemented. Test it with the clients your household uses before depending on it, and keep your original Jellyfin addresses available.
Yes. Jellyswarrm cloud use gives the proxy a dedicated Cloud VPS with your domain and certificate; set that address under Settings afterwards. A machine from another host can be connected as self-managed and run the same template.
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.