Cloud VPS 6 GB
Most popularA single app's video calls or voice AI agent.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy LiveKit hosting and run a self-hosted WebRTC server that your own app connects to for video calls, live streams and voice AI agents. xCloud starts the pinned LiveKit image as a single container, generates an API key and secret, publishes the signalling and API port over HTTPS on your domain and lists the UDP and TCP media ports you open in your firewall. It has no web console.
LiveKit is open-source realtime infrastructure for voice, video and AI agents. Upstream describes a scalable, distributed WebRTC SFU, a selective forwarding unit, where people, devices and AI agents join the same room, with SDKs for web, mobile, desktop and server, JWT authentication, UDP, TCP and TURN connectivity, and a single binary, Docker or Kubernetes deployment. It is released under the Apache License 2.0. Self-hosted LiveKit is the option for teams that would otherwise rent a hosted video API such as Twilio Video.
On xCloud the template runs the livekit/livekit-server v1.13.9 image, pinned by digest, as one container with no database, cache or volume. Signalling and the HTTP API sit behind HTTPS on your domain, while media goes straight to the server IP on two ports you open yourself. Rooms live in memory and start empty after a restart. The embedded TURN relay is off.
Self-hosting a WebRTC media server normally means a container, a domain, generated API credentials and two open firewall ports before a single video call can connect. This is the same result without assembling any of it.
Step 01
Create your xCloud account, pick LiveKit from the OneClick catalog and select a domain — no extra fields, xCloud generates the credentials.
Step 02
One click. We bring up the pinned LiveKit v1.13.9 image, generate an API key and secret, and publish the signalling and API port over HTTPS on your domain, shown in the protected installation credentials.
Step 03
Open the UDP and TCP media ports listed on the credentials card in your server firewall, then point a LiveKit SDK, the LiveKit CLI or a LiveKit Agents worker at the Server URL and sign access tokens with the key and secret.
LiveKit runs in full here — the open-source WebRTC media server, on infrastructure you control.
Self-hosted real-time audio and video infrastructure you control, with no managed media vendor.
SDKs for web, mobile and backend languages to build video calls, live streams and voice AI agents.
HTTPS (WebSocket) signalling on your domain, with a generated API key and secret and no default credentials.
Single container with no database or cache to manage.
Lightweight: measured idle memory was roughly 15 MiB on QA.
Nothing is stored on disk. After an xCloud Restart the same API key and secret keep working; rooms are held in memory only and start empty.
Managed hosting for LiveKit, so the parts that keep it online are not your problem.
A product team building video calls can point its web and mobile clients at its own selective forwarding unit, so media routes through a server it controls instead of a third-party video API.
Run a LiveKit Agents worker that joins rooms as a participant, so users talk to an AI agent in real time while your backend signs the access tokens that let them in.
Publish from an encoder or a browser into a room and let many participants subscribe. Your backend decides who gets a token, so access stays under your control.
A small team can try in-app calls on a single container, with generated credentials, and tear it down or resize the Cloud VPS later without changing the client code.
Dedicated Cloud VPS sizes, pre-configured for LiveKit hosting. Pick the one that fits, and resize any time.
A single app's video calls or voice AI agent.
$24.99per month
More concurrent rooms and participants.
$59.99per month
LiveKit alongside a whole self-hosted stack.
$84.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. LiveKit itself is free and open source under the Apache License 2.0.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy LiveKit 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.
LiveKit 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 LiveKit Docker hosting the template runs the livekit/livekit-server image, pinned by digest, as a single container, generates an API key and secret and puts HTTPS signalling on your domain. Upstream also supports a single binary and Kubernetes. It is a singleton, so one install per server.
No. LiveKit is a media server with no web console. Your application drives it through a LiveKit SDK, the LiveKit CLI or a LiveKit Agents worker, using the API key and secret to sign short-lived access tokens. Requesting the domain in a browser just answers OK once the server is ready.
LiveKit's manifest floor is 256 MB of RAM, a single core and 2 GB of disk, and idle memory measured roughly 15 MiB in QA. Real rooms need more as participants and tracks grow. The 6 GB Cloud VPS sold here covers a small deployment; media-heavy use calls for more CPU and bandwidth.
Yes. The LiveKit server is open source under the Apache License 2.0, so the server software is free. xCloud bills for the Cloud VPS hosting it and for the deployment. Keep upstream's licence notices if you redistribute it.
Signalling and the API use container port 7880, behind HTTPS on your domain. Media uses 7882 over UDP, with 7881 over TCP as a fallback, each published on its own allocated host port shown in your credentials. xCloud does not open firewall ports, so open both media ports yourself.
Upstream lists SDKs for web, mobile, desktop, embedded and server, plus the LiveKit Agents framework for Python and Node.js. Point any of them at your Server URL, wss:// followed by your domain, and sign access tokens with the generated API key and secret.
Yes. Upstream presents LiveKit Agents as the SDK for code-first realtime voice agents, joining rooms like any participant. The agent worker is a separate program you run, pointed at your Server URL with the key and secret. This template deploys the media server only, not an agent.
Keep it on your server only, never in a web page or mobile app, because it signs the tokens that let people join rooms. It lives in the Environment editor; changing it and redeploying invalidates every token signed with the old one. Do not put Basic Auth in front of the domain, since clients send tokens in the Authorization header.
The container stays at v1.13.9 by digest. For a newer server, read upstream's release notes, keep a copy of the API key and secret, and select a later template version. Rooms are held in memory, so any room open during the restart ends and starts empty afterwards.
There is no volume, so a LiveKit backup is only your credentials. The server keeps no state on disk, and rooms are held in memory and start empty after a restart. The only thing to keep is the API key and secret from the Environment editor, so store a copy; anyone you gave tokens to needs them unchanged.
Yes. Under LiveKit cloud use, xCloud sets up a dedicated Cloud VPS, deploys the server and attaches your domain and certificate. Media goes to the server IP, so a Cloudflare-proxied domain carries signalling only. Without TURN, clients blocking UDP and TCP cannot connect.
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.