Pepperminty Wiki

Open-source wiki software, honestly reviewed. No marketing fluff, just what you get when you deploy a 200KB file on a PHP host.

TL;DR

• What it is: A complete, self-hostable wiki engine distributed as a single PHP file — no database, no complex stack, just upload and go [website][README].
• Who it’s for: Solo founders, hobbyists, and small teams who need a lightweight internal knowledge base and want zero server complexity. Not for teams that need Confluence-grade features or serious access controls.
• Cost savings: Confluence starts at $5.75/user/month (Cloud Standard); Notion at $8–$15/user/month. Pepperminty Wiki runs free on any cheap PHP host — including shared hosting for $3–5/month that you’re probably already paying for [3].
• Key strength: Genuinely the simplest self-hosted wiki deployment path available. One PHP file on a web server. No Docker required, no database provisioning, no environment setup. Flat files for storage means backup is a cp command [website][2].
• Key weakness: 206 GitHub stars, essentially a single-developer project with a slow release cadence. The feature ceiling is real — no real-time collaboration, no granular permissions beyond basic user roles, no REST API, and the Android app is still described as “a work in progress” [README].

---

What is Pepperminty Wiki

Pepperminty Wiki is a complete wiki engine contained in a single PHP file. The project’s own README calls it “a wiki in a box” [README], and that’s accurate in the most literal sense: you download one file, upload it to a directory on any PHP-enabled web server, and you have a functioning wiki. No MySQL setup, no Redis, no Docker Compose, no environment variables to wire up.

The project was developed by a solo developer (Starbeamrainbowlabs) and inspired by an earlier minimal wiki called Minty Wiki [README]. It stores content as Markdown files in a flat directory structure, which means your entire wiki is a folder of text files you can back up with a file copy, open in any text editor, or sync to GitHub. The license is MPL-2.0 — a weak copyleft license that lets you self-host and modify freely, but requires publishing changes to the core file if you distribute modified versions [README][3].

As of this review, the project has 206 stars on GitHub. That’s not a typo — 206 stars, not 206K. This is a niche, low-profile tool with a small but real user base. It appears in every major awesome-selfhosted list [3][4][5] and gets occasional mentions in r/selfhosted threads when people are searching for lightweight alternatives to heavier wiki engines [1].

The target use case is narrow but well-defined: you need a searchable, linkable, editable knowledge base that lives somewhere on the web, you want zero database overhead, and you’d rather not stand up a full application stack to do it.

---

Why People Choose It

The honest version: people choose Pepperminty Wiki when they’ve looked at the full wiki landscape and decided they don’t need most of it.

In a 2024 r/selfhosted thread comparing wiki options [1], Pepperminty Wiki appears in a list alongside BookStack, Wiki.js, DokuWiki, Outline, and a dozen others. The pattern in those discussions is consistent: people who mention Pepperminty Wiki are specifically reacting to the complexity of heavier alternatives. Wiki.js requires Node.js and a database. BookStack is PHP but still needs MySQL. Outline is excellent but demands PostgreSQL, Redis, S3, and careful setup. Pepperminty Wiki’s pitch is explicit contrast to all of that [website][2].

WikiMatrix’s comparison [2] describes the core proposition this way: “No database required! Simple flat file structure that scales to millions of words and 1000s of pages, and makes for easy backups too!” The scale claim (millions of words, thousands of pages) is plausible given that it’s just flat files, though at that scale you’d want to benchmark the full-text search engine rather than take it on faith.

The DevOpsSchool wiki comparison [3] and the Homelab wiki’s awesome-selfhosted list [4] both describe it the same way: “Complete markdown-powered wiki contained in a single PHP file. MPL-2.0 PHP.” No more, no less. That consistency suggests the tool’s reputation is exactly what it claims to be — not over-hyped, not under-appreciated, just exactly what it says.

The migration case study referenced in the README — a blog post by @SeanFromIT describing their move from MediaWiki to Pepperminty Wiki [README] — suggests the tool can serve as a viable replacement for setups that started on MediaWiki and found it overkill for their actual needs.

What people are not choosing it for: team collaboration at scale, granular access control, or feature richness. If your requirement is “my team of 12 needs a wiki where different departments can only see their pages,” Pepperminty Wiki isn’t the answer.

