DokuWiki is a free, open-source wiki that stores every page as a plain text file, so it needs no database at all. That single design choice makes it fast to install, trivial to back up, and easy to version with Git. Written in PHP, it runs on almost any shared host or cheap VPS. For small teams that want a self-hosted internal knowledge base without database admin work, DokuWiki has been a default pick for close to two decades, and it sits near the top of most self-hosted wiki shortlists.
This DokuWiki review covers what the software actually is, how the flat-file model works, its feature set, setup, and the honest limitations. If you want a broader view of the category first, the open source knowledge base roundup and the team wiki guide both frame where a tool like this fits. For a head-to-head with a database-backed rival, the BookStack review is the natural next read.
What is DokuWiki?
DokuWiki is wiki software first released in 2004 by German developer Andreas Gohr. It targets a specific job: documentation for small companies, developer teams, and internal knowledge bases. The current stable release is the 2026-07-14 "Mort" line, and the project ships named releases roughly once or twice a year on a steady, unhurried schedule.
The defining trait is storage. Most wikis write content to a MySQL or PostgreSQL database. DokuWiki writes each page to a .txt file on disk, in a readable wiki markup format. Old revisions get gzipped and kept in an attic folder. There is no database process to install, tune, or repair.
That approach has real consequences. Your entire wiki is a folder of text files you can copy, grep, and put under version control. A backup is a tar command. A migration is a file copy. Nothing is locked inside a binary database dump.
Who is DokuWiki for?
DokuWiki fits teams that value simplicity and control over polish. The typical user runs a small IT department, a developer team, an open-source project, or a club that needs shared notes. It suits an internal wiki where five to fifty people write runbooks, standard procedures, and reference docs.
It is a poor fit for anyone who wants a hosted, branded, public-facing product site with zero server work. It also frustrates teams expecting a modern block editor like Notion. DokuWiki asks you to run PHP and learn a light markup syntax. In exchange, it gives you a wiki you fully own.
DokuWiki vs BookStack vs a hosted option
Before the deep dive, here is the fast comparison people search for. It lines DokuWiki up against BookStack, the popular database-backed self-hosted wiki, and against a hosted platform like Docsio for public docs.
| Factor | DokuWiki | BookStack | Docsio (hosted) |
|---|---|---|---|
| Storage | Plain text files | Database rows | Managed cloud |
| Database | None required | MySQL / MariaDB | None to manage |
| Best for | Internal self-hosted wiki | Structured internal wiki | Public branded docs |
| Editor | Wiki markup + toolbar | WYSIWYG + Markdown | AI agent + editor |
| Hosting | You run PHP | You run Docker | Hosted with SSL |
The pattern is clear. DokuWiki wins on setup simplicity because there is no database to wire up. BookStack wins on editor comfort and content structure. A hosted tool wins when you want a public docs site live this week without touching a server. Different jobs, different tools.
How does DokuWiki work?
The architecture is deliberately plain. DokuWiki is a set of PHP scripts that read and write text files. When a visitor requests a page, PHP loads the matching .txt file, parses the wiki markup into HTML, applies your template, and returns the page. There is no database query in the loop.
Pages live in namespaces, which map directly to folders on disk. A page at team:onboarding:setup is a file inside nested team and onboarding directories. This gives you a folder-tree structure for free, and it means your URL scheme and your filesystem match one to one.
Every save writes the current version to the live file and pushes the previous version into the attic as a compressed revision. That is how page history works without a database table. Media files like images and PDFs sit in their own media folder with the same namespace layout.
Because everything is a file, standard Unix tools work on your whole wiki. You can search content with grep, track changes with Git, sync with rsync, and diff two backups with a plain file compare. Few other wikis give you that level of transparency.
Key DokuWiki features
DokuWiki keeps a focused core and pushes extras into plugins. The headline capabilities:
- Flat-file storage. No database. Content is readable text on disk, simple to back up and version.
- Access control lists (ACLs). Fine-grained permissions per namespace and per page, down to individual users and groups. You can lock a section to editors while keeping the rest public.
- Page revisions. Full version history for every page, with diffs between any two versions and one-click rollback.
- Plugin ecosystem. Well over a thousand community plugins add tables, tags, LDAP auth, diagrams, math, and more. Most install by unzipping into a folder.
- Templates. Swappable themes control the look. The default is dated, but templates like the community-favorite options modernize it quickly.
- Wiki markup with a toolbar. A quick-buttons editor sits above the text area for users who do not want to memorize syntax.
- Full-text search. A built-in indexer powers search across all pages without any external service.
- Media manager. Upload and organize images and files through the browser, sorted by namespace.
- Multilingual. The interface ships in more than fifty languages.
The core stays lean on purpose. Anything beyond the basics tends to be a DokuWiki plugin rather than a built-in feature, which is both the strength and the catch, covered in the limitations below.
DokuWiki setup overview
Installation is where the no-database model pays off. The steps for a self-hosted install are short:
- Check requirements. You need a web server (Apache, Nginx, or similar) and PHP. Nothing else. No database server, no message queue, no separate cache.
- Download and unpack. Grab the latest stable tarball from dokuwiki.org and extract it into your web root.
- Run the installer. Open
install.phpin a browser, set the wiki title, create an admin account, and pick an initial ACL policy. Delete the installer when done. - Start writing. Log in and create your first page. Namespaces appear as you use them.
The whole process usually takes ten to fifteen minutes on a fresh server. There is a one-click option too: many hosting panels and self-hosting tools like Cloudron or YunoHost offer DokuWiki as a packaged app. For a broader walkthrough of standing up a wiki from scratch, the how to create a wiki guide covers the planning side.
Backups stay just as easy. Because the wiki is a folder, a scheduled tar or rsync of the data directory captures every page, revision, and upload. Restoring is a copy back. No database dump, no import step.
DokuWiki pros
The strengths are consistent and hold up after years of real use:
- No database. The headline benefit. Fewer moving parts, faster install, simpler backups, and lower maintenance over time.
- Truly portable content. Plain text files you can move, search, and version with ordinary tools. Zero lock-in.
- Low resource use. DokuWiki runs happily on tiny servers and cheap shared hosting because there is no database process eating memory.
- Fine-grained ACLs. The permission system is one of the most granular in the self-hosted wiki space.
- Mature and stable. Two decades of releases, a large plugin library, and an active community mean most problems already have a documented answer.
- Free and open source. GPL licensed, no paid tier, no seat limits. You pay only for the server.
DokuWiki cons and limitations
An honest review has to name the trade-offs, and DokuWiki has a few real ones.
The default look is dated. Out of the box, DokuWiki looks like software from an earlier era. Templates fix most of it, but you have to go find and install one. The stock experience will not impress a modern audience.
Wiki markup, not Markdown. DokuWiki uses its own syntax, which differs from the Markdown most developers already know. It is easy to learn, but it is one more dialect, and pasting Markdown from elsewhere needs a plugin to convert cleanly.
Feature depth depends on plugins. Tables of contents, tags, advanced tables, and many other niceties come from community plugins rather than the core. Quality varies, and a plugin can lag behind a new release. Your setup is only as maintained as the plugins you rely on.
Scaling is possible but manual. Flat files work well into the thousands of pages, but very large or high-traffic wikis need caching and tuning that a database-backed tool might handle more gracefully. It scales; it just asks more of you at the top end.
Not built for public product docs. DokuWiki can serve public pages, but it gives you no custom-domain-plus-SSL workflow, no branded marketing shell, and no content generation. Public-facing documentation is not the job it was designed for.
Who should use DokuWiki (and who shouldn't)
The clear "yes" cases:
- Small teams that want a self-hosted internal wiki without running a database
- Developers and sysadmins comfortable with PHP and the command line
- Projects that want content under Git for full version control
- Budget-tight setups that need to run on minimal hardware
- Anyone who values data ownership and zero vendor lock-in
The "probably not" cases:
- Non-technical teams with nobody to run a server
- Teams that want a public, branded documentation site with SSL and a custom domain
- Writers who expect a modern WYSIWYG or block editor by default
- Very large organizations needing heavy real-time collaboration
A quick gut check: if your team is happy to SSH into a box, unzip a plugin, and write in a light markup syntax, DokuWiki will feel great. If any of that sounds like a chore, a database-backed or hosted tool will serve you better.
Best DokuWiki alternatives
No single wiki fits every team. The main alternatives, by use case:
- BookStack. The closest self-hosted rival. It uses a database and a shelves-books-chapters structure with a friendlier editor. If the dated look and markup of DokuWiki put you off, BookStack is the usual next stop, and the Wiki.js vs BookStack comparison covers a third strong option.
- Wiki.js. A modern Node.js wiki with a slick interface and Markdown editing. More capable UI, heavier server footprint.
- MediaWiki. The engine behind Wikipedia. Powerful for large public wikis, overkill and database-heavy for a small internal one.
- Docsio. For SaaS founders and small teams who want a public, branded docs site rather than a self-hosted internal wiki, a managed platform removes the server entirely. Docsio generates a docs site from your URL with AI, hosts it with SSL, and supports custom domains, so there is no PHP server to run or plugin to patch. It is the right pick when the goal is customer-facing documentation, not an internal knowledge base you maintain yourself.
DokuWiki stays the better choice for a private, self-hosted wiki you run on your own terms. The two categories rarely overlap, and plenty of teams run one of each: a self-hosted wiki for internal notes and a hosted docs site for the public product.
Frequently asked questions
What is DokuWiki used for?
DokuWiki is used to build internal wikis, knowledge bases, runbooks, standard operating procedures, and team documentation. Small IT departments, developer teams, and open-source projects run it as a private, self-hosted tool. Because it stores pages as plain text files, it also suits anyone who wants documentation they can version with Git.
Does DokuWiki need a database?
No. DokuWiki stores every page and revision as a plain text file on disk, so it requires no database at all. This is its defining feature. Installation, backup, and migration are simpler because there is no MySQL or PostgreSQL server to configure, and your entire wiki is just a folder you can copy or version.
Is DokuWiki free?
Yes. DokuWiki is free and open-source software released under the GPL license. There is no paid tier, no per-seat pricing, and no usage cap. You pay only for the server you run it on, which can be a cheap VPS or shared hosting. The plugin and template ecosystem is free too.
What is the best DokuWiki alternative?
It depends on the job. BookStack is the closest self-hosted alternative with a friendlier editor and a database backend. Wiki.js suits teams wanting a modern Markdown interface. For a public, branded docs site with hosting and SSL instead of a self-hosted internal wiki, a managed platform like Docsio is the better fit.
Final verdict
DokuWiki remains one of the simplest ways to run a self-hosted wiki, and the no-database design is still its best argument. Two decades in, it is stable, portable, and cheap to run, with a permission system and plugin library that few free rivals match. The costs are a dated default look, a markup syntax that is not Markdown, and a feature set that leans on community plugins.
If you want an internal wiki you fully control and you are comfortable with a PHP server, install DokuWiki this week. If your real goal is a public, branded documentation site with no server to run, that is a different tool. Docsio generates one from your existing website in minutes and hosts it for you. Match the tool to the job and either path is a good one.