Cloud VPS 16 GB
Most popularA single-team experiment workspace, sized for real headroom.
$59.99per month
- 16 GB RAM
- 6 vCPU cores
- 200 GB NVMe SSD
- 30 TB
- Unlimited
MLflow hosting for teams that need a private place to track experiments and compare runs. Deploy MLflow 3.15.2 as a self-hosted machine learning experiment tracking server: xCloud runs the pinned image behind an authenticated HTTPS gateway, keeps metadata and artifacts on one persistent volume, and generates the credentials you sign in with, so nothing in the interface is reachable anonymously.
Self-hosted MLflow is a machine learning experiment tracking server. Its README describes MLflow as an open source AI engineering platform for agents, LLMs and ML models, and lists experiment tracking of parameters, metrics and results, model evaluation, a model registry and deployment tools. Teams run their own server instead of a hosted tracker such as Weights and Biases so that runs and artifacts stay on infrastructure they control.
On xCloud the template runs the ghcr.io/mlflow/mlflow v3.15.2 image behind a Caddy gateway, both pinned by immutable digest. MLflow stores metadata in SQLite and serves artifacts itself, all on the mlflow_data volume, and only the gateway is published, over HTTPS. Caddy enforces Basic Authentication on every request using the administrator username you choose and a generated password. The setup is a compact single-node baseline.
Self-hosting MLflow normally means a container, an authentication layer in front of it, persistent storage for metadata and artifacts, and a domain and certificate before a single run is logged. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick MLflow from the OneClick catalog. Enter a site title and domain, confirm an administrator username, and let xCloud generate a strong password.
Step 02
One click. We bring up the official MLflow 3.15.2 image, pinned by immutable digest, behind a Caddy gateway that protects the entire UI, tracking API and artifact API with your generated credentials, mount the mlflow_data volume for SQLite metadata and served artifacts, and publish it over HTTPS on your domain.
Step 03
Open your HTTPS URL and sign in with the generated administrator credentials shown in your xCloud credential panel. Create an experiment, start a run, log a parameter and a metric, upload a small artifact, and read it all back to confirm the workspace works end to end.
MLflow runs in full here — experiment tracking, run comparison and artifact storage, on infrastructure you control.
Create experiments, start runs and browse the full run history from the familiar MLflow interface.
Log and compare metrics, parameters and tags across runs to see what actually changed between them.
Upload and read back artifacts — files, models, plots — served directly by MLflow from its own volume.
A Caddy gateway protects the entire UI, tracking API and artifact API with your generated credentials — nothing is reachable unauthenticated.
The MLflow container itself has no path to the internet — only the authenticating gateway is published.
SQLite metadata and served artifacts share one persistent volume, so a run and everything it produced stay together.
Managed hosting for MLflow, so the parts that keep it online are not your problem.
Log parameters and metrics from each run to your own server and open the MLflow interface to see which change moved the result, with every run kept in the SQLite database on your Cloud VPS.
Upload plots, models and other artifacts through MLflow, which serves them from the same volume as the metadata, so a run and the files it produced are retrieved and backed up together.
Share a single authenticated HTTPS address with colleagues so everyone logs to the same server, rather than keeping separate local MLflow folders on laptops.
Point an LLM application's tracing at the server to inspect calls, per MLflow's tracing features, while keeping prompts and outputs off a third-party service, at modest single-node volumes.
Dedicated Cloud VPS sizes, pre-configured for MLflow and its authenticated gateway. Pick the one that fits, and resize any time.
A single-team experiment workspace, sized for real headroom.
$59.99per month
More concurrent experiments and a growing artifact store.
$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. The 6 GB rung sold elsewhere on this site is deliberately absent: this app's own template minimum is 3 GB, which does not leave comfortable headroom on it once the operating system is counted. MLflow itself is free under the Apache License 2.0.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy MLflow on it through the same panel, for a per-server management fee instead of a Cloud VPS rental. Size it above MLflow's own 3 GB minimum.
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.
MLflow 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.
The template manifest asks for 3072 MB of RAM, 2 CPU cores and 20 GB of disk as a floor. A 6 GB server would leave only about 3 GB above the app's own floor once the OS is counted, so this page sells the 16 GB tier as the entry rung rather than calling that comfortable.
Yes. MLflow is Apache-2.0 licensed, per the LICENSE.txt at the v3.15.2 tag, and its README calls it an open source AI engineering platform. There is no licence fee; xCloud charges for the dedicated Cloud VPS and deployment around it, and the experiments stay yours.
This is MLflow Docker hosting prepared for you: the template runs the official ghcr.io/mlflow/mlflow v3.15.2 image and a Caddy gateway, both pinned by immutable digest, with the mlflow_data volume and HTTPS on your domain. You point your code's tracking URI at the site and log in.
It is where run metadata lives. Here the template starts MLflow with a SQLite file at /mlflow-data/mlflow.db for experiments, runs, metrics, parameters, tags and the registry. That suits a compact single-node workspace; no PostgreSQL driver is in the image and none is added.
MLflow serves them itself and writes them under /mlflow-data/artifacts, on the same mlflow_data volume as the SQLite database. Runs therefore stay together with the files they produced, and one volume backup captures both. External object storage is not configured by this template.
Not through MLflow's own auth app here: the upstream image omits a package it needs, so a Caddy gateway enforces HTTP Basic Authentication in front of the UI, tracking API and artifact API with your generated credentials. MLflow also restricts allowed hosts and CORS origins to your domain.
MLflow's README lists LLM tracing, evaluation, prompt management and an AI Gateway among its features. This template runs the server in a compact single-node setup with SQLite, so it suits modest tracing volumes; it is not configured for high-concurrency production traffic.
Nothing upgrades it for you: the template pins MLflow v3.15.2 by immutable digest. Read the migration and release notes, take a consistent backup of mlflow_data, then verify sign-in and run read-back after raising the pinned image, or adopt a newer template version.
Not as configured. SQLite metadata and local served artifacts fit a compact single-node workspace. The image has no database or object-storage drivers and this template adds none, so larger multi-worker deployments need an upstream-supported external database and artifact store.
It is your own MLflow on a dedicated Cloud VPS that xCloud provisions, not a shared tracking service. The server, the mlflow_data volume and the administrator credentials belong to your install, and only the authenticating gateway is published over HTTPS.
A backup is the mlflow_data volume plus your Environment values, taken at the same point in time. The volume holds both the SQLite database and every served artifact, so restoring one without the other, or without the credentials, leaves runs pointing at missing files.
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.