Cloud VPS 6 GB
Most popularA docs site for one product, team or notebook.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
CodeX Docs hosting on xCloud gives you a self-hosted documentation site for product docs, team docs or personal notes, written in the Editor.js block editor. Deploy CodeX Docs from the OneClick catalog and xCloud starts the pinned image as one container with no database, generates the editor password, mounts volumes for pages and uploads and publishes the site over HTTPS on your domain. Published pages are public, and one shared password unlocks the editor.
CodeX Docs is a free docs application based on the Editor.js ecosystem, which its README says gives all modern opportunities for working with content. You can use it for product documentation, internal team docs or personal notes. It lists nested docs structure, static rendering, human-readable SEO-friendly URLs, an interface that looks good on desktop and mobile, and deployment with no database or other dependencies. Self-hosted CodeX Docs is a self-hosted documentation site you run yourself. It is licensed under Apache-2.0.
On xCloud, the template deploys CodeX Docs 2.2.5 as a community-built image of upstream v2.2.5, pinned by digest, behind HTTPS on your domain. Pages are stored in the app's built-in file database on the codex_docs_db volume and uploaded files on codex_docs_uploads. There is no username and no multi-user accounts: one shared editor password unlocks the editor, and everyone can read published pages.
A docs site normally means a container, a place to keep pages and uploads, a way to protect the editor, a domain and a certificate before the first page. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick CodeX Docs from the OneClick catalog. Choose your domain and target server, then enter the Site Title (default "Documentation"); the Editor Password is generated for you.
Step 02
One click. We bring up the community-built CodeX Docs image, pinned by immutable digest, as a single container with no database, mount the codex_docs_db and codex_docs_uploads volumes, and publish it over HTTPS on your domain.
Step 03
Save the Editor Password from the protected installation credentials, open your HTTPS site, go to /auth and sign in — there is no username. Then create the first page from the sidebar.
CodeX Docs runs in full here: a block-editor documentation site with public pages and a protected editor, with nothing else to run.
Write pages in the Editor.js block editor and publish them at human-readable, SEO-friendly URLs.
Nest pages under each other to build any documentation structure, shown in the sidebar.
Readers open pages without signing in; creating and editing needs the Editor Password at /auth.
Pages are stored in the app's built-in file database on a persistent volume, so there is no database container or credentials to manage.
Uploaded images and files live on their own codex_docs_uploads volume, with request bodies up to 200 MB accepted by the proxy.
The password is generated at install and shown in the protected credentials; the upstream default password was verified not to work.
Managed hosting for CodeX Docs, so the parts that keep it online are not your problem.
A small product team writes docs in the Editor.js block editor, nests them into a structure that fits the product, and publishes pages with readable URLs on its own domain.
A team keeps runbooks and how-tos in one site, with a single editor password held by the people who maintain it, and pages that anyone with the link can read.
A writer or engineer keeps notes as pages in nested sections, edits them from any browser with the editor password, and shares the ones worth sharing.
An operator who does not want a separate database service runs a docs site from two volumes, backs them up as plain files, and upgrades by moving to a newer template version.

Dedicated Cloud VPS sizes, pre-configured for CodeX Docs hosting. Pick the one that fits, and resize any time.
A docs site for one product, team or notebook.
$24.99per month
More headroom if CodeX Docs sits alongside other apps on the same server.
$59.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. CodeX Docs itself is licensed by its maintainers under Apache-2.0.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy CodeX Docs 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.
CodeX Docs 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. CodeX Docs is open source under Apache-2.0, with the licence file linked from this page at the pinned v2.2.5 tag. xCloud bills for the Cloud VPS under it, not for CodeX Docs, and there is no per-editor fee. The image here is a community build of that upstream release.
Yes, and this CodeX Docs Docker hosting template does it for you: a community-built multi-architecture image of upstream v2.2.5, pinned by digest, is a single container on your own server rather than a CodeX Docs cloud account, with HTTPS in front of port 3000.
Per its manifest, CodeX Docs needs at least 128 MB of RAM, a single core and 1 GB of disk, because there is no database service. Uploads and pages grow the volumes. This page sells the 6 GB tier, which is vastly more than the floor and leaves room for other apps.
No. Upstream says it deploys with no database or other dependencies, and on this template pages are stored in the app's built-in file database on the codex_docs_db volume. Uploaded images and files go on codex_docs_uploads, so those two volumes are everything to back up.
Open the /auth address on your domain and enter the editor password from the credentials panel; there is no username. Anyone can read published pages without logging in. The password and session secret are read from the environment on every start, so change them there and redeploy.
Only by sharing the editor password. There is one shared password and no username or multi-user accounts, so everyone who knows it has full edit rights, and there is no per-person history of who changed what. Use a tool with accounts if you need roles or an audit trail.
Upstream says it is powered by the Editor.js ecosystem, which gives the blocks you write with. This page does not list which blocks or plugins are bundled in the community image, so check the editor itself after install. Extra configuration goes in as APP_CONFIG values that must be valid JSON.
Include both volumes in one backup: codex_docs_db holds your pages and codex_docs_uploads holds uploaded images and files. Copy them off the server while the app is idle, and keep your editor password and session secret in your notes. Test a restore on a disposable install before you rely on it.
Upgrades are not automatic. The template pins 2.2.5-xcloud.1 by immutable digest, and existing sites are not touched by catalog updates. Back up both volumes, read the upstream release notes, then move to a newer template version when one is published. Never use the upstream default password, which was verified not to work here.
It can be, if you use Notion for product docs, team docs or personal notes, the uses its README names. CodeX Docs is a docs site, with one shared password and no accounts, so this page makes no feature-parity claim. Try it with your own content first.
Yes. Published pages are public to anyone who can reach the domain, and only the editor is password-protected. Do not publish private material. If you need a private site, add Basic Auth at the access layer, which this template does not enable, or use a tool with per-user permissions.
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.