XWiki on MassiveGRID PaaS
XWiki is an open-source enterprise wiki and knowledge-management platform, widely adopted as a self-hosted alternative to Confluence. It combines rich editing, structured data, scripting and hundreds of extensions. The MassiveGRID PaaS package deploys XWiki with its Java server and database in one click.
Both buttons open the MassiveGRID PaaS dashboard with XWiki pre-selected. The trial needs no credit card.
XWiki Package Facts
| Attribute | Value |
|---|---|
| Package | XWiki |
| Type | Application (installs a complete environment) |
| Category | Websites & CMS |
| Software vendor / project | XWiki SAS |
| Licence | LGPLv2.1 (open source) |
| Runtime / stack | Java application server (Tomcat), MySQL/MariaDB or PostgreSQL |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use from $2.46/month ($0.003372/hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is XWiki?
XWiki goes beyond a documentation wiki. Pages can hold structured objects, forms and scripts, so teams build lightweight applications such as meeting notes, asset registers or CRMs inside the wiki. It offers page versioning, nested spaces, fine-grained rights, LDAP and SSO integration, a Confluence importer and an extension manager with more than 900 extensions. Since Atlassian ended Confluence Server, XWiki has become a common migration target.
As a Java application with a relational database, XWiki needs a properly configured servlet container. The marketplace package deploys Tomcat, links a database, and installs XWiki so you reach the distribution wizard in minutes. MassiveGRID is also an official XWiki hosting partner and offers a managed XWiki service for teams that prefer not to run it themselves.
What the XWiki Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure.
- Java application server: Tomcat running the XWiki web application with JVM memory settings tied to the environment's cloudlets.
- Database: A linked MySQL/MariaDB or PostgreSQL container for pages, attachments metadata and history.
- Permanent directory storage: Persistent storage for attachments, the Solr search index and extensions, with snapshots.
- Built-in domain and SSL: Immediate HTTPS on a platform subdomain; attach your own domain via Let's Encrypt.
Why Teams Choose XWiki
Confluence alternative
A dedicated importer and comparable feature set make XWiki the usual open-source destination for Confluence Server migrations.
Structured data and applications
App Within Minutes lets non-developers build form-based applications; scripting in Velocity or Groovy extends further.
Enterprise access control
Rights per wiki, space and page, with LDAP, Active Directory, OpenID Connect and SAML integration.
Extensible
Diagrams, Office import, blog, forum, task manager and more from the extension manager, installed with one click inside XWiki.
How to Install XWiki on MassiveGRID PaaS
Installing the package takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the XWiki package pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every XWiki node, wires them together and hands you the live URL and credentials.
Who Runs XWiki on PaaS
Teams leaving Confluence
Companies that want to keep their knowledge base on open-source software they host themselves.
Engineering documentation
Architecture docs, runbooks and specifications with versioning, diagrams and code macros.
Public knowledge bases
Product documentation and community wikis with public read access and controlled editing.
Why Run XWiki on MassiveGRID PaaS
Built for uptime. XWiki runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet XWiki environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: Managed XWiki Hosting · XWiki vs Confluence.
XWiki Questions
More from the Marketplace
Packages that are often deployed alongside XWiki, or that solve the same problem a different way. Browse all 84 packages.
Deploy XWiki Today
Start the free 14-day trial and have XWiki running in minutes. No credit card required.