---

Features

Based on the README, website, and WikiMatrix feature listing:

Core content management:

• Markdown syntax via Parsedown [website][README]
• Full-text search with an “advanced query syntax” for power users [website]
• Page revision history (rollback supported) [website][README]
• Sub-pages and hierarchical organization [2]
• Page tags and tag-based filtering [website][README]
• Page lists and overview pages [website]
• Redirect pages [website]

Collaboration and users:

• Multiple user accounts with basic role management [website][2]
• Threaded per-page comments [website]
• Email notifications to verified addresses [website]
• Page protection (restrict editing) [2]
• Recent changes page showing who changed what and when [website]
• User watchlists [README]

Media and files:

• File upload (images, video, audio, and more) [website][README]
• File embedding in pages [website]
• Upload history shown in recent changes [website]

Usability:

• Built-in dynamic help page — covers Markdown syntax, redirect pages, and feature docs [website]
• Dark theme via prefers-color-scheme (auto-detects browser preference) [website]
• Multiple wiki-wide themes, including a “photo theme” for background customization [website]
• Accessibility support for assistive technologies [website]
• Android app for browsing and editing — available in beta on Google Play [website][README]

Deployment:

• Docker image available (sqlatenwiki/peppermintywiki) [README]
• Single-file installation option (upload index.php, done) [website]
• Online downloader for picking specific module combinations [website]
• Source build option for maximum control [website]

What’s missing or incomplete:

• The Android app is explicitly described as “a work in progress” with features added incrementally [website][README]
• iOS app: the README explicitly states this is “not practical for the foreseeable future” due to Apple dev licensing costs and ecosystem complexity [README]
• No REST API for external integration [merged profile]
• No SSO or LDAP [merged profile]
• No real-time collaboration (think Google Docs-style concurrent editing)
• Auto-update system is listed as a todo item, not a shipped feature [README]

---

Pricing: SaaS vs Self-Hosted Math

Pepperminty Wiki costs:

• Software license: $0 (MPL-2.0) [README]
• Infrastructure: whatever you’re already paying for PHP hosting, or $3–10/month for a basic VPS

What you’re replacing:

Confluence Cloud:

• Free tier: up to 10 users
• Standard: $5.75/user/month
• 5-person team: $28.75/month = $345/year
• 10-person team: $57.50/month = $690/year

Notion:

• Free tier: limited blocks, no version history
• Plus: $8/user/month (annual)
• 5-person team: $40/month = $480/year
• Business: $15/user/month for teams that need audit logs and SSO

Pepperminty Wiki self-hosted:

• Shared PHP hosting (if you don’t have it yet): ~$3–5/month = $36–60/year
• VPS (Hetzner Cloud, smallest tier): ~$4.50/month = $54/year
• Your existing web hosting: $0 marginal cost

The savings are real for small teams that need basic knowledge management rather than Confluence’s full project/space/permission hierarchy. A 5-person team replacing Notion Plus saves roughly $420/year. Data not available on exact feature overlap — if you genuinely need Notion’s database views or Confluence’s Jira integration, those features don’t exist in Pepperminty Wiki and the comparison breaks down.

The honest framing: Pepperminty Wiki competes with DokuWiki and other flat-file wikis on cost and simplicity, not with Confluence or Notion on features. If you’re paying for Confluence, evaluate BookStack or Wiki.js before evaluating Pepperminty Wiki — they’re closer feature peers.

---

Deployment Reality Check

This is Pepperminty Wiki’s strongest card, and it’s genuinely different from almost everything else in the self-hosted wiki space.

Installation path 1 (simplest): Download the prebuilt index.php from the releases page. Upload it to an empty directory on any PHP-enabled web server. Navigate to the URL. Done [website].

That’s it. No package manager, no npm install, no database provisioning. If you have shared hosting (cPanel, Plesk, or similar) that supports PHP — which is essentially all shared hosting since the 1990s — you can have this running in under 5 minutes.

Installation path 2 (Docker): The Docker image sqlatenwiki/peppermintywiki is available with documented pull counts [README]. This path makes more sense if you’re already running a homelab with Docker, and want Pepperminty Wiki alongside other containers.

Installation path 3 (custom build): The online downloader lets you select which modules to include, so you can build a leaner version without features you don’t need [website].

