Cloud VPS 6 GB
Most popularA few concurrent browser sessions for one team's scripts and tests.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Browserless hosting on xCloud gives your code a self-hosted headless browser service: connect Puppeteer or Playwright to a remote Chromium over WebSocket, or call REST endpoints such as screenshots. Deploy Browserless from the OneClick catalog and xCloud starts the pinned image with one gigabyte of shared memory, generates the API token and publishes the HTTP and WebSocket API over HTTPS on your domain. Every request needs the token, and the licence has commercial terms.
Browserless is a way to deploy headless browsers in Docker. Its README describes parallelism and queueing with configurable concurrency limits, a debug viewer, unforked Puppeteer and Playwright support, fonts and emoji, configurable timeouts, and crash tolerance, so a Chrome crash does not take the service down. Self-hosted Browserless is a self-hosted headless browser service you run yourself instead of a cloud one. It is dual licensed under SSPL-1.0 or a Browserless Commercial License.
On xCloud this template deploys Browserless v2.56.7 as the official Chromium image, pinned by digest, with one gigabyte of shared memory, behind HTTPS with WebSocket upgrades. It is stateless, with no volume or database, and every HTTP and WebSocket request needs the generated token. Upstream's premium cloud features, such as BrowserQL and session replay, are not included.
A headless browser service normally means a container, shared-memory tuning, a token, a domain and a certificate before the first screenshot. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick Browserless from the OneClick catalog. Choose your domain and target server. There is nothing else to fill in: xCloud generates the 48-character API token.
Step 02
One click. We bring up the official Browserless v2.56.7 image, pinned by immutable digest, and publish it over HTTPS on your domain.
Step 03
Copy the API token from the credentials panel. Connect Puppeteer with browserWSEndpoint set to your domain's WebSocket URL plus ?token=, or Playwright with connectOverCDP, or POST to /screenshot?token= to get a PNG. The site root returns 404 by design; the interactive API docs are at /docs/.
The open-source Browserless image runs here: remote Chromium sessions for Puppeteer and Playwright, plus the REST API for screenshots, PDFs, content and scraping.
Point browserWSEndpoint or connectOverCDP at your domain and drive a real Chromium session remotely.
POST a URL to /screenshot, /pdf, /content or /scrape and get the result back without a browser on your side.
Authentication is always on: pass the token as ?token= or an Authorization: Bearer header, or get a 401.
The container runs with 1 GB of shared memory so Chromium does not crash on demanding pages.
CONCURRENT, QUEUED and TIMEOUT are read on every start; raise them only on a larger server, at roughly 500 MB per busy session.
Each session starts from a clean browser profile; there is no volume and nothing to migrate.
Managed hosting for Browserless, so the parts that keep it online are not your problem.
A developer points puppeteer.connect at the WebSocket URL with the token, so scrapers and test scripts drive a browser on the Cloud VPS instead of installing Chromium on every machine.
A backend sends a POST to the screenshot endpoint with a URL and gets an image back, rendering pages for previews or reports without keeping a browser in the application server.
A team connects Playwright to the Chromium endpoint from CI, caps concurrency with the CONCURRENT and QUEUED settings, and keeps the browser fleet on a server they rent.
A data team runs its own headless browsers so cookies, targets and logs stay on its server, setting its own timeouts and limits, and taking care of the licence terms for commercial use.
Dedicated Cloud VPS sizes, pre-configured for Browserless hosting. Pick the one that fits, and resize any time.
A few concurrent browser sessions for one team's scripts and tests.
$24.99per month
More RAM for more concurrent Chromium sessions and heavier pages.
$59.99per month
Browserless alongside the apps and pipelines that call it.
$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. Browserless itself is dual-licensed by Browserless under SSPL-1.0 or a commercial licence; closed-source commercial or CI use needs a licence from browserless.io.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy Browserless 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.
Browserless 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.
Not unconditionally. The README states the licence as SSPL-1.0 or a Browserless Commercial License, and says that using it to build commercial sites, applications or closed-source CI systems needs a purchased commercial licence, while compatible open-source use is allowed. Read the licence file at the pinned v2.56.7 tag and decide before use; this is not legal advice.
Yes, and this Browserless Docker hosting template does it for you: the official ghcr.io/browserless/chromium image, pinned by digest and published for amd64 and arm64, runs as one container on your own server, not in a Browserless cloud account, with HTTPS and WebSocket upgrades in front of port 3000.
The template manifest asks for 2048 MB of RAM, 2 CPU cores and 8 GB of disk as a floor, and the container gets 1 GB of shared memory so Chromium does not crash on heavy pages. Each concurrent session uses memory. This page sells the 6 GB tier, which leaves headroom for several sessions.
Use puppeteer-core's connect with the Puppeteer WebSocket URL from the credentials panel, wss://your-domain?token=TOKEN. Upstream's README shows this pattern with unforked Puppeteer. The URL contains the token, so keep it out of logs and client-side code, and rotate TOKEN if it leaks.
Yes for Chromium: upstream documents connecting standard Playwright to the service, and this template ships the Chromium image. Upstream says Firefox and WebKit need its separate firefox or multi images, which this template does not use, so only Chromium sessions are available here.
Yes, and it is always set. Every HTTP and WebSocket request must carry it as a token query parameter or an Authorization Bearer header, and a request without it gets 401; only the /docs/ pages are open. Never blank TOKEN, because an empty value turns authentication off and leaves the browser API open to anyone.
The template's README shows a POST to the screenshot endpoint with a URL returning a PNG, and the API reference at /docs/ lists the other REST endpoints. Upstream lists some features, such as BrowserQL, session replay and residential proxying, as premium cloud or enterprise features that are not part of this install.
That is set by CONCURRENT and QUEUED, read on every start, with TIMEOUT capping session length. Edit them in the Environment editor, redeploy, and give clients the new TOKEN if you change it. Size the server for your concurrency, because each Chromium session uses memory and CPU.
They are separate projects with separate APIs. Steel has its own OneClick page. This template runs Browserless, which exposes Chromium to unforked Puppeteer and Playwright over WebSocket and offers REST endpoints. This page does not rank the two, so test your own workload.
No. It is stateless, with no volume and no database, and each session starts from a clean browser profile, so there is nothing to back up beyond your own environment values and token. Keep TOKEN, CONCURRENT, QUEUED and TIMEOUT in your notes, and take a backup of anything your scripts save elsewhere.
Upgrades are not automatic. The template pins v2.56.7 by immutable digest, and new installs use that release while existing sites are left alone. When a newer template version is published, read the upstream release notes and adopt that version. Since nothing is stored, there is no volume to back up first; moving only restarts sessions.
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.