Cloud VPS 6 GB
Most popularA self-hosted knowledge base for a small team getting started.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Deploy XWiki hosting and run a self-hosted wiki platform for knowledge bases, structured content and document management on a domain you control. xCloud starts the pinned XWiki image beside a private PostgreSQL database, generates the database credentials and publishes the site over HTTPS. You create the first administrator yourself in XWiki's Distribution Wizard, which also installs the standard flavor and can take several minutes.
XWiki is an extensible open-source wiki platform for collaborative knowledge bases, structured content, attachments and document management, released under LGPL-2.1. Upstream describes the XWiki Platform as a generic wiki platform offering runtime services for applications built on top of it, with Administrator, Developer and User guides. Self-hosted XWiki is the option for teams that would otherwise keep documents in a hosted tool such as Confluence or SharePoint.
On xCloud the template runs the official xwiki 18.7.0 postgres-tomcat image beside a private PostgreSQL 17.11 container with no published port, both pinned by digest. Two volumes hold the wiki's permanent files and the database. It is a heavier stack than most: the manifest asks for 4 GiB of RAM and 2 CPU cores. Commercial XWiki Cloud, support and Pro Applications are separate upstream offerings and are not included.
Self-hosting an extensible wiki normally means a container, a private database, a domain and a certificate before a single page exists. This is the same result without assembling any of it.
Step 01
Create your xCloud account and pick XWiki from the OneClick catalog. Choose your site title, domain and target server — there is nothing else to fill in, since xCloud generates the database name, user and password.
Step 02
One click. We bring up the official XWiki 18.7.0 image, pinned by immutable digest, alongside a private PostgreSQL 17.11 sidecar, mount the xwiki_data and xwiki_database volumes, and publish it over HTTPS on your domain.
Step 03
Open the generated HTTPS URL, install the standard XWiki flavor, and create the first administrator. Review registration and access rights before adding private content, then create a page and attach a file to confirm search indexing.
XWiki runs in full here — pages, attachments, access controls, extensions and structured content, on infrastructure you control.
Build a searchable company knowledge base or internal documentation hub, instead of scattering docs across shared drives and chat threads.
Create wiki pages with attachments and access controls, so teams can write and file supporting documents in one place.
Extend the standard flavor with XWiki applications and structured content as your needs grow, without re-platforming.
PostgreSQL stays private with no host port at all; only the XWiki web interface is proxied over HTTPS.
Wiki records and XWiki's permanent data persist across an xCloud Restart on two declared volumes, not the container's own filesystem.
A good fit for internal knowledge bases, product and engineering documentation, team intranets and policy libraries.
Managed hosting for XWiki, so the parts that keep it online are not your problem.
Teams can keep documents and structured content together, with attachments and permissions, in a wiki whose pages and users live in PostgreSQL on a server they control.
Upstream describes XWiki as a platform for applications built on top of it, so a developer can extend the wiki with its own structured content and logic.
After the Distribution Wizard, review registration and access-right settings so that private areas stay private while public documentation stays readable.
Move handbooks and procedures from shared drives into one searchable wiki with attachments, so staff look in one place instead of asking around.
Dedicated Cloud VPS sizes, pre-configured for XWiki hosting. Pick the one that fits, and resize any time.
A self-hosted knowledge base for a small team getting started.
$24.99per month
More headroom for a larger wiki and more concurrent editors.
$59.99per month
XWiki alongside a larger self-hosted documentation 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. XWiki itself is free under the LGPL-2.1 licence.
Connect any VPS — DigitalOcean, Vultr, Linode, AWS, Hetzner or bare metal — and deploy XWiki 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.
XWiki 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.
XWiki is used to build knowledge bases and structured wikis that many people edit together. Teams keep documentation, attachments and structured content in one place, and developers can build applications on top of the platform. It suits organisations that want a wiki they can extend and host on their own server.
Yes. XWiki and its official Docker image are open source under the LGPL-2.1 licence, so there is no licence fee for the wiki. Commercial XWiki Cloud, support and Pro Applications are separate upstream offerings that this template does not include. On xCloud you pay for the Cloud VPS that runs the stack.
Yes. For XWiki Docker hosting the template runs the official xwiki 18.7.0 image with Tomcat and a private PostgreSQL 17.11 container, both pinned by digest, with two named volumes. It generates the database name, user and password and attaches HTTPS on your domain without any compose file from you.
The template manifest asks for 4 GiB of RAM, 2 CPU cores and 20 GiB of disk as a starting requirement. The 6 GB Cloud VPS sold here sits close to that floor, not far above it, because XWiki runs on Java with a database beside it. A busy wiki with many users should move to a larger size.
It is XWiki's own first-run setup. When you first open the site, the wizard installs the standard flavor and asks you to create the first administrator. Startup and flavor installation can take several minutes, and you should not interrupt the container while extensions are installing. xCloud does not store the administrator credential.
An XWiki backup covers both volumes taken at the same moment: xwiki_database holds pages, users, permissions and metadata, and xwiki_data holds permanent configuration, extensions, logs, search data and attachment-related files. Stop writes or the stack, take a PostgreSQL-consistent dump, keep it off-server and test a restore.
A catalog re-sync never touches a running XWiki 18.7.0 site, since both images carry digests. Save both volumes, read XWiki's release and upgrade notes, then select a later template version that raises the images together, and check the wiki and its extensions after the restart.
This template pairs XWiki with a private PostgreSQL 17.11 container on the internal network, without any host port. xCloud generates the database name, user and password, which appear in your credentials for backup and recovery. The database holds the wiki pages, users and permissions, so protect it first.
You do, inside the Distribution Wizard the first time you open the site. The install form has no XWiki-specific fields, and xCloud does not generate or display an administrator password. After the wizard, review registration and access-right settings before adding private content.
Yes. Under XWiki cloud use, xCloud provisions a dedicated Cloud VPS, runs the wiki and PostgreSQL on it and attaches your domain and certificate. The Java stack is heavy, so size the server for it. Another provider's machine can be attached as a self-managed server.
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.