DokuWiki

Open source alternative to Confluence, Notion, Nuclino and GitBook

4.7K stars
GPL-2.0
Active recently
Last commit 36 days ago

Last verified Nov 5, 2026

Host a wiki on plain text files with no database, built-in access controls, and over 1200 community plugins.

Visit website GitHub4.7K Deploy on Hostinger

Read the full breakdownWho it is for, how it works, trade-offs and the FAQ

who it's for

Who DokuWiki is for#

IT teams running a corporate intranet or knowledge base

DokuWiki's ACL system and authentication backends make it well-suited for an internal team wiki where different departments need different access levels. LDAP integration keeps user management in your existing directory rather than a separate wiki user store.

Skip if:

Skip if your team needs live database views, Kanban boards, or project tracking in the same tool. DokuWiki is a focused wiki, not a generalist workspace, and lacks the relational data features of Notion or Confluence.

Open source projects documenting software

DokuWiki covers the full software documentation use case: simple markup syntax, namespace-based content organization, and unlimited page revisions with diff support. Project maintainers can self-host a docs site with no cloud dependency and no recurring cost.

Skip if:

Skip if your documentation needs to be publicly polished with Git-synchronized content workflows. Static site generators with Markdown or GitBook are better fits for public-facing developer documentation.

Teams migrating away from Confluence

Teams leaving Confluence because of per-seat pricing or the Atlassian product direction can get a fully self-hosted wiki with built-in ACLs and no recurring cost. The plain-text file format makes DokuWiki data portable in a way a database-backed wiki is not.

Skip if:

Skip if your team depends on deep Jira or Bitbucket integrations. DokuWiki does not connect natively with the Atlassian ecosystem and would require manual workflow changes for teams that rely on Confluence-Jira linking.

the problem

The problem it solves#

Running a team wiki or knowledge base on commercial platforms means accepting per-seat pricing that scales with every new hire. Content stored in Confluence or Notion lives in a vendor's data format: exporting it cleanly is not straightforward, and moving to a different tool later means working around that format and its limitations.

The deeper pain is infrastructure dependency. These platforms require a live subscription and a third-party connection. Teams that have documented years of internal processes, software manuals, or project decisions in a hosted wiki face real switching costs when pricing changes or the product shifts direction. A flat-file wiki you host yourself sidesteps that dependency entirely.

how DokuWiki solves it

How it solves it#

No database required

DokuWiki stores every page as a plain text file on disk. There is no database server to install, configure, or maintain, which keeps the operational footprint small and backup trivially simple: copy the data directory to another location.

Built-in access control lists

Extended ACLs let you assign read, write, and admin permissions to users and groups at the namespace or page level. Authentication backends include LDAP, MySQL, Postgres, and others, so it integrates into existing directory infrastructure without a separate user database.

Over 1200 community plugins

The plugin ecosystem covers search enhancements, additional editor modes, authentication adapters, and content types well beyond the core wiki format. Over 100 templates are also available for layout customization, all contributed by the DokuWiki community.

Full revision history with diff support

Every page edit is stored as a revision with no limit on history depth. Colored side-by-side diff views let you compare any two revisions and see exactly what changed and when. Section editing lets contributors update a single part of a long page without touching the full document.

Index-based full-text search

DokuWiki builds and maintains a full-text search index across all pages. Page caching speeds up repeated queries, and an Ajax-enhanced interface means search results appear without full page reloads.

strengths · trade-offs

Strengths and trade-offs#

Strengths

Data portability through plain text filesEvery page is a text file in a directory on your server. Backup is a file copy. Migration is moving that directory. There is no proprietary export format and no vendor API standing between you and your content, which makes DokuWiki data portable in a way database-backed wikis are not.
GPL-2.0 with no seat limitsDokuWiki is GPL-2.0 licensed and free to run on your own infrastructure with any number of users. There is no per-seat fee, no commercial tier that restricts features, and no cloud plan required to unlock access controls or plugins.
Active development since 2004 with 4700+ GitHub starsDokuWiki has been in continuous development since 2004 with 4737 GitHub stars and 924 forks. The community has contributed over 1200 plugins, giving it broad extension coverage for a wiki engine of its age and scope.

Trade-offs

-Requires a PHP web server to runDokuWiki is a PHP application that runs on a web server. Setting it up means provisioning and maintaining a server with PHP support. It is not a one-command container deployment, so teams without server administration experience will face a steeper setup path than SaaS alternatives.
-Wiki markup syntax, not a block editorDokuWiki uses its own wiki markup syntax rather than a modern drag-and-drop block editor. Users accustomed to Notion or Confluence's visual editors will need to learn the markup, and the editing experience is closer to a text editor than a modern workspace tool.
-396 open GitHub issuesThe project carries 396 open issues on GitHub. For a tool active since 2004, the backlog reflects the breadth of edge cases and plugin interactions a PHP wiki engine accumulates over decades, and some feature requests have been open for years.

versus alternatives

DokuWiki vs alternatives#

DokuWiki vs Confluence

Both tools serve as team knowledge bases, but they differ on hosting model, cost, and data ownership. Confluence is a managed SaaS platform from Atlassian; DokuWiki is a self-hosted PHP application with no database.

Feature	DokuWiki	Confluence
License	GPL-2.0	Proprietary
Self-hosting	Yes	Cloud or Data Center (Server discontinued)
Storage	Plain text files	Database
Pricing	Free (self-hosted)	Per-seat subscription
Access controls	Built-in ACLs	Built-in

DokuWiki is the stronger pick for teams that need full data ownership, want to avoid per-seat costs, or are running a wiki on existing PHP infrastructure. Confluence is the better fit for large enterprise teams that depend on Atlassian integrations (Jira, Bitbucket) and prefer managed hosting or Atlassian Data Center over running their own server. Note that Atlassian has announced Data Center end of life for March 2029; Cloud is now the primary hosting option.