What you actually need:

• A web server with PHP enabled (most shared hosts, or nginx/Apache with PHP-FPM)
• Write permissions to the installation directory (for flat file storage)
• Optionally: a domain and HTTPS via Let’s Encrypt if you want it public-facing

What can go sideways:

• If you’re on managed shared hosting with strict file permission sandboxing, the flat-file storage may conflict with hosting policies
• PHP versions matter — older installations may have PHP compatibility issues depending on the release
• The auto-update system is listed as a todo, not shipped [README] — updates require manual file replacement, which means you need to be aware of releases yourself
• No migration tooling documented for moving from other wikis except the one community blog post about MediaWiki migration [README]

Realistic time to working instance:

• Technical user with a PHP host already available: 5–10 minutes
• Technical user spinning up a fresh VPS: 30–45 minutes including server provisioning, PHP setup, and domain configuration
• Non-technical user following a guide with existing shared hosting: 15–30 minutes
• Non-technical user with no existing hosting: factor in time to pick and configure a host first

This is the lowest deployment friction of any wiki engine reviewed on this site. That’s the accurate statement, not a marketing claim.

---

Pros and Cons

Pros

• Genuinely single-file deployment. Not “simple deployment” — literally one PHP file. The concept is not approximate; you really do upload one file [website][README].
• No database required. Flat file storage means no PostgreSQL, no MySQL, no SQLite setup. Backup is a folder copy. Portability is trivial [website][2].
• Works on any PHP host. Including cheap shared hosting you’re already paying for. No Docker, no VPS required (though both are supported) [website].
• MPL-2.0 license. Weak copyleft, commercially friendly, no usage restrictions for self-hosters [README][3].
• Decent built-in feature set. Full-text search, revision history, file uploads, tags, threaded comments, dark mode, user management — everything a small team wiki needs [website][2].
• Modular architecture. The online downloader lets you pick exactly which modules to include [website].
• Real-world usage exists. WikiProject Paranormal runs on it, there’s an active (if slow) development history, and it appears consistently in community recommendations [README][1][3].

Cons

• 206 GitHub stars and a solo developer. This isn’t a community-backed project — it’s one person’s open-source tool. That affects long-term maintenance risk materially [README].
• Android app is perpetually “in progress.” The README and website both flag this as a work in progress with incremental improvements. No iOS app and no plans for one [website][README].
• No REST API. You can’t build external integrations against it programmatically in any documented way [merged profile].
• No SSO/LDAP. If your team authenticates via Google Workspace, Okta, or any enterprise identity provider, there’s no integration path [merged profile].
• Manual updates. No auto-update system — listed as a future goal, not a current feature [README]. You need to watch for releases and replace files manually.
• Flat-file search performance ceiling. The full-text search is “performant” per the website, but flat-file search at serious scale (tens of thousands of pages) will eventually hit limits that database-backed wikis avoid structurally [website].
• Limited community support. With 206 stars and a Gitter chat room, you’re not going to find a lot of Stack Overflow answers or community plugins. If you hit an edge case, you’re reading the source code [README].
• Not suitable past ~20–30 users. The user management is basic — no fine-grained RBAC, no department-level access control, no audit logs [2][merged profile].

---

Who Should Use This / Who Shouldn’t

Use Pepperminty Wiki if:

• You want a personal knowledge base or a small-team internal wiki and have zero interest in running a database.
• You already have cheap shared PHP hosting and want to use it.
• Your backup strategy is “copy the folder to Dropbox.”
• You’re a solo founder who needs somewhere to document processes and decisions, not a full team collaboration platform.
• You want something that will still be running correctly in 5 years without version upgrades breaking everything.
• You’ve tried DokuWiki and found it confusing to configure — Pepperminty Wiki is simpler.

Skip it (pick DokuWiki instead) if:

• You want a flat-file wiki with a larger community, more plugins, and longer production track record.
• DokuWiki has been running stable at Wikipedia-adjacent scale since 2004 and has an extensive plugin ecosystem.

Skip it (pick BookStack instead) if:

• You need a well-organized knowledge base with a clear hierarchy (books → chapters → pages), proper team management, and a polished UI.
• BookStack is PHP + MySQL but the installation is well-documented and the UX is dramatically better for teams.

