Docuwiki

Open-source wiki software, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: A GPL-2.0 open-source wiki engine written in PHP that stores everything in plain text files — no database required [3].
• Who it’s for: Small teams, developers, and technical writers who want dead-simple internal documentation without standing up a database, running Confluence, or paying per-seat for Notion.
• Cost savings: Confluence Cloud starts at $5.16/user/month and scales fast. Notion runs $8–16/user/month per seat. DokuWiki is $0 in software cost, self-hosted on a $5–6/mo VPS with unlimited users.
• Key strength: No database. Flat files mean trivially simple backups, git-friendly version history, and a server that runs on almost nothing. It’s been in production since 2004 and shows no signs of dying [3].
• Key weakness: The default interface looks like it hasn’t been redesigned since 2008, because it mostly hasn’t. The plugin ecosystem can cover a lot, but the out-of-box experience isn’t what non-technical users expect in 2026.

---

What is DokuWiki

DokuWiki is an open-source wiki engine created by Andreas Gohr and licensed under the GPL v2. It’s written in PHP, has been in active development since 2004, and sits at 4,585 GitHub stars — modest for its age, but that’s partly because the project predates GitHub as the default hub for open-source collaboration and its community is primarily on the project’s own website and forums [merged profile][3].

The defining architectural decision is one that sets it apart from virtually every other wiki tool in the category: DokuWiki stores all content as plain text files. No MySQL. No PostgreSQL. No SQLite. Pages are files on disk, and that single decision has downstream consequences for everything — backups, migration, version control integration, server requirements, and disaster recovery [3].

The syntax is its own (DokuWiki syntax), described as similar to MediaWiki’s but not identical [3]. This is worth knowing before you commit, because your existing Markdown content won’t import cleanly. DokuWiki has its own formatting conventions, and while plugins can add Markdown support, the native experience is a custom markup language.

The project is maintained by a community of contributors under the split-brain GitHub organization. Unlike most tools in this review series, there’s no venture-backed company behind it, no commercial tier, and no enterprise upsell. It is purely open-source community software.

---

Why people choose it

The source material for this review is thin on third-party user opinions — most available reviews focus on enterprise alternatives rather than DokuWiki specifically [1][2]. What does exist points to a consistent profile: people who choose DokuWiki are choosing simplicity and longevity over features.

The no-database argument is the main one. For a team that just wants to write internal documentation, requiring a running PostgreSQL instance feels like overkill. DokuWiki eliminates that entirely. Everything lives in a folder structure of .txt files. Backing up your entire wiki is tar -czf wiki-backup.tar.gz /var/www/dokuwiki/data/. Moving it to a different server is copying that folder. Restoring from backup is copying it back [3].

The MSP and IT documentation use case is real. The managed services provider community in particular has historically used DokuWiki as a lightweight internal knowledge base before migrating to purpose-built tools like IT Glue or Hudu [2]. It fills a “good enough for cheap” slot where you want searchable internal documentation without a per-user licensing bill.

The plugin ecosystem extends the basics. While the core is minimal, there are over 1,000 community plugins covering everything from LDAP authentication to syntax highlighting, diagram rendering (via Mermaid or PlantUML), and full-text search improvements. The quality varies significantly across plugins; the core plugin set is stable, the long-tail plugins less so.

The longevity factor. A tool that has been continuously developed and deployed since 2004 isn’t going anywhere. For teams that have been burned by SaaS tools being acquired, pivoting, or sunsetting, a two-decade-old GPL-licensed project with flat-file storage is extremely hard to lock into.

---

Features

Based on the project documentation and what is widely established about DokuWiki:

Core wiki engine:

• Flat-file storage — all pages stored as plain text .txt files [3]
• Built-in revision history and diff viewing (no external VCS needed)
• Full-text search across all pages
• DokuWiki markup language (wiki syntax, not Markdown natively)
• Hierarchical namespace system for organizing pages
• ACL (Access Control List) — per-page and per-namespace read/write permissions
• Media manager for file and image uploads
• RSS feeds for recent changes
• Multilingual interface

Authentication and access control:

• Built-in user management (flat-file based)
• LDAP and Active Directory integration (via plugin)
• SAML support (via plugin)
• Multiple authentication backends (htpasswd, MySQL via plugin, etc.)
• Public, read-only, and fully authenticated modes

Template and extensibility system:

• Template (theme) system — swap the entire visual interface
• Plugin architecture for extending functionality
• 1,000+ community plugins in the official repository
• Plugin management through the admin panel (no manual file editing required)
• Popular plugins: discussion threads, diagram rendering, code block syntax highlighting, Markdown support, calendar

What’s not built in:

