5 Best VPS for Self-Hosting Xibo

Xibo CMS is a Docker Compose stack of five containers that will run on almost any KVM VPS with an x86-64 CPU and 4GB of RAM. That sentence rules out more hosts than you’d expect. ARM plans are out, because the CMS has no ARM build. OpenVZ containers are out, because Docker inside a container is a mess. And anything under 4GB will run, right up until MySQL starts pinning a core at 30 or 40 displays.

The payoff for getting it right is that a $5 to $35 server replaces per-screen cloud fees that scale linearly. Fifty screens on a hosted platform at $10 to $20 each is $500 to $1,000 a month. The same fleet on a single VPS running Xibo costs whatever the VPS costs, with no display cap. Below are the requirements as Xibo documents them, then the five hosts that meet them at a sensible price.

Xibo Server Requirements

Xibo’s current stable release is the 4.5 line, AGPLv3, distributed as a Docker Compose file that brings up the CMS web app, MySQL 8, the XMR relay for real-time pushes to players, Memcached, and QuickChart for report rendering. The supported environments page specifies Ubuntu Server LTS on x86-64, Docker with the stock compose file, and a reverse proxy in front for TLS. Installing directly onto the OS is community-supported only and not covered by the admin manual, so don’t.

On RAM, the docs contradict themselves slightly. The supported-environments page says 4GB minimum. The older CMS installation service page says 2GB will do and points at DigitalOcean, Linode and Vultr’s 2GB tiers. In practice 2GB runs a handful of screens for testing, and 4GB is the honest floor for production. A 4GB box handles somewhere around 50 to 100 displays before MySQL starts eating CPU. One admin on the Xibo forum runs 230 players on a 4-core, 8GB VPS and still sees the database container pinned at 100%.

Storage starts at 20GB and grows with your media library. Past roughly 25GB of video and images, Xibo’s own guidance is to attach block storage rather than upgrade the whole plan. Bandwidth matters less than you’d think. Players cache everything locally and keep running if the CMS goes offline, so traffic spikes when you publish new media and then drops to almost nothing.

Two ports need to be open. 80 (or 443 behind a reverse proxy) for the CMS, and 9505 for XMR. The most common “waiting for CMS” error on the forum is someone who forgot 9505.

One last filter. Container-based VPS plans like OpenVZ can’t run Docker properly. Every host below sells KVM, which is what you want. If you’re unsure which kind you’re looking at, our shared vs VPS vs dedicated explainer covers the difference.

1. Hostinger

Hostinger is the only host on this list with a one-click Xibo template. Pick it from the OS dropdown and you get the full five-container stack behind a Traefik reverse proxy with HTTPS already sorted. That’s an hour of setup gone.

The specs are the other reason it’s first. The entry KVM 1 plan comes with 4GB RAM, 1 vCPU, 50GB NVMe and 4TB of traffic for about $4.99 a month on a long-term deal. KVM 2 doubles that to 8GB, 2 vCPU and 100GB NVMe for around $5.99. Both clear Xibo’s recommended floor on the cheapest tier, which no other host here manages. Full breakdown in our Hostinger VPS review.

The downside is the usual Hostinger one. Those prices need a multi-year prepay, and renewals land somewhere between double and triple. Check the renewal figure in the cart before you commit. Even so, if you want Xibo running today without touching a compose file, this is the one.

2. DigitalOcean

DigitalOcean is the host Xibo’s own docs recommend, and the setup they describe still holds. Grab a 2GB droplet, attach a block storage volume when the library outgrows the disk, done. The docs quote $20 for that droplet, which is outdated. A 2GB Basic droplet with 50GB SSD is now $12, the 4GB tier is $24 and 8GB is $48. Block storage is $0.10 per GB per month, so a 100GB media library adds $10.

No Xibo image in the Marketplace, so you’re deploying Ubuntu 22.04 and following the official Docker guide. Billing went per-second in January 2026 with a monthly cap, and a powered-off droplet still bills, so destroy it when you’re done testing.

You pay a premium per GB of RAM compared to everything else here. In return you get predictable pricing and the exact configuration the Xibo team tests against, which is worth it for teams that want the reference setup and would rather not debug someone else’s. If the price bothers you, we’ve covered the best DigitalOcean alternatives separately.

3. Contabo

Contabo wins on raw resources per dollar and it isn’t close. The entry Cloud VPS plan gives you 3 vCPU, 8GB RAM, 75GB NVMe (or 150GB SSD if you’d rather have space than speed) and 32TB of traffic for around $4.95 a month on a 12-month term. That’s more RAM than most people will ever need for Xibo, at the price other hosts charge for 2GB.

