Cloud VPS 6 GB
Most popularA personal or small-team notebook workspace.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
JupyterLab hosting on xCloud gives you a self-hosted Jupyter notebook environment in the browser, with notebooks, terminals and text files on a workspace that stays on a server you control. Deploy JupyterLab from the OneClick catalog and xCloud starts the official Jupyter Docker Stacks minimal-notebook image, mounts the persistent jupyterlab_work volume, publishes it over HTTPS and generates the access token you sign in with.
JupyterLab is an extensible environment for interactive and reproducible computing, and self-hosted JupyterLab is a self-hosted notebook environment you run on your own server instead of a hosted service such as Google Colab. Its README calls it the next-generation user interface for Project Jupyter, with notebook, terminal, text editor, file browser and rich outputs, extensible through npm packages. It is licensed under BSD-3-Clause.
On xCloud this template runs the official Jupyter Docker Stacks minimal-notebook image, tagged 2026-08-24 and pinned by digest, which bundles JupyterLab. HTTPS is on your domain, and a single generated access token is the whole access model. Only the jupyterlab_work volume at /home/jovyan/work persists; packages installed elsewhere in the container are lost when it is recreated. It is single-user, not JupyterHub.
Self-hosting a notebook environment normally means a container, a persistent workspace, a domain and a certificate before a single cell runs. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick JupyterLab from the OneClick catalog. Enter a site title and domain, then leave the access-token field empty for secure automatic generation or supply your own.
Step 02
One click. We bring up the official Jupyter Docker Stacks minimal-notebook image pinned by immutable digest, mount the jupyterlab_work volume at /home/jovyan/work, and publish JupyterLab over HTTPS on your domain.
Step 03
Open your HTTPS URL and sign in with the access token shown in your installation credentials. Create a notebook or upload project files under the persistent work directory.
JupyterLab runs in full here — notebooks, terminals and interactive data exploration, on infrastructure you control.
Write and run notebooks, open terminals and edit text files from one interface, without installing anything locally.
Sign in with a generated access token instead of a shared or default password.
Notebooks and files under /home/jovyan/work survive a restart, so your files are still there when you come back.
Runs the same minimal-notebook image the Jupyter project itself publishes and maintains.
Install the kernels and packages your analysis needs inside the running environment, on hardware you size yourself.
The jupyterlab_work volume is the entire persistence contract — everything under it survives a restart.
Managed hosting for JupyterLab, so the parts that keep it online are not your problem.
An analyst opens a notebook from a laptop or tablet, loads project data into the work directory, and keeps going from the same state later because the workspace lives on a server.
A researcher keeps notebooks and datasets on one server they rent, signs in with a generated token, and decides when to upgrade the image rather than depending on a hosted notebook service.
An instructor prepares a workspace with the packages a course needs and shares the token with a small group, so nobody installs Python locally. For per-person accounts, use JupyterHub instead.
A developer starts a long computation in a terminal or notebook on a Cloud VPS sized for the job, closes the laptop, and returns to the results in the same persistent work directory.
Dedicated Cloud VPS sizes, pre-configured for JupyterLab hosting. Pick the one that fits, and resize any time.
A personal or small-team notebook workspace.
$24.99per month
Larger datasets and heavier kernels.
$59.99per month
JupyterLab 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. JupyterLab itself is free under the BSD-3-Clause license.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy JupyterLab 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.
JupyterLab 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. JupyterLab and the Jupyter Docker Stacks image are free software under BSD-3-Clause, with the licence file linked here. xCloud bills for the Cloud VPS under it, not for JupyterLab, and the software adds no per-user fee. Notebooks you create remain yours.
Per JupyterLab's README, it is the next-generation user interface for Project Jupyter, offering the familiar building blocks of the classic Jupyter Notebook, such as notebook, terminal, text editor and file browser, in a more flexible interface. This template runs JupyterLab through the minimal-notebook image.
Yes, and this JupyterLab Docker hosting template does it for you: the official quay.io/jupyter/minimal-notebook image, tagged 2026-08-24 and pinned by digest, runs as one container on your Cloud VPS, not in a JupyterLab cloud account, with HTTPS in front on port 8888.
JupyterLab's README says extensions are npm packages, with prebuilt ones distributed through PyPI and conda, and source extensions installable from npm. Install them inside the running environment, but note that anything outside /home/jovyan/work is lost when the container is recreated, so record your setup in work.
With one access token and no username. Leave the install field empty for xCloud to generate a 32-character token, or supply your own of at least 24 characters. Token authentication is the entire access model here, so anyone with the token has full access to the workspace and terminal.
The template manifest asks for 2048 MB of RAM, 2 CPU cores and 8 GB of disk as a floor. Heavier kernels and bigger datasets need more, because notebooks hold data in memory. This page sells the 6 GB tier, and you can resize the server later when your workload grows.
On the jupyterlab_work volume, mounted at /home/jovyan/work, which is the only persistent path. Include that volume in your backup before upgrades or destructive changes. Packages, custom kernels and system changes elsewhere in the container do not survive a recreation.
Upgrades are not automatic. The template pins the minimal-notebook 2026-08-24 image by immutable digest, a date tag rather than a JupyterLab version, and a catalog re-sync affects new installs only. Back up the work volume and check kernels and packages before changing the pinned image.
It can be: JupyterLab is a notebook environment in the browser on hardware you choose, with files you keep. This page makes no feature-parity claim with Colab, and it does not provide Colab's hosted compute, so size the Cloud VPS for your own workload.
No. This template runs a single-token minimal-notebook instance, not JupyterHub, and has no multi-user account management. One access token controls the whole workspace. JupyterHub has its own OneClick page if you want a sign-in page and separate workspaces per person.
Update JUPYTER_TOKEN in the Environment editor and restart the application, then verify a fresh sign-in. Existing browser sessions may need to sign in again. Keep the token stable between restarts, and make a backup of the work volume before any change to the install.
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.