Skip it (pick Wiki.js instead) if:

• You need a modern, actively-developed wiki with SSO, LDAP, multiple storage backends, and a large feature surface.
• Wiki.js is more complex to deploy but much closer to Confluence in capability.

Skip it (stay on Confluence/Notion) if:

• Your team is larger than 10–15 people and depends on search, @mentions, structured templates, and permission hierarchies.
• The cost difference doesn’t justify the capability difference at your scale.

---

Alternatives Worth Considering

• DokuWiki — The grandfather of flat-file PHP wikis. No database, GPL-2.0, massive plugin ecosystem, production-proven at scale. More complex initial configuration but far more extensible [3][4].
• BookStack — PHP + MySQL, but polished “books/chapters/pages” structure, active development, good team features. Better UX for non-technical users despite higher setup complexity [1][3][4].
• Wiki.js — Node.js + database, modern UI, SSO/LDAP, Git sync, multiple storage backends. The obvious step up when you’ve outgrown Pepperminty Wiki [1][3][4].
• Outline — Excellent modern team wiki (think Notion minus databases), open source, good search. Requires PostgreSQL + Redis + S3 equivalent, so much heavier to self-host [1][3].
• TiddlyWiki — Single-file wiki (like Pepperminty Wiki) but runs entirely in the browser, storing everything in one HTML file. Excellent for personal use, not suitable for multi-user [3][4][5].
• Gitit — Wiki stored entirely in a Git repository. Good if you want your wiki content version-controlled by git at the filesystem level and you’re comfortable with Haskell dependencies [3][4].
• Raneto — Node.js, Markdown-based knowledgebase. Good for static documentation-style wikis, MIT licensed [3][4].

For a non-technical founder choosing between these: BookStack is the most common “I need a real team wiki” answer, DokuWiki is the “I want flat files but with more features” answer, and Pepperminty Wiki is the “I want the absolute minimum” answer. All three are valid depending on what you actually need.

---

Bottom Line

Pepperminty Wiki does exactly what it says and nothing more: it’s a complete wiki in a single PHP file with no database dependency. For a specific use case — solo founder or tiny team who wants a searchable, editable knowledge base on the cheapest possible infrastructure with the simplest possible deployment — it’s hard to beat on those terms. The tradeoffs are equally honest: 206 stars and a solo developer mean you’re accepting maintenance risk, the feature ceiling is real, and once your team grows past a handful of people you’ll be migrating to something else anyway.

If the only thing stopping you from having a team wiki is “I don’t want to deal with Docker and databases,” Pepperminty Wiki removes that blocker completely. If you actually need a real team knowledge management tool, start with BookStack instead.

If deploying any of this is the actual blocker, that’s what upready.dev handles — one-time deployment, you own the infrastructure, no recurring bill.

---

Sources

1. r/selfhosted — “Looking for a better Wiki” (2024 thread comparing wiki options including Pepperminty Wiki). https://www.reddit.com/r/selfhosted/comments/196e77w/looking_for_a_better_wiki/
2. WikiMatrix — “Pepperminty Wiki Features” (feature listing and tool description). https://www.wikimatrix.org/show/pepperminty-wiki
3. DevOpsSchool — “List of Top Free Open Source & Self Hosted Application for Wikis” (comparative wiki listing). https://www.devopsschool.com/blog/list-of-top-free-open-source-self-hosted-application-for-wikis/
4. The Homelab Wiki — “Awesome Selfhosted - Wikis” (curated self-hosted wiki list). https://thehomelab.wiki/books/helpful-tools-resources/page/awesome-selfhosted-wikis
5. AwesomeRank — “Awesome Rank for Kickball/awesome-selfhosted” (ranked awesome-selfhosted list). https://awesomerank.github.io/lists/Kickball/awesome-selfhosted.html

Primary sources:

• GitHub repository and README: https://github.com/sbrl/pepperminty-wiki (206 stars, MPL-2.0 license)
• Official website: https://peppermint.mooncarrot.space
• Docker Hub image: https://hub.docker.com/r/sqlatenwiki/peppermintywiki
• Documentation: https://starbeamrainbowlabs.com/labs/peppermint/__nightdocs/01-Welcome.html