There are strings. The entry tier carries a one-time setup fee that varies with the contract length, and monthly billing costs 15 to 20% more than annual. Contabo is also mid-way through renaming its VPS line in 2026, so the plan at checkout may not be called Cloud VPS 10 anymore.

The bigger caveat is consistency. Contabo overcommits CPU at roughly 3:1, so the vCPUs you’re sold are shared with neighbours. For Xibo that’s fine at 20 screens and noticeable at 200, because MySQL is sensitive to I/O jitter. Spend some of the RAM headroom on a bigger MySQL memory limit and it evens out. If your media library is measured in hundreds of gigabytes and your budget isn’t, this is where to go.

4. Kamatera

Kamatera doesn’t sell fixed plans. You build the server from vCPU, RAM, disk and traffic blocks, starting at $4 a month for a 1 vCPU, 1GB box, and pay per minute if you’d rather not commit. Start at 2GB for the pilot, scale to 8GB when the fleet grows, and the resize takes under a minute with no downtime.

The other draw is the trial. Kamatera still offers 30 days with up to $100 in credit and 1TB of traffic, long enough to run a proper pilot with real players before spending anything. It also has 24 data centres across North America, Europe, Asia, the Middle East and Australia, so the CMS can sit close to your screens.

Two warnings. Pricing is per component, so build your config in the calculator and compare it against DigitalOcean’s fixed tiers before deciding. And powering a server off doesn’t stop the billing. Terminate it, or you’ll pay for an idle box. Those aside, it’s the pick for pilots and deployments that need to grow without a migration.

5. Hetzner

Hetzner used to be the obvious answer for cheap European hosting, and for Xibo it comes with a trap. The CAX plans, its cheapest tier, run on ARM. The Xibo CMS won’t run on them at all. You need the CPX line, which is x86 AMD EPYC.

Hetzner also raised prices twice in 2026, in April and again in June, and the old Cost-Optimized CX plans were unavailable to order when I checked. What’s left is CPX12 at €11.99 for 2GB, CPX22 at €19.49 for 4GB and CPX32 at €35.49 for 8GB, plus €0.50 a month for an IPv4 address. That puts the 4GB tier roughly level with DigitalOcean, which wasn’t the case a year ago.

The reason it stays on the list is traffic. Every European Hetzner plan includes 20TB a month, ten times what DigitalOcean gives on its 2GB droplet. Volumes for block storage run around €0.057 per GB. If you’re pushing 4K video to a lot of screens from an EU data centre, that allowance matters more than the base price, and Hetzner is still the right call for that job.

Self-host vs. Pay Per Screen

Self-hosting Xibo makes sense when you have enough screens for per-screen fees to hurt, and someone who can run Docker updates and restore a backup without panicking. Below about ten screens the maths flips. You’d be paying $5 to $20 a month for a server plus your own time to save a bill that was never big.

For that size, hosted signage is the sane option. Xibo Cloud starts around £3.50 a month per display and runs the same CMS you’d self-host. If you’d rather skip Xibo entirely, a cloud digital sign software like OptiSigns starts at $10 per screen (three screens free), runs on a Raspberry Pi or a Fire TV stick, and needs no server at all. Yodeck starts at $8 per screen and ScreenCloud at $20.

Break-even is somewhere around 15 to 25 screens depending on the plan you compare against. Above that, a $6 to $35 VPS running unlimited displays wins every year.

Setup Notes

Deploy Ubuntu 22.04 or 24.04, install Docker and the Compose plugin, and follow Xibo’s official Docker guide rather than a random YouTube tutorial. The compose file sets memory limits for each container, and on a 4GB box you’ll want to lower the CMS and MySQL limits to 512MB each or they’ll fight over RAM.

Everything Xibo cares about lives under the shared directory. Media in shared/cms/library, the database in shared/db, daily dumps in shared/backup. Back that whole folder up off the server. Before you ever run docker compose down, check that shared/backup/db/latest.tar.gz was created in the last 24 hours. Plenty of forum threads start with someone who didn’t.

Put a reverse proxy in front for HTTPS. Caddy is the least effort, Traefik if you’re on Hostinger’s template, and either way raise the upload body limit to 2GB so large video files don’t fail silently.

Conclusion

For most people, Hostinger. The one-click template removes the hardest part of self-hosting Xibo and the entry plan already has 4GB of RAM. If you’d rather run the setup Xibo’s own team documents, DigitalOcean is the safe pick. And if your media library is measured in hundreds of gigabytes, Contabo’s 8GB entry plan buys more room than anything else at that price.

If none of the five fit, Vultr’s $10 2GB plan is on Xibo’s own recommended list and works as a drop-in substitute.