Cloud VPS 6 GB
Most popularA shared recipe box for a household or small group.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
CookCLI hosting on xCloud gives you a self-hosted recipe server for your Cooklang recipe files, with a web interface to browse, search and edit them from any device. Deploy CookCLI from the OneClick catalog and xCloud starts the pinned 0.37.0 image behind a gateway that asks for a generated Basic Authentication login, mounts a recipe volume and publishes it over HTTPS. There is no database to run.
CookCLI is a suite of command line tools for working with Cooklang recipes, which its README says it built to automate your cooking and shopping routine with UNIX tools. It can also function as a webserver for your recipes, making them browsable on any device. Its README lists a web interface, recipe search, organised shopping lists, pantry tracking with expiration dates and meal plans written as menu files. Self-hosted CookCLI is that recipe server run on your own server. It is licensed under MIT.
On xCloud this template deploys CookCLI 0.37.0 from the upstream image, pinned by digest, behind a Caddy gateway that enforces HTTP Basic Authentication, with no database. Recipe files sit on the cookcli_recipes volume, seeded with upstream sample recipes on first start. CookCLI has no accounts of its own, so everyone with the gateway credentials has full access.
Self-hosting CookCLI normally means a container, a gateway, a domain and a certificate before a single recipe is written. This is the same result without assembling any of it.
Step 01
Create your xCloud account, pick CookCLI from the OneClick catalog, choose a domain, and keep or change the gateway username (default admin).
Step 02
One click. We bring up CookCLI 0.37.0 behind a Caddy gateway, generate the access password, mount the recipe volume preloaded with upstream sample recipes, and publish it over HTTPS.
Step 03
Open your HTTPS URL, enter the username and generated password from your installation credentials, then click New Recipe and write it in the browser editor — it saves automatically.
CookCLI runs in full here — its recipe editor, shopping lists and pantry tracking, on infrastructure you control.
Recipes are ordinary Cooklang .cook files instead of a proprietary database, easy to copy or keep in Git.
Write and edit recipes with live Cooklang language support, right in the browser.
Turn one or more recipes, scaled as needed, into an organized shopping list.
Track pantry inventory and expiration dates, and plan meals with .menu files.
The whole site, API and editor sit behind a username and a generated password — nothing is open by default.
Upstream sample recipes load on day one, so the library is never empty when you first sign in.
Managed hosting for CookCLI, so the parts that keep it online are not your problem.
You write recipes as Cooklang files in the web editor and keep them in one volume you can back up, copy or move as ordinary files.
You pick the dishes you plan to cook and let CookCLI assemble one organised shopping list instead of copying ingredients by hand.
A household records pantry items and expiration dates in the web interface and checks them before the weekly shop.
Everyone in the home opens the same HTTPS address with one shared login, and each person can browse and edit recipes from a phone or laptop.
Dedicated Cloud VPS sizes, pre-configured for CookCLI hosting. Pick the one that fits, and resize any time.
A shared recipe box for a household or small group.
$24.99per month
Larger recipe libraries and more frequent edits.
$59.99per month
CookCLI 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. CookCLI itself is free under the MIT licence.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy CookCLI 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.
CookCLI on xCloud runs on a dedicated Cloud VPS that we provision, patch, monitor and restore. Deploy faster. Own your recipes. 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.
Cooklang is the recipe markup that CookCLI works with, described on cooklang.org, and recipes are stored as plain .cook text files. This page does not teach the syntax, so use the upstream documentation, and add your own .cook files through the web editor or by copying them into the volume.
Yes. CookCLI is open source under the MIT licence, linked from this page at the pinned v0.37.0 tag. xCloud bills for the Cloud VPS under it, not for CookCLI, and there is no per-user fee. The Caddy gateway in front of it is a separate project under Apache-2.0.
Yes, and this CookCLI Docker hosting template does it for you: the upstream ghcr.io/cooklang/cookcli image, pinned by digest, runs beside a Caddy gateway on your own server, with HTTPS in front. It is not a CookCLI cloud account, so your recipes stay on your server.
CookCLI needs at least 256 MB of RAM, one core and 1 GB of disk by its manifest, covering CookCLI and the gateway. Recipe files are small, so the library rarely grows the disk much. This page sells the 6 GB tier, which leaves enormous headroom above that floor.
No. CookCLI has no built-in authentication, so this template puts the whole site behind one shared Basic Authentication login. Everyone who has it can read, create, edit and delete every recipe and use the shopping list and pantry. Rotate it by changing the environment values and restarting.
Open your HTTPS address and your browser asks for the username and generated password shown after install. The default username is admin and the password is 32 characters. Then the recipe library opens, seeded with upstream sample recipes the first time the volume starts.
Yes, if they are Cooklang .cook files: add them through the web editor, or copy them into the cookcli_recipes volume. This page does not claim a browser upload for bulk import, and request bodies are limited to 1 MiB, so convert other formats to Cooklang first.
Only a Caddy 2.10.2 gateway that enforces the Basic Authentication login. CookCLI's own port is reachable only from the gateway on the private network, and there is no database. Cross-site request protection stays on, so recipe changes must come from your own domain.
Back up the cookcli_recipes volume, the complete data boundary, which holds every recipe file. Stop writes or stop the container briefly for a consistent copy, keep it off the server, and test a restore on a disposable install. The volume is owned by user 1000 inside the container.
A running 0.37.0 server is left alone when the catalog changes; a newer template version is something you adopt. Back up the recipe volume first and read the upstream release notes. The image tag and digest in the template are pinned together by its maintainers.
CookCLI keeps recipes and builds shopping lists from them, storing the recipes as plain Cooklang files on a server you run. This page makes no feature-parity claim against Paprika, so try CookCLI with a few of your own recipes first.
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.