• Markdown natively (requires a plugin)
• WYSIWYG editing is limited compared to Confluence or Notion — the default editor is markup-based
• No real-time collaboration (last-write-wins on conflicts)
• No embedded database — can’t store structured data or build tables dynamically beyond basic formatted tables in wiki syntax
• No native API (REST API available via plugin)

---

Pricing: self-hosted math

DokuWiki is free software under the GPL v2. There is no commercial tier, no paid features, no enterprise license. The only cost is infrastructure [3].

Self-hosted:

• Software: $0
• VPS to run it on: $4–6/month on Kamatera, Hetzner, or Contabo [3]
• Minimum specs: 512MB RAM is enough for small teams; 1–2GB RAM comfortable for larger wikis
• Storage: depends entirely on how many files and images you attach; the text files themselves are negligible

Confluence for comparison:

• Free tier: 10 users max
• Standard: $5.16/user/month (100 users = $516/month)
• Premium: $9.73/user/month
• Self-hosted (Data Center): $27,000/year for 500 users

Notion for comparison:

• Free: limited block count
• Plus: $8/user/month
• Business: $15/user/month

Concrete savings math:

A 20-person engineering team on Confluence Standard pays $5.16 × 20 = $103/month, or $1,236/year. On DokuWiki self-hosted, that same team pays $6/month for VPS hosting, or $72/year. That’s $1,164/year saved — and the wiki has no user limit, so adding the next 20 people costs nothing extra.

The caveat: someone on your team needs to set it up and keep the server running. That’s a real cost in engineering time, even if it’s small.

---

Deployment reality check

DokuWiki is one of the simpler self-hosted applications to deploy, primarily because the absence of a database eliminates the most common source of configuration errors.

What you actually need:

• A Linux VPS with PHP 7.4+ (PHP 8.x recommended) [3]
• A web server (Apache or nginx) configured to serve PHP
• 256MB RAM minimum; 512MB+ comfortable
• No database software to install or configure

Installation steps (simplified):

1. Download the DokuWiki tarball from the official site
2. Extract to your web root
3. Set file permissions on the data/ directory
4. Visit /install.php in your browser to complete setup
5. Delete install.php after setup (security requirement)

That’s it. For a technical user, this is a 20-minute job including HTTPS setup with Certbot. Docker images exist if you prefer containerized deployment. Kamatera offers a one-click DokuWiki deployment for users who want a managed starting point [3].

What can go sideways:

• File permissions are the number one source of DokuWiki pain. If your web server user can’t write to the data/ directory, nothing works. The setup guide covers this, but shared hosting environments can make it fiddly.
• Plugin updates are manual. DokuWiki’s admin interface has a plugin manager, but it doesn’t auto-update. Running outdated plugins is a real security risk, and there’s no Dependabot equivalent here.
• Upgrading DokuWiki itself is more manual than tools with a proper package manager or Docker-based deployment. The process is download-and-overwrite, with careful attention to what to preserve.
• No built-in HTTPS. You need to handle that yourself via nginx/Caddy as a reverse proxy with Let’s Encrypt. Standard self-hosting requirement, but worth stating explicitly.
• Performance at scale becomes an issue without database indexing. Full-text search on a large wiki with thousands of pages can get slow. The bundled search is flat-file grep under the hood, and it shows.

For a technical user: 15–30 minutes to a working instance. For a non-technical founder following a guide: 1–2 hours including DNS and HTTPS. Docker deployment is faster if you’re already comfortable with containers.

---

Pros and Cons

Pros

• No database required. This is the feature that makes DokuWiki genuinely different from almost every other wiki. Backup is a folder copy. Migration is a folder copy. Recovery is a folder copy [3].
• GPL-2.0 license. Fully free software. No commercial tiers, no open-core, no “community edition” with artificial limitations. What you download is what you get [merged profile][3].
• 20+ years of stability. A project that has been maintained since 2004 is not going to evaporate next quarter [3]. For internal documentation, longevity matters more than features.
• Minimal server requirements. Runs on the cheapest VPS tier available. 256MB RAM is enough to get started [3].
• Excellent ACL system. Per-namespace and per-page read/write permissions are built in, not plugin-dependent.
• 1,000+ plugins. Most gaps in the core feature set can be filled with community plugins [established fact].
• No per-user licensing. Add 5 users or 500 — the cost doesn’t change.
• Built-in version history. Every edit is tracked without external VCS integration. You can diff and roll back any page.

Cons

• Interface hasn’t kept pace with modern expectations. The default look is functional but dated. Non-technical users coming from Notion or Confluence will feel the gap immediately. Themes help, but the overall UX is a 2004-era design philosophy.
• Not Markdown. DokuWiki uses its own markup syntax. Migrating content from Markdown-heavy tools (Obsidian, Notion, GitHub wikis) requires conversion work.
• Plugin quality varies wildly. The core plugins are solid; community plugins range from excellent to abandoned mid-2015 and untouched since. Due diligence required before depending on any single plugin.
• No real-time collaboration. Multiple people editing the same page simultaneously produces conflicts. DokuWiki has locking to mitigate this, but it’s not Google Docs.
• Search degrades at scale. Flat-file full-text search works fine for small wikis; it gets noticeably sluggish past a few thousand pages without additional indexing plugins.
• No structured data. Unlike Confluence with databases or Notion, there’s no concept of structured tables or relational content. Everything is freeform text pages.
• Manual maintenance. Updates, plugin management, and backups require active attention. There’s no hosted version with managed updates.
• No REST API in core. API access requires a plugin. For teams wanting to programmatically push documentation from their CI/CD pipeline, this adds a setup step.

---

Who should use this / who shouldn’t

Use DokuWiki if:

• You want internal technical documentation for a dev team or small company, and you’re not willing to pay Confluence’s per-seat pricing.
• You need a wiki that runs on minimal hardware — a $4/month VPS, a Raspberry Pi, an old laptop in your closet.
• Your team is technical enough to write in a markup language (or learn one quickly).
• Backup simplicity matters to you — flat files you can version-control or rsync are better for your workflow than dumping a database.
• You want software that will still be deployable in 10 years without worrying about the vendor.

Skip it (use Outline or BookStack instead) if:

• Your team expects a modern, polished interface. Both Outline and BookStack offer contemporary UX with self-hosted deployment while keeping costs low.
• You need Markdown natively, not via plugin.
• You want real-time collaborative editing.

Skip it (use Notion) if:

• You’re a small team willing to pay $8–15/user/month for the convenience of a managed, polished, feature-rich product.
• You need databases, relations, and structured content alongside your docs.
• Non-technical team members need to contribute without learning markup syntax.

Skip it (use Confluence) if:

• You’re in a large organization that needs enterprise SSO, audit logs, and deep Jira integration.
• You have the budget and need the native integrations with the Atlassian ecosystem.

Skip it (use a static site generator + git) if:

• You’re a developer team already living in git, and the wiki is primarily consumed by developers. MkDocs or Docusaurus with a git-backed editing workflow beats DokuWiki on every axis for that use case.

---

Alternatives worth considering

• BookStack — Modern UI, MySQL-backed, Markdown support, organized around “books, chapters, and pages.” Better onboarding for non-technical users. GPL-3.0 self-hosted.
• Outline — Clean interface, real-time collaboration, Markdown-native, Slack-connected. Business Source License (not fully open source), but self-hostable.
• MediaWiki — The engine behind Wikipedia. More powerful and more complex than DokuWiki. Requires MySQL. Better for very large public wikis. BlueSpice builds an enterprise distribution on top of it [1].
• Confluence (self-hosted) — Data Center edition. Purpose-built for teams, deep integrations, polished — but expensive at scale and increasingly Atlassian’s afterthought compared to their cloud tier.
• Obsidian + git — For personal or small-team knowledge management where Markdown and a local-first approach matter more than multi-user web access.
• Notesnook / Joplin — If the use case is personal notes rather than team documentation, these are simpler alternatives.
• Gitea/GitHub Wikis — If your documentation is code-adjacent and your team lives in git, a repository wiki is often sufficient without standing up separate infrastructure.

For a non-technical founder who just wants cheap, self-hosted internal documentation: BookStack vs DokuWiki is the real decision. DokuWiki if you want the absolute minimum infrastructure footprint and are comfortable with markup. BookStack if you want something that looks contemporary and your non-developer team members need to contribute.

---

Bottom line

DokuWiki occupies a specific and honest niche: it is the simplest possible wiki that still works properly. No database, minimal server requirements, GPL-2.0, and 20+ years of active maintenance. If that description matches your requirements, it’s an excellent choice and the math is obvious — software costs zero, hosting costs $5–6/month, and there’s no vendor to raise your bill or get acquired.

The honest trade-off is that “simple” extends to the UI. If your team expects Notion or Confluence, DokuWiki will feel like a step backward. It’s built for people who prioritize stability, portability, and operational simplicity over polished UX — and for that audience, it remains one of the most battle-tested choices in the category.

If you want DokuWiki running without dealing with the setup yourself, that’s exactly the kind of one-time deployment upready.dev handles for clients. You own the server, you own the data, and you’re not on a per-seat billing cycle ever again.

---

Sources

1. SourceForge — DokuWiki Reviews (software listing and alternatives). https://sourceforge.net/software/product/DokuWiki/
2. Evolved Management Blog — “MSP Documentation Systems” (Sep 25, 2024). https://www.evolvedmgmt.com/blog/msp-documentation-systems
3. Kamatera — “Scalable DokuWiki Hosting” (application page with technical specs). https://www.kamatera.com/applications/dokuwiki/

Primary sources:

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