Skip to main content

Fully Managed MediaWiki
as a Service

Deploy MediaWiki as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

MediaWiki is the open-source wiki engine behind Wikipedia and thousands of community, enterprise, and government knowledge bases. It combines structured templates, wikitext, VisualEditor, fine-grained access control, and a deep extension ecosystem with the privacy and control of self-hosted infrastructure.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

MediaWiki

MediaWiki

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
MediaWiki Preview Image

ABOUT THE SOFTWARE

What is MediaWiki

MediaWiki is the open-source wiki engine that powers Wikipedia, Wiktionary, and every other Wikimedia project — and tens of thousands of independent community, enterprise, and government knowledge bases. Written in PHP, backed by MariaDB or PostgreSQL, licensed GPL-2.0-or-later, and maintained by the Wikimedia Foundation on a six-month release cadence.

Beyond Wikipedia, MediaWiki has powered NASA's EVA Wiki at Johnson Space Center (~30,000 content pages, 88,000 page views per month, 151 active contributors at the five-year mark), Intel's internal Intelpedia and Vistawiki, Novell's internal knowledge base, the US State Department's Diplopedia, the US Intelligence Community's Intellipedia, the Department of Defense's milWiki/milSuite, ArchWiki, Gentoo Wiki, and WikiLeaks. WikiApiary tracks 38,000+ independent MediaWiki installs across the public web.

FEATURES

What MediaWiki does

MediaWiki ships a wikitext editor and a VisualEditor for non-technical contributors, a templating system Wikipedia uses for its infoboxes, fine-grained namespaces and access control, a documented REST and Action API, and an extension ecosystem that covers structured queries, multilingual workflows, single sign-on, and spam control.

Wikitext + VisualEditor dual editing

MediaWiki ships both a wikitext syntax and a WYSIWYG VisualEditor backed by Parsoid, letting technical authors and non-technical contributors collaborate on the same page.

File uploads with thumbnailing via ImageMagick

Upload images, video, PDFs, and SVGs with sanitization. ImageMagick or GD generates thumbnails on demand. $wgUploadPath can point to local disk or S3-compatible object storage.

Action API + bot framework (Pywikibot)

A documented REST and Action API exposes every read/write operation. Pywikibot, the official Python framework, drives mass edits, imports, and CI/CD documentation pipelines.

Extension ecosystem

Thousands of extensions: Semantic MediaWiki 6.0.1 and Cargo for structured queries, Translate for multilingual workflows, AbuseFilter and ConfirmEdit for spam, PluggableAuth for SSO.

ParserFunctions, templates, and Scribunto/Lua

Build reusable content blocks with templates, parameterize them with ParserFunctions, and write performant logic in Lua via Scribunto — the same stack Wikipedia uses for its infoboxes.

Revision history, rollback, and FlaggedRevs

Every edit is versioned. Admins can roll back vandalism in one click, compare any two revisions, and gate publication behind reviewer approval using Extension:FlaggedRevs.

CirrusSearch on OpenSearch/Elasticsearch

Replace MediaWiki's built-in SQL search with CirrusSearch on OpenSearch 1.3 for sub-second full-text search across hundreds of thousands of pages, with title prefix completion and faceting.

Multilingual / interwiki + Translate

The UI is translated into 400+ languages on translatewiki.net. Extension:Translate adds page-level translation memory. Interwiki tables link cleanly across federated wikis.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed MediaWiki

Atlassian raised Confluence Cloud prices effective 15 October 2025 — Standard ~+5%, Premium ~+7.5%, Enterprise +7.5–10% — at the same time MediaWiki's 1.39 LTS hit end-of-life. The buyers who pick managed MediaWiki this year refuse to pay a third price hike or burn a quarter on a self-hosted upgrade.

Running MediaWiki in production is not what the install screen suggests. The wiki engine itself sets up cleanly. The work that hides behind it is keeping PHP, MariaDB, and the OS on compatible versions across every six-month release. Rebuilding the search index when CirrusSearch's underlying engine changes. Renewing SSL. Rotating image thumbnails when ImageMagick upgrades break SVG sanitization. Resolving Composer dependency conflicts when one extension demands a version of param-processor that another forbids.

The Composer issue is the one that catches teams. Install extensions via composer.local.json, run composer update, and Composer re-walks the entire dependency tree — including libraries MediaWiki core ships. It can quietly strip what the wiki needs. The first symptom is usually a blank page or HTTP 500. The bug is tracked at Phabricator P6481 and T173141, has been open for years, and is not fixable from the wiki's UI. We pin a tested matrix of extension versions to each MediaWiki point release so update.php runs clean on every customer's wiki.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run MediaWiki on DANIAN

The teams who land on managed MediaWiki tend to fit one of three profiles — a community wiki escaping a hostile host, an open-source project documenting itself, or an enterprise replacing a per-seat SaaS that's outgrown its budget. Their config choices reveal the platform's range.

40-PERSON GAME-COMMUNITY WIKI

Leaving Fandom after the Quick Answers rollout broke moderation

A 50,000-page game-community wiki moving off fandom.com to a self-hosted MediaWiki in Germany. Stack: VisualEditor + Parsoid for casual editors, CirrusSearch on OpenSearch 1.3 for prefix search, ConfirmEdit (QuestyCaptcha with game-trivia questions) plus AbuseFilter for spam, Scribunto/Lua for game-stat templates, Cargo for structured infoboxes, Discord webhook for edit pings, nightly XML dump to off-site object storage.

12-PERSON OPEN-SOURCE PROJECT

Replacing a static-site generator that couldn't keep up with release-note volume

A 5,000-page documentation wiki in France for an OSS project with users across 40 countries. Stack: Extension:Translate for multilingual workflows, CodeEditor + SyntaxHighlight_GeSHi for code blocks, Cite/Citoid for references, PluggableAuth + OpenID Connect against the project's GitLab, GitHub Actions webhook pushing release notes via the Action API on every tag.

1,200-EMPLOYEE ENTERPRISE

Migrating 80,000 Confluence pages after the October 2025 price hike

A private MediaWiki in US replacing Confluence Cloud for a US-based fintech. Stack: Semantic MediaWiki 6.0.1 + Cargo for structured policy queries, LDAPAuthentication2 against Active Directory, SimpleSAMLphp for SAML SSO, Lockdown for namespace ACLs, FlaggedRevs for SOP review workflows, encrypted-at-rest object storage for uploads, mysqldump replicated for 7-year retention.

COMPARISON

Four ways to run MediaWiki

Most teams pick MediaWiki because Confluence Cloud's per-seat math broke for them, Notion's data-control posture didn't fit, or both. The honest comparison is between four real paths — proprietary SaaS, a self-managed VPS, a home server, and DANIAN — at every plausible team size.

 PATH1 EDITOR5 EDITORS 10 EDITORS
Confluence Cloud Standard 
$5.42/user/mo annual, 10-user minimum
$54.20/mo
10-seat minimum
$54.20/mo
10-seat minimum
$54.20/mo
Self-host on a $24/mo VPS 
2 vCPU, 4 GB RAM, 80 GB SSD
~$44/mo + 1–2h/mo time~$44/mo + 2–4h/mo time~$44/mo + 4–6h/mo time
Home server 
Synology DS923+ NAS, ~€650 one-time
~€85/mo all-in + 2–4h/mo~€85/mo all-in + 4–6h/mo~€85/mo all-in + 4–8h/mo
DANIAN Managed MediaWiki€9/mo · 0 hours€9/mo · 0 hours€9/mo · 0 hours

Confluence Cloud Standard prices the 10-user floor regardless of team size; smaller teams pay the same as a 10-seat team. The $24/mo VPS path adds ~$5/mo for object-storage backup and ~$15/mo for production-class monitoring. At a freelance sysadmin rate of €60–120/hour, 4 hours of monthly ops time alone matches a year of managed-MediaWiki billing.

BY INDUSTRY

MediaWiki for specific industries

MediaWiki's templating, namespace ACLs, revision history, and Semantic-MediaWiki structured queries put it at home in environments where knowledge is regulated, multi-author, and long-lived. Five industries put specific demands on the platform — and on the people running it.

Research universities and graduate programs run MediaWiki for lab notebooks, course materials, and inter-departmental knowledge bases.

The platform handles long content lifecycles — a doctoral cohort spans 5–7 years — and the structured-citation patterns the rest of the web ignores.

By default, we ship Extension:SimpleSAMLphp wired to the institution's identity provider, Extension:Lockdown for namespace-level ACLs on coursework and research namespaces, and Extension:FlaggedRevs so a thesis advisor can mark a graduate student's lab notebook as advisor-reviewed before publication.

The 1.43 LTS branch carries security patches through 31 December 2027 — long enough to cover a PhD program end-to-end without an unplanned migration mid-thesis. 
Municipal, state, and federal agencies use MediaWiki for policy documentation, procedural manuals, and public-facing knowledge bases — the same pattern that produced Intellipedia, Diplopedia, and milSuite inside US government networks.

Public-facing wikis must meet WCAG 2.1 AA accessibility for citizens with screen readers.

We ship the 1.44+ skin updates that fix legacy heading-markup contrast issues, Extension:ApprovedRevs so a policy lead can hold draft revisions back from the public-facing render until they pass review, and a separate read-only namespace pattern for documents under retention.

Three of the largest documented MediaWiki deployments — Intellipedia, Diplopedia, and milWiki — all run inside US government networks.
Open-source projects use MediaWiki for documentation that survives maintainer turnover and tooling pivots. ArchWiki, Gentoo Wiki, and the Mozilla developer wiki are canonical examples.

License-tracking matters: documentation built on contributor patches needs SPDX headers and REUSE.software metadata to be reused downstream.

By default, we enable Extension:CodeEditor + SyntaxHighlight_GeSHi for the code-block-heavy editing pattern, Extension:Cite for inline references to issue trackers, and a service account with bot rights so a release-engineering pipeline can push version-specific docs via Pywikibot on every Git tag.

ArchWiki hosts more than 4,000 English content articles across 30+ languages — a single MediaWiki instance carrying the documentation for an entire Linux distribution. 
The largest MediaWiki migration story of the last three years is the steady exodus of fan-community wikis from Fandom — Hollow Knight in October 2023, the Trails / Ys / Falcom merger in August 2025, the Grand Theft Auto wiki in March 2026.

The trigger is consistent: ad load, mandatory features, and unmoderated AI Quick Answers that introduce factual errors no editor can remove.

Community admins running their own MediaWiki need DMCA safe-harbor procedures — Extension:RevisionDelete to suppress infringing revisions without breaking history, AbuseFilter rules tuned to copyright-flag patterns, ConfirmEdit (QuestyCaptcha) tuned with game-specific questions so spam bots fail without burning new contributors.

We ship all three configured out of the box and import Fandom XML dumps directly via importDump.php. 
Research labs, galleries, libraries, archives, and museums (GLAM) reach for MediaWiki when they need a structured-content store that interoperates with the broader scientific web.

FAIR data principles — Findable, Accessible, Interoperable, Reusable — map cleanly onto MediaWiki's namespace, template, and Semantic MediaWiki property model.

By default, we ship Semantic MediaWiki 6.0.1 (released August 2025) for typed properties, Extension:Cargo for tabular #ask queries, and Extension:ORCID so a researcher's experiment page can carry [[author::ORCID:0000-0002-...]] and feed a lab's full publication list as a single #ask query.

NASA's EVA Wiki at Johnson Space Center reached approximately 30,000 content pages with 151 active contributors at its five-year mark, averaging 88,000 page views per month. 

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

By default, every managed-MediaWiki instance includes the WMF-bundled set (Echo, DiscussionTools, Linter, LoginNotify, Thanks, VisualEditor, CirrusSearch, ConfirmEdit, Nuke, ParserFunctions, Scribunto, SyntaxHighlight_GeSHi, WikiEditor) plus Semantic MediaWiki, Cargo, Translate, PluggableAuth, AbuseFilter, and FlaggedRevs. Custom extensions install via composer.local.json.
Yes. VisualEditor and Parsoid have been bundled in core since 1.35, and we enable them on every wiki by default. Editors who prefer wikitext keep that option — the toolbar lets users switch per page. WikiEditor is enabled alongside for power users who want the classic source editor with syntax highlighting.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed MediaWiki for 7 days

No card. Cancel from the dashboard.