DokuWiki vs Notion

Notion is a block-based workspace covering notes, databases, and project tracking; DokuWiki is a focused wiki engine. The overlap is in team documentation and knowledge bases.

Feature	DokuWiki	Notion
License	GPL-2.0	Proprietary
Self-hosting	Yes	No
Data format	Plain text files	Proprietary
Pricing	Free (self-hosted)	Per-seat (free tier limited)
Database views	No	Yes

DokuWiki suits teams that want a text-based wiki with version history and no cloud dependency. Notion is the better fit when your team needs linked database views, Kanban boards, or a richer block editor that doubles as a project workspace.

DokuWiki vs GitBook

GitBook is built for public-facing developer documentation with Git sync and a polished reader experience. DokuWiki serves internal wikis, intranets, and software manuals.

DokuWiki is the right pick for internal team documentation where access controls, namespace organization, and self-hosting matter. GitBook is better when you are publishing public developer documentation and want a modern reading experience with Git-based content workflows and version branches.

DokuWiki vs Nuclino

Nuclino is a lightweight team wiki with a visual graph view and real-time collaboration; DokuWiki is a self-hosted, file-based wiki without built-in real-time co-editing.

DokuWiki is the better choice when self-hosting and data ownership are requirements, or when your team needs LDAP-integrated access controls. Nuclino is the right fit for teams that want a managed, real-time collaborative wiki with no server to maintain.

tech stack · detected from GitHub

What it's built on#

Languages: JavaScriptPHP

frequently asked

FAQ#

Does DokuWiki require a database?

No. DokuWiki stores every page as a plain text file on disk. There is no database to install, configure, or maintain. This is DokuWiki's most distinctive architectural choice and the reason backup is as simple as copying the data directory to another location.

What license does DokuWiki use?

DokuWiki is licensed under GPL-2.0. You can use and modify it freely for any internal team or commercial purpose without restriction. Distributing a modified version requires releasing those changes under the same GPL-2.0 terms.

How many plugins does DokuWiki have?

The DokuWiki community has contributed over 1200 plugins, covering extended authentication, additional editor modes, content types, and search enhancements. Over 100 layout templates are also available. The full list is in the official plugin and template repository at dokuwiki.org.

Is DokuWiki still actively maintained?

Yes. The repository at github.com/dokuwiki/dokuwiki shows the last push was September 2026, and the project has been in continuous development since 2004. It has 4737 GitHub stars and 924 forks, with an active community contributing plugins and translations.

How does DokuWiki handle multi-language content?

DokuWiki ships with support for over 50 interface languages and full UTF-8 encoding, so it handles non-Latin scripts correctly. Interface translations are community-contributed. Content itself is stored as plain text files, so multi-language page sets are organized through namespaces.

Looking for more

Other ways to replace Confluence, Notion, Nuclino and GitBook#

AppFlowy

#1 in the Notion guide

Full Notion replacement for small teams

78,085

AFFiNE

#2 in the Notion guide

Docs, whiteboards, and databases in one workspace

74,216

Outline

#3 in the Notion guide

Polished team wiki and internal knowledge base

41,170

Macro Docs

#4 in the Notion guide

Markdown-native docs that agents and teammates edit together

6,143

All 28 Notion alternatives 9 open source Notion alternatives, ranked

by category

Open source tools in these categories#

271

Business & Productivity

OpenClaw, Excalidraw, RustDesk 153

Communication & Collaboration

freeCodeCamp, iptv, Excalidraw

Hostinger

Self-host DokuWiki on a Hostinger VPS

Keep it running 24/7, even when your laptop is off. A Hostinger VPS gives it a server of its own.

01
Choose a plan
Starts from $6.49/mo
02
Apply
Extra 10% off yearly plans
03
Install DokuWiki
On a server that stays on
04
Start building
Focus on the app, not the server

Deploy on Hostinger

Inbox Zero

Alternative toSuperhuman

AI email assistant that drafts replies and clears your inbox

12,889 GitHub stars
Licence AGPL-3.0
#Email

rakazo

Alternative toGrok Bot

AI teammates you own: your keys, your model, your machine.

7,028 GitHub stars
Licence Apache-2.0
#AI Agents

SnitchFeed

Live monitoring on LinkedIn, X, Reddit & more. Agentic social listening for startups.

Marketing & Growth

Advertise your product

The projects we add and every new guide. Free, unsubscribe any time.

Find open source alternatives to paid software

DokuWiki vs Confluence

Feature	DokuWiki	Confluence
License	GPL-2.0	Proprietary
Self-hosting	Yes	Cloud or Data Center (Server discontinued)
Storage	Plain text files	Database
Pricing	Free (self-hosted)	Per-seat subscription
Access controls	Built-in ACLs	Built-in

DokuWiki vs Notion

Notion is a block-based workspace covering notes, databases, and project tracking; DokuWiki is a focused wiki engine. The overlap is in team documentation and knowledge bases.

Feature	DokuWiki	Notion
License	GPL-2.0	Proprietary
Self-hosting	Yes	No
Data format	Plain text files	Proprietary
Pricing	Free (self-hosted)	Per-seat (free tier limited)
Database views	No	Yes

DokuWiki vs GitBook

GitBook is built for public-facing developer documentation with Git sync and a polished reader experience. DokuWiki serves internal wikis, intranets, and software manuals.

DokuWiki vs Nuclino

Nuclino is a lightweight team wiki with a visual graph view and real-time collaboration; DokuWiki is a self-hosted, file-based wiki without built-in real-time co-editing.