DokuWiki Hosting

How DokuWiki works

DokuWiki maps page names and namespaces to text files, then renders its wiki syntax as web pages. Namespaces create a hierarchy, links connect related material, and full-text search helps readers find information across the site. Because the source remains readable outside the application, administrators can inspect and copy documentation without first exporting a database.

Revision history records earlier versions so editors can compare changes or restore content. Built-in access control lists apply permissions to users, groups, pages, and namespaces. The media manager handles uploaded files, while plugins and templates extend syntax, authentication, navigation, and appearance beyond the standard installation.

Key DokuWiki features

The flat-file design keeps the relational-database requirement at Not required. Pages, revisions, media, indexes, configuration, plugins, and templates still form one application data set and must be protected together. Large media collections or extensive revision history can drive storage even though no PostgreSQL or MariaDB service is present.

Application email is disabled on the hosting service hosted services. Core writing, search, permissions, and revision workflows remain usable, but email-dependent registration, password recovery, notifications, or plugin behaviour should not be assumed. Plugins can also change security and resource requirements, so install only maintained extensions whose behaviour has been reviewed.

DokuWiki vs Confluence

DokuWiki provides a focused wiki based on plain text files, namespaces, revisions, access controls, plugins, and templates. Confluence is a provider-operated workspace for creating and sharing knowledge, with collaboration features and close connections to Jira and other Atlassian products. Both support team documentation but differ in storage and service model.

Confluence may suit organisations that want an Atlassian-hosted workspace, native Jira reporting, managed accounts, and a large integration ecosystem. DokuWiki is a stronger match when readable files, a lightweight wiki model, self-hosted permissions, and long-term documentation portability matter more than a broader commercial collaboration suite.

Who uses DokuWiki

IT teams maintain runbooks, developers document systems, researchers publish project notes, and communities create manuals or reference sites. Small companies use namespaces and ACLs to separate departments, while public projects combine searchable pages with downloadable media and contribution history.

DokuWiki is less suitable for teams that want database-style records, spreadsheet views, built-in video meetings, or a polished hosted office suite. Its syntax and plugin ecosystem reward deliberate administration. Readers and editors may need guidance on namespaces, markup, media naming, and permission inheritance.

Self-hosting DokuWiki: requirements and cost

Page count, revision history, search indexes, uploaded media, plugins, templates, authentication lookups, and concurrent readers determine resource use. DokuWiki is listed without a PostgreSQL or MariaDB service. Its plain-text core stays light, though large media archives and demanding extensions can require more capacity than the pages alone suggest.

On AvaHost, DokuWiki uses Plan 1 at €2. The hosted DokuWiki package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Application email is disabled, so mail-dependent registration, recovery, notifications, and plugins are unavailable. The package does not include Atlassian accounts, Jira, external identity providers, third-party plugins, or custom templates. Review permissions and extensions after updates, and keep a separate export or copy of critical documentation according to your policy.