PmWiki

PmWiki is a wiki-based content-management system for teams building and maintaining websites together. It suits administrators who need fine-grained page permissions and a database-free installation more than a managed, ready-to-use service. The trade-off is operational: contributors edit in a browser, but the owner must run and maintain the PHP environment.

Overview

Users can create and edit pages through the web without learning HTML or CSS, making PmWiki practical for community sites, internal documentation, and other shared content that changes over time. Pages are stored as flat files rather than in a database, and the project says this approach can handle thousands of pages. That can simplify deployment and backups for a technically capable administrator, while organizations that expect a hosted control panel will find the self-hosted model less convenient.

PmWiki has been developed since 2001 and supports custom domains, version history, API access, and self-hosting. Its current 2.7.6 release, dated September 18, 2026, includes updates for recent PHP versions. Release 2.7.5 addressed a vulnerability affecting versions 2.0.0 through 2.7.4 on Windows servers under certain editing and read-protection conditions; administrators should therefore keep installations current.

Key features

Granular permissions and authentication

Password protection can cover the complete site, a page group, or one page, with independent controls for reading, editing, and uploads. That granularity fits projects combining public material with restricted work areas. PmWiki can also use existing .htaccess, LDAP, and MySQL password databases, which is useful when access should align with credentials already managed elsewhere. The flexibility brings administration work: someone must design, review, and maintain the permission rules.

History, privacy, and recovery

Page histories provide restore links, and administrators can set how many days and revisions to keep. In version 2.7.6, edit IP addresses in histories are visible only to administrators, a narrower exposure for sites where contributor privacy matters. Retention is configurable, so owners can balance recovery options against storage and privacy requirements.

Customization and extensions

Skins and HTML templates can change the site's appearance and structure. Administrators can also alter markup and add functions through Cookbook recipes. This is a strong fit for teams willing to customize a wiki to their workflow; it is less suitable when a polished, standardized interface with vendor-managed extensions is the priority.

Pricing

The software itself has no subscription charge, seat fee, or stated usage quota. The free plan is appropriate for anyone able to supply hosting and PHP administration. Paid help is an optional service for owners who need implementation, troubleshooting, or bespoke development but do not want to handle all technical work themselves. Hosting and infrastructure costs are separate from these prices.

Platforms

PmWiki runs as self-hosted software on Linux, macOS, or Windows servers and is used through the web. PHP is required for the installation. This gives the owner control over domain, deployment, and data location, but it also means responsibility for server maintenance and upgrades.

Who it's for

Choose PmWiki for collaborative websites, documentation, or knowledge collections where page-level permissions, configurable history, flat-file storage, and extensive customization are important. It is particularly well matched to administrators comfortable with PHP hosting and authentication integration. Look elsewhere if you need a fully hosted product with no server upkeep or a fixed, vendor-managed feature set.

Pros and cons

Pros

• Granular access control: Site, group, and page protection can separately govern reading, editing, and uploads.
• Database-free storage: Flat files avoid a database dependency and are intended to scale to thousands of pages.
• Deep customization: Skins, templates, markup changes, and Cookbook recipes let administrators shape appearance and behavior.
• Recoverable editing: Configurable revision retention and restore links support rollback.
• No software license fee: The open-source, self-hosted plan costs nothing.

Cons

• Self-hosting is mandatory: The owner must provide PHP hosting and handle operational maintenance.
• Customization requires administration: Permissions, templates, markup, and recipes offer control but demand ongoing technical decisions.
• Support beyond community resources costs extra: Paid maintainer assistance is billed at 60€ per hour.

Alternatives

Browse Wiki Software or Knowledge base software for a wider shortlist.

• TiddlyWiki is another free, open-source option spanning mobile, desktop, web, and self-hosted platforms, with donations supporting development.
• Confluence is the better fit for a hosted freemium service, offering a free-forever tier for 10 users with 2 GB of file storage and three active whiteboards per user.
• Foswiki is a community-supported, free self-hosted alternative with API support.
• ikiwiki is free software for Linux, macOS, self-hosted, and web deployments.
• MediaWiki is free, GPL-licensed, self-hosted software with API support.
• MoinMoin is free GPL software for self-hosted deployments and multiple operating systems.
• Tiki Wiki CMS Groupware is free/libre open-source software for self-hosted Linux, macOS, Windows, and web use.
• TWiki is free GPL software requiring web-server administration.

Verdict

PmWiki is a strong choice for technically capable owners who want a free collaborative wiki with page-level security, flat-file storage, and broad customization. Its central advantage is control without a database or license cost. Choose a hosted alternative instead when avoiding PHP hosting and administrator responsibility matters more than that control.