Your company's knowledge should be a folder, not a subscription.

Most wiki tools are SaaS products. Notion, Confluence, Slite — you pay monthly, your documents live on their servers, and the day you stop paying, your knowledge base disappears behind a login wall. The content is yours in theory. In practice, it travels with the subscription.

DokuWiki is different in the way that matters: every page is a plain text file on disk. Your entire company knowledge base is a folder. You can move it, back it up, search it with standard tools, and read it with any text editor. No database. No proprietary format. No subscription.

Why plain text is the right format for company knowledge

A company wiki needs to outlast any individual tool. Processes documented today should be readable in ten years without any migration effort. Plain text guarantees this. A DokuWiki archive from 2005 opens in any text editor today with no conversion required. You cannot say the same about any SaaS wiki from 2005 — most of them do not exist anymore.

Plain text also means your wiki is AI-readable by default. A model can scan your entire knowledge base in seconds — all your SOPs, onboarding guides, supplier notes, process documentation — without any integration, API key, or data leaving your infrastructure. Try doing that with Notion.

What we use it for at La Nao

We maintain wikis for things that change slowly but matter consistently: standard operating procedures, supplier contact protocols, country-specific shipping and customs notes, onboarding guides for new team members, and the reasoning behind non-obvious decisions.

The distinction that has worked well for us: email handles things that are in motion; the wiki handles things that are settled. A supplier negotiation lives in email. The agreed process for handling that supplier's invoices lives in the wiki. When a new team member joins, they get the email archive for context and the wiki for procedure. Between the two, they have everything.

How it pairs with mailing lists

DokuWiki and mailing lists work together rather than competing. Discussions and decisions happen on the list, where they are archived and threaded. Once a decision solidifies into a repeatable process, it gets documented in the wiki. The email thread is the origin; the wiki page is the distilled result. Neither tries to be the other.

Setup is minimal

DokuWiki runs on Hetzner's shared webhosting plan — a few euros a month, no server to manage. No database to configure. Installation is uploading a folder via FTP and setting file permissions. The entire install, including all content, is a directory you can zip and move in seconds.

Access control is built in. Different teams can be given access to different sections. External contractors can be given read-only access to specific namespaces. Everything is handled in configuration files, not a user management dashboard with per-seat pricing.