Cloud VPS 6 GB
Most popularA private wiki for one team's documentation.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy LeafWiki hosting and give your team a private, self-hosted Markdown wiki on your own domain. xCloud runs the pinned LeafWiki v0.14.1 container, generates the admin password and signing secret, mounts a persistent data volume and publishes the wiki over HTTPS in minutes. It is one container, with SQLite and plain Markdown files on disk, and no database for you to run or tune.
Self-hosted LeafWiki is a wiki delivered as a single Go binary, with SQLite and Markdown stored on disk. Its README aims it at engineers and self-hosters who want structured, long-lived documentation, with no Node.js, no Redis and no Postgres, and says it may fit people who found Wiki.js or Outline too much to operate. It offers a tree-structured page hierarchy, a Markdown editor and full-text search, and is MIT licensed. Its README calls it intentionally narrower than larger wiki systems.
On xCloud the template runs the ghcr.io/perber/leafwiki v0.14.1 image as a single container, pinned by immutable digest, with a leafwiki_data volume. HTTPS is published on your domain, and login is required until you enable public access. Revision history, link refactoring and email are upstream options that this template leaves off.
A self-hosted wiki normally means a container, a data volume, a signing secret, an admin account, 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 LeafWiki from the OneClick catalog. Choose your domain and target server — there are no extra fields to fill in.
Step 02
One click. We bring up the official LeafWiki container, pinned by immutable digest, as a single service with no separate database, mount the leafwiki_data volume for the SQLite database, Markdown pages, uploads and snapshots, generate the admin password and signing secret, and publish it over HTTPS on your domain.
Step 03
Open your HTTPS LeafWiki URL and sign in as admin with the generated password from the protected credentials panel. Change the password from your profile, then create your first page with the + button in the sidebar.
LeafWiki runs in full here: a tree-structured Markdown wiki on your own domain, with its content kept in a volume you control.
Pages sit in an explicit hierarchy with manual ordering rather than a flat feed of notes, so a handbook keeps the shape you give it.
A built-in editor with live preview and autocomplete for internal page links, plus tables, task lists, callouts and Mermaid diagrams.
Search across titles and content, and filter by tags added to pages.
Admin, editor and viewer roles, with login required to read or edit until you choose to enable public read access.
Upload attachments to pages, import Markdown from a ZIP archive, and rely on a daily snapshot ZIP written into the data volume.
Content is SQLite metadata plus plain Markdown files on disk, so pages stay readable outside the app.
Managed hosting for LeafWiki, so the parts that keep it online are not your problem.
Organise pages in a tree and write them in Markdown, with full-text search to find them again.
Pages are Markdown files on disk beside a SQLite database, so your documentation is not locked inside a service.
One container, no external database and no cache service means little to maintain beyond backups.
Login is required by default, so only the accounts you create can read or edit pages unless you turn on public access.
Dedicated Cloud VPS sizes, pre-configured for LeafWiki hosting. Pick the one that fits, and resize any time.
A private wiki for one team's documentation.
$24.99per month
More headroom if LeafWiki sits alongside other tools 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. LeafWiki itself is licensed by its maintainers under the MIT license.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy LeafWiki 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.
LeafWiki 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 manifest asks for 1 CPU core, 256 MB of RAM and 1 GB of disk, and QA measured about 10 MiB idle. The 6 GB tier sold here leaves plenty of room above that, and attachments are what grow the disk.
Yes. LeafWiki is MIT licensed, per the LICENSE file at the v0.14.1 tag, so there is nothing to pay for the software; the xCloud bill is the dedicated Cloud VPS, and your pages and attachments stay on your own volume.
Yes, and this is LeafWiki Docker hosting prepared for you: the template runs the official ghcr.io/perber/leafwiki v0.14.1 image as one container, pinned by immutable digest, with a data volume and HTTPS, making it LeafWiki cloud hosting on your own VPS.
LeafWiki is a single Go binary with SQLite and Markdown on disk, per its README, while Wiki.js is a Node.js application. Wiki.js has its own xCloud page, so compare features, editors and how much you want to operate.
Use admin and the generated password shown in the protected credentials panel, then change the password from your profile. The first start takes under a minute while the database is created. The admin login only seeds the account on first start.
No. Login is required to read and edit pages unless you enable public read access with LEAFWIKI_PUBLIC_ACCESS in the Environment editor. Enable it only if you want anyone with the address to read the wiki, and check what is in it first.
LeafWiki signs login sessions with it, so a new value signs every user out. xCloud generates it at install; keep it stable when you edit the environment, and keep a private copy so a rebuilt server keeps the same sessions.
Attachments are limited to 50 MiB each. ZIP import and snapshot restore accept up to 500 MiB, but requests above about 100 MB are rejected when your domain sits behind the Cloudflare proxy. Split large imports into several smaller archives.
Revision history, link refactoring and SMTP email are opt-in upstream flags that this template leaves off, so do not rely on them being available. There is also no real-time collaborative editing and no single sign-on in this setup.
The leafwiki_data volume, plus your stable environment values. LeafWiki also writes a daily ZIP snapshot into that same volume, which is a convenience copy and not an off-server backup, so copy the volume elsewhere and test a restore.
Nothing upgrades it for you: the install stays on pinned release v0.14.1 until you adopt a newer template version. Back up leafwiki_data first, read the upstream release notes, then check sign-in and a few pages afterwards.
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.