Dokuwiki

Open-source wiki software, honestly reviewed. Two decades of plain-text storage, no vendor, no subscription.

TL;DR

• What it is: Open-source (GPL-2.0) wiki engine built in PHP. Stores all content in plain text files — no database, no SQL, no Redis [2][4].
• Who it’s for: Small teams, solo developers, and technical users who want a lightweight internal wiki on the cheapest possible hosting — shared hosting, a $5 VPS, even a Raspberry Pi [2][5].
• Cost savings: Confluence Cloud starts at $5.75/user/month and scales fast. DokuWiki runs on a $4/mo shared hosting plan with zero license cost [2][4].
• Key strength: Genuinely no-database architecture. If you can run PHP, you can run DokuWiki. It installs in minutes, survives on minimal hardware, and the plain-text file format means you never lose data to a corrupted database [2][4].
• Key weakness: The interface looks like 2008 and hasn’t caught up. No real-time collaboration. Many of its thousands of plugins are abandoned and may not work with recent versions [2][5].

---

What is DokuWiki

DokuWiki is a PHP-based wiki engine that launched in 2004 and has been in continuous development for over two decades. The project is maintained by Andreas Gohr and a community of contributors. As of this review it has 4,585 GitHub stars — modest by modern standards, but the project predates GitHub and the star count understates actual adoption [merged profile].

The defining architectural choice is no database. Every page, every revision, every upload lives in flat files on disk. This is either DokuWiki’s killer feature or its main limitation depending on what you’re trying to do. For a two-person team that wants a searchable wiki on shared hosting they already pay for, it’s a killer feature. For a 200-person company that needs to query, export, and integrate their knowledge base via API, it’s a problem [2][4].

The official description from the GitHub repo is blunt: “The DokuWiki Open Source Wiki Engine.” No marketing language, no tagline about transforming your workflow. It does one thing — structured, versioned, wiki-style documentation — and it’s been doing it reliably since George W. Bush was in his first term.

---

Why people choose it

The reviews we found are thin — three Capterra reviews and a handful of comparison articles — which itself tells you something about who uses DokuWiki. It’s not the kind of tool people evangelize on Product Hunt. It’s the kind of tool that quietly runs on a server for years without anyone thinking about it [5].

The no-database argument is real. Every comparison article eventually lands here. MakeTechEasier [2] puts it plainly: DokuWiki “runs without a database and works well on shared hosting or lightweight VPS plans.” This matters when you’re a non-technical founder or a small team that has a shared hosting plan they’re already paying for and doesn’t want to provision a PostgreSQL instance, manage connection strings, or worry about database backups. With DokuWiki, your backup strategy is literally “copy the data folder.” That’s not a joke — it’s a genuine advantage [2][5].

Twenty years of stability has its own value. The self-hosted space is littered with tools that launched with enthusiasm and went dark. DokuWiki has shipped continuously since 2004. If you set it up today, the probability of it still working in five years without you touching it is high. One Capterra reviewer notes they’ve been using it for two-plus years for internal company documentation, integrating custom plugins to pull data from their databases [5].

It runs on the cheapest possible infrastructure. PHP on shared hosting is the most commoditized web hosting stack on the planet. DokuWiki doesn’t need Node.js, a SQL database, Redis, or a modern server. It needs PHP. That means your $4/month shared hosting plan from 2019 probably runs it just fine [2][4].

The plugin ecosystem covers significant gaps. LDAP and Active Directory authentication are available via plugin. WYSIWYG editing is available via plugin. The core DokuWiki editing syntax is its own markup language, but you don’t have to learn it — plugins exist to make it feel more familiar [2][5]. A senior developer on Capterra called it “very easy to install” and noted that “many extensions fill its gaps” [5].

Where the reviews push back: the UI is dated. Three different Capterra reviewers, in three different languages, all arrive at the same observation. One says “everything looks a little dated” [5]. Another (a French developer) calls it “a generation behind” compared to Confluence or Notion [5]. The MakeTechEasier comparison notes that “its interface can feel old-fashioned” [2]. This isn’t a fringe complaint — it’s the consistent read from everyone who has used it recently.

---

Features

Based on the comparison articles and user reviews, here is what DokuWiki actually provides:

Core wiki engine:

• Plain-text file storage — no database required [2][4]
• Built-in version control: every edit is tracked, pages are diffable and reversible [2]
• DokuWiki markup syntax (custom, similar to other wiki markup formats)
• WYSIWYG editing available via plugin [2]
• Full-text search across all pages [4]
• Media manager for file and image uploads
• Page hierarchy via namespace structure
• Templating system for custom visual themes

Access control:

• ACL (access control list) system for per-page and per-namespace permissions [2]
• Native user management (users stored in flat files, no database needed)
• LDAP and Active Directory support via plugin — works for larger organizations [2]
• Multiple authentication backends via plugin (SAML, OAuth, etc.)

Extensibility:

• Thousands of plugins available through the official plugin repository
• Caveat: a meaningful portion of these plugins are no longer maintained and may break on current PHP versions [2][5]
• Template system for UI customization
• Developer API for building custom integrations

What it does not have out of the box:

• Real-time collaboration — one user edits a page at a time [2]
• Markdown support natively (plugins add it)
• REST API for programmatic content management
• Modern WYSIWYG by default (plugin required)
• Built-in analytics or usage tracking

---

Pricing: SaaS vs self-hosted math

DokuWiki has no SaaS version and no commercial license. The software is GPL-2.0 and costs nothing.

The relevant comparison for the target audience is what you’d pay for the SaaS alternatives DokuWiki replaces:

Confluence Cloud (Atlassian):

• Free: up to 10 users, limited features
• Standard: ~$5.75/user/month (10 users = $57.50/mo)
• Premium: ~$11/user/month (10 users = $110/mo)
• At 25 users on Standard: ~$143/mo

Notion:

• Free: limited block storage
• Plus: $10/user/month (10 users = $100/mo)
• Business: $15/user/month (10 users = $150/mo)

DokuWiki self-hosted:

• Software: $0 (GPL-2.0)
• Shared hosting that supports PHP: $3–6/mo (you probably already have one)
• VPS for a more serious setup: $5–10/mo on Hetzner or Contabo

Concrete savings math:

A 10-person team on Confluence Standard pays ~$690/year. On DokuWiki, they pay ~$48–72/year for the server — or nothing if they have hosting already. That’s roughly $600–640/year saved [4][2].

The catch: DokuWiki doesn’t match Confluence feature-for-feature. If your team actually needs Confluence’s structured page hierarchy, inline comments, Jira integration, or modern editing experience, DokuWiki isn’t a drop-in replacement. If your team needs “a place to write and find internal docs,” DokuWiki absolutely is [5][2].

---

Deployment reality check

DokuWiki’s install process is legitimately one of the easier ones in the self-hosted space. The requirements are minimal: PHP 7.2 or higher, a web server (Apache, Nginx, Lighttpd), and write permissions to a directory. No database to provision, no connection strings to configure, no Redis.

Standard install path:

1. Download the ZIP, extract to your web root
2. Point your browser to the install script
3. Set admin credentials through the web UI
4. Done

A technical user should be running in under 15 minutes. A non-technical founder following a guide for their first VPS should budget 30–60 minutes.

What can go sideways:

• Plugin compatibility. The plugin ecosystem is large but aging. A plugin that worked on an older PHP version may throw errors on PHP 8.x. You’ll need to research each plugin you want before installing [2][5]. One Capterra reviewer (a full-stack developer) specifically called out: “many extensions are abandoned and no longer maintained — it is difficult to navigate” [5].
• No real-time editing. If two people try to edit the same page simultaneously, one of them will get a conflict warning. This is by design but can frustrate teams used to Google Docs or Confluence’s collaborative editing [2].
• The editing interface has a learning curve. DokuWiki markup is not Markdown and it’s not WYSIWYG by default. One Capterra reviewer (a COO) notes that “editing and creation of new pages must be more easy” [5]. A French developer reviewer says it’s “more complex to learn than Confluence or Notion” [5]. This is addressable with WYSIWYG plugins, but it’s friction at onboarding.
• Backups are simple but manual by default. There’s no built-in backup system. Your data is in plain files, so copying the data directory works — but you have to set that up yourself.

For a technical team or a solo developer: this is not a hard install. For a non-technical founder who has never managed a server: budget a full afternoon and consider having someone deploy it for you.

---

Pros and cons

Pros

• No database. The flat-file architecture is the most distinctive feature in the wiki category. It runs on shared hosting, minimizes infrastructure complexity, and makes backups trivial [2][4].
• Minimal resource requirements. PHP only. Runs on hardware that would struggle with Node.js wikis. Suitable for Raspberry Pi or shared hosting plans you already have [2].
• GPL-2.0 license. Genuinely free software. No commercial license required, no usage restrictions, no “fair-code” terms [merged profile].
• 20+ years of active development. The project started in 2004 and is still maintained. That’s unusual staying power in the self-hosted space [5].
• Built-in version control. Every edit is tracked, every page is reversible, no external VCS required [2].
• LDAP/Active Directory out of the box (via plugin). Enterprise-grade auth is accessible without a SaaS upgrade [2].
• Fast install. A working wiki in under 15 minutes on any PHP-capable server [2][5].
• ACL-based permissions. Per-page and per-namespace access control — more granular than most tools in this category [2].

Cons

• The UI looks like 2008. Every third-party review and user quote reaches the same conclusion. The default interface is functional but dated [2][5].
• No real-time collaboration. One editor per page at a time. Teams that expect Google Docs-style simultaneous editing will be frustrated [2].
• Large portion of plugins are abandoned. The plugin catalog is big in number but inconsistent in quality. Some plugins are unmaintained and broken on modern PHP [2][5].
• DokuWiki markup syntax is not Markdown. The default editing syntax has a learning curve, and while WYSIWYG plugins exist, they’re not first-party [2][5].
• No REST API. Programmatic content management is not a first-class feature. Integrating DokuWiki into a workflow that needs to read or write pages via API is not straightforward [4].
• Not designed for large teams. The flat-file architecture that makes it simple also limits scalability. High-traffic wikis with dozens of concurrent editors will hit friction [2].
• Modest community activity. 4,585 GitHub stars is low for a 20-year-old project. The plugin ecosystem reflects this — investment in new features is slow [merged profile].

---

Who should use this / who shouldn’t

Use DokuWiki if:

• You’re a solo developer, small technical team, or hobbyist who needs an internal wiki and wants zero infrastructure complexity.
• You’re on shared hosting and refuse to provision a database just for a wiki.
• You want a wiki that will run unchanged for five years with minimal maintenance.
• Your team is technical enough to learn the markup syntax, or willing to install a WYSIWYG plugin.
• You want a GPL-licensed tool you can fully control and self-host without any license restrictions.

Skip it (pick BookStack instead) if:

• You want a modern, organized knowledge base with a clean UI that non-technical team members can use without training.
• You want Markdown editing and a database-backed search out of the box.

Skip it (pick Wiki.js instead) if:

• You need real-time collaboration where multiple people can edit simultaneously.
• You want modern authentication (OAuth, SAML, GitHub, Discord) without plugin hunting.
• You’re comfortable setting up Node.js and a SQL database and want a current-generation interface.

Skip it (stay on Confluence) if:

• Your team is already on the Atlassian stack (Jira, Bitbucket) and you need deep integration.
• Your compliance requirements mandate a vendor with SLAs and support contracts.
• Your non-technical team members need an onboarding experience that doesn’t require reading a wiki markup guide.

Skip it (pick Obsidian or Notion) if:

• You’re an individual looking for a personal knowledge management system — DokuWiki is overkill and under-featured for solo PKM use.

---

Alternatives worth considering

From the comparison articles and alternative listings:

• Wiki.js — the direct modern alternative. Node.js-based, SQL-backed, real-time collaboration, modern UI, Markdown-first. More infrastructure overhead, dramatically better editing experience [2][4].
• BookStack — organized around books, chapters, and pages. Clean UI, more intuitive structure for non-technical users, MySQL-backed. The recommended pick if DokuWiki’s interface is the blocker [4].
• MediaWiki — the software that runs Wikipedia. Extremely scalable, database-backed, battle-tested. Overkill for small teams; right for large knowledge bases with heavy traffic [3][4].
• Confluence — the incumbent commercial option. Best Atlassian integration, largest feature set, most expensive per user as teams grow [3][5].
• XWiki — open-source, database-backed, very extensible. More complex to set up than DokuWiki but more powerful for enterprise use cases [3][4].
• TiddlyWiki — single-file, runs in the browser with no server. Extreme simplicity for personal use, not suitable for team wikis [3][4].
• Outline — modern, Markdown-based, Slack-integrated team wiki. Requires more infrastructure but the editing experience is significantly better.

For a non-technical founder choosing between self-hosted wiki options, the realistic shortlist is DokuWiki vs BookStack vs Wiki.js. Pick DokuWiki if minimal infrastructure is the priority. Pick BookStack if the team includes non-technical members who need to write docs without friction. Pick Wiki.js if you need real-time collaboration and are comfortable with a heavier stack.

---

Bottom line

DokuWiki is a tool that has earned its longevity by doing one thing well: running quietly on cheap hardware without a database. It’s not the flashiest option in the wiki category — reviewers have been calling the interface dated for years, and that’s a fair read [5][2]. But for a solo developer or a small technical team that needs a simple, versioned internal wiki on minimal infrastructure, the no-database architecture and 20-year maintenance track record are genuinely hard to argue with.

The trade-offs are concrete: you give up real-time collaboration, a modern editing experience, and a well-maintained plugin ecosystem. What you get in return is a wiki that runs on a $4/month shared hosting plan, backs up as a folder copy, and will probably still be running without intervention in 2030.

If the dated UI or the single-user editing model is a blocker, BookStack or Wiki.js are the natural next step. If your team just needs a fast, cheap, versioned place to write internal documentation and doesn’t want to think about database provisioning, DokuWiki is still a defensible choice in 2026 — which is a remarkable thing to say about software that launched when Friendster was still a going concern.

---

Sources

1. DokuWiki Reviews — SourceForge (product listing and alternatives). https://sourceforge.net/software/product/DokuWiki/
2. Jo, Make Tech Easier — “DokuWiki vs Wiki.js: Which Self-Hosted Wiki Is Right for You?”. https://www.maketecheasier.com/dokuwiki-vs-wikijs/
3. Alternative.me — “10 Best DokuWiki Alternatives — Reviews, Features, Pros & Cons”. https://alternative.me/dokuwiki
4. SaaSHub — “DokuWiki Alternatives & Competitors”. https://www.saashub.com/dokuwiki-alternatives
5. Capterra New Zealand — “DokuWiki Pricing, Reviews & Features” (3 reviews, 4.7/5 overall). https://www.capterra.co.nz/software/205894/dokuwiki

Primary sources:

• GitHub repository: https://github.com/dokuwiki/dokuwiki (4,585 stars, GPL-2.0)
• Official website and documentation: https://www.dokuwiki.org