Wiki-Go turns a folder of Markdown files into a searchable team wiki with page history, comments, and access rules, and never asks you to run a database. Pages live in a nested tree with a sidebar and breadcrumbs, and an editor with a preview toggle handles emoji shortcodes, highlighted code, LaTeX math, Mermaid diagrams, collapsible sections, GitHub-style alerts, and embedded YouTube, Vimeo, or MP4 video. Full-text search supports exact phrases in quotes and term inclusion or exclusion, and highlights each match. Each save keeps a revision, up to a configurable limit, and any stored version can be restored later. Attachments such as PDFs, spreadsheets, images, and archives sit beside the page they belong to. Drop a Kanban board into any document for drag-and-drop task tracking with nested tasks, or build a categorized link library that fills in page metadata automatically. Signed-in users comment in Markdown, and admins can remove comments. Admin, editor, and viewer roles, user groups, path-based public or private rules, and an optional private-wiki mode decide who sees what. Branding comes from a custom logo, banner, and favicon, shortcodes such as stats insert live site statistics, and readers can switch between dark and light themes or print any page. A REST API opens content to scripts, and a community tool imports Notion exports. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Most wikis die of flat page-and-tag sprawl; BookStack's defining decision is enforced structure - an MIT-licensed PHP/Laravel platform (over MySQL) where content lives in a hierarchy of shelves, books, chapters, and pages, the way a physical library works. A shelf maps to a department, a book to "Engineering Runbooks," a chapter to "Database Procedures," a page to the actual document. That opinionation removes the "where does this go?" friction and keeps knowledge bases tidy as they grow. Editing works both ways: a clean WYSIWYG editor for most users, a Markdown editor with live preview for those who prefer it - switchable per page. Full-text search spans all books or scopes to one, with direct links to individual paragraphs, and include tags let you embed one page's content inside another so shared blocks update everywhere at once. Every edit creates a diffable, revertible revision. Page templates standardize recurring formats, tags add cross-cutting categorization, and built-in diagrams.net integration draws architecture diagrams in place. Authentication covers email/password plus OIDC, SAML2, LDAP, and social login; a full role and permission system locks content down per shelf, book, or page. Pages and books export to PDF, HTML, plain text, and Markdown, a REST API automates content, and the whole thing runs happily on the cheapest VPS you can find.

Team and product documentation on a fast Vue frontend with PostgreSQL storage: Wiki.js is a Node.js wiki engine. Its distinguishing trait is per-page editor choice: authors pick Markdown with live preview, a WYSIWYG visual builder for non-technical writers, or raw HTML, page by page. Native Git synchronization commits every page change to GitHub, GitLab, Bitbucket, Azure DevOps, or any Git remote - bi-directionally, so edits made in the repository flow back into the wiki - giving documentation version-controlled backup for free. Authentication coverage is among the broadest of any self-hosted wiki: local accounts with self-registration, social login via Google, GitHub, Discord, and Slack, and enterprise SSO through LDAP/Active Directory, SAML, CAS, Auth0, Okta, Azure AD, Keycloak, and generic OAuth2/OIDC, with optional MFA. Built-in full-text search runs on PostgreSQL with zero setup, and external engines like Algolia or Solr can substitute. Page history with visual version comparison, granular group-based permissions per path, nested navigation menus, 50+ integration modules, and full localization round it out. AGPLv3-licensed with a 28k-star community.

With MediaWiki, the wiki software behind Wikipedia, a team writes one shared knowledge base in plain wikitext or a visual editor while every revision stays saved for comparison and rollback. Page history names the author and edit summary of each change, and a side-by-side diff shows exactly what moved before anyone reverts. Talk pages hold threaded discussions with inline replies, notifications announce mentions and thanks, and watchlists flag the pages you follow. Namespaces, categories, redirects, and reusable templates give a large wiki its structure, and Lua modules written for Scribunto power infoboxes. Uploaded images get automatic thumbnails and a full-screen lightbox. Bundled extensions add PDF handling and math rendering for documentation that needs more than text. Group-based permissions decide who may read, edit, protect, or delete. A wiki can stay open to everyone or sit behind a login. AbuseFilter, CAPTCHAs, blocklists, and two-factor sign-in help fend off spam and account takeovers. Vector 2022 brings a sticky table of contents and an optional dark mode. The interface is localized in over 350 languages. Bots and scripts log in, read, search, and edit with the Action API. Use it for company handbooks, engineering runbooks, course notes, fandom encyclopedias, and public reference sites. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-2.0-or-later licensed.

Write your knowledge as plain Markdown files, and WikiDocs turns the folder into a searchable, versioned wiki with no database to set up or back up. Pages carry YAML front matter, so the whole wiki can be copied, archived, or opened in any text editor. An editor with a formatting toolbar handles headings, lists, task lists, links, and images, and pictures can be pasted straight from the clipboard. Math is typeset with KaTeX, Mermaid renders diagrams such as ER models and mind maps, and code blocks get syntax highlighting. Every save keeps a revision, a versions dialog lists them, and deleted pages wait in a trash where they can be restored or erased. Attachments upload and download from any page, namespaces build a page tree in the sidebar with pinned pages on top, and full-text search highlights every match. Public mode publishes a read-only knowledge base, private mode requires sign-in, and administrator and user accounts are managed in the app. Settings cover the wiki title, owner notice, privacy banner, language, timezone, light or dark template, and accent color, and every page has a print button. A desktop app keeps files on your computer and syncs with your self-hosted instance, while a REST API with Swagger documentation lets other tools read and write pages. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With over 140,000 code commits, 1,200+ GitHub stars, and continuous development since 2004 spanning more than two decades of active maintenance through version 18.6.0 released in July 2026, XWiki operates as a second-generation wiki platform that goes beyond static pages by enabling teams to build custom collaborative applications directly inside wiki pages using structured data forms and in-page scripting. The Java backend runs on Apache Tomcat with PostgreSQL, MySQL, or Oracle database storage, serving a responsive web interface with a WYSIWYG editor featuring real-time collaborative editing, link and macro editors, user mentions, inline comments, annotations, and complete version history with diff comparison. The App Within Minutes extension lets non-developers create custom data-driven applications using drag-and-drop form builders that generate filterable live tables for structured data browsing without writing code. Over 900 extensions from the built-in Extension Manager add functionality including blogs, task trackers, forums, diagram editors, and Confluence migration tools. Enterprise integration features include LDAP and Active Directory authentication, SAML and OIDC single sign-on, fine-grained per-page and per-space permissions with nested page hierarchies, and multi-wiki support for hosting multiple independent wikis from a single installation. The RESTful API provides programmatic access to pages, spaces, objects, attachments, and properties with XML and JSON representations. Office document import converts Word and Excel files directly into wiki pages while PDF export generates formatted documents from wiki content. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. LGPL-2.1 licensed.

Every wiki page lives as a plain-text file in a standard Git repository, giving you full version history, branching, merging, and the freedom to edit with any text editor or IDE alongside the web interface. Originally built by GitHub's founders as the engine behind GitHub's own wiki feature, Gollum supports Markdown, AsciiDoc, reStructuredText, Org-mode, Textile, MediaWiki, Creole, and Pod markup formats with live preview rendering as you type. PlantUML and Mermaid diagrams render inline for architecture documentation, MathJax handles mathematical notation, and BibTeX integration via Pandoc provides academic citation management. YAML frontmatter controls per-page sidebars, headers, footers, and table of contents generation. CriticMarkup annotations enable editorial review workflows with tracked insertions, deletions, substitutions, and comments. Macros extend pages with dynamic content injection, file includes, and navigation helpers. The wiki maintains compatibility with GitHub and GitLab wiki repositories, so teams can clone existing platform wikis for local editing and offline access. The official Docker image at gollumwiki/gollum exposes port 4567 with volume-mounted repositories, requiring roughly 170 MB of container storage and minimal RAM. Authentication integrates via OmniAuth supporting GitHub, GitLab, Google, and other OAuth providers. Over 14,300 stars on GitHub since 2009. MIT licensed.

Engineering teams and technical writers maintain operational runbooks, system documentation, and knowledge bases using LeafWiki, an open-source self-hosted wiki that stores page contents directly as human-readable Markdown files on the local filesystem. Authors can compose documentation through a dual-pane editor equipped with live HTML preview, keyboard navigation, autocomplete for internal links, and native rendering for Mermaid diagrams, KaTeX mathematical formulas, and collapsible callout containers. The navigational tree organizes complex documentation into explicit directory hierarchies and custom drag-and-drop page sequences tracked in lightweight configuration files rather than arbitrary alphabetical lists. An integrated SQLite engine indexes page content and custom taxonomy tags for fast full-text searches, automatic incoming backlink tracking, and automated broken link detection. System operators can deploy the single-binary application without external database servers or runtime dependencies, backing up the entire repository by copying the data directory. Administrators can provision granular user roles, configure reverse proxy header authentication for single sign-on gateways, and manage read-only API access keys for automated documentation scripts and continuous integration pipelines. Public viewers can browse technical notes without authentication or switch between dark and light high-contrast themes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Confluence and Notion both want your team's documentation in their cloud; Docmost, an open-source collaborative wiki platform, keeps it on your server. The centerpiece is a Notion-style block editor with CRDT-based real-time collaboration: multiple people edit the same page simultaneously and changes merge without conflicts or overwrites. Content lives in spaces - per team, project, or department - with nested page trees, role-based permissions, groups, inline comments, page history with restore, and full-text search across everything. The editor covers tables, code blocks, callouts, KaTeX math, and file attachments, and diagramming is built in rather than bolted on: Mermaid, Draw.io, and Excalidraw all render inside pages, alongside embeds for Airtable, Loom, Miro, and more. Migration paths include Notion, Markdown, HTML, and ZIP archive imports (Confluence, PDF, and DOCX importers ship in the Enterprise edition, along with SSO via SAML/OIDC/LDAP and MFA). The stack is TypeScript with PostgreSQL and Redis, deploys via Docker Compose, runs in air-gapped environments with no external dependencies, and is translated into 10+ languages. The AGPL-3.0 community edition carries no per-seat fees; the project has passed 20,000 GitHub stars since its 2024 launch.

Every page in Otter Wiki is a plain Markdown file and every save is a git commit, so a small team gets a simple wiki whose history never goes missing. The editor highlights Markdown as you type, offers a toolbar for headings, lists, tables, code, alerts, and images, and can show a live preview beside the source. Paste or drop an image into the editor and it is stored as a page attachment. History, blame, and changelog views, with RSS and Atom feeds, show who changed what and when. Beyond standard Markdown you get footnotes, task lists, math formulas, Mermaid diagrams, alert boxes, and spoiler or folded blocks, plus experimental embeddings such as sortable data tables, info boxes, image frames, videos, and included pages. A customizable sidebar shows a menu, a page index, or both. Search offers case-sensitive and regular expression options. Dark mode is built in. Admins decide whether anonymous visitors, registered users, or approved users may read, write, or upload, grant rights per user, close registration, or require email confirmation. An optional, experimental git web server lets people clone, pull, and push the wiki, and changes can be pushed to or pulled from a remote repository over SSH. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Enterprise documentation discipline without enterprise infrastructure: Documize Community is the Confluence alternative built on exactly that trade. The entire platform - Go backend, Ember.js frontend - compiles to a single executable binary for Linux, Windows, and macOS with zero runtime dependencies: no Elasticsearch, no Redis, no JVM. Point it at PostgreSQL, MySQL, MariaDB, Percona, or Microsoft SQL Server (rare in open source, decisive in Microsoft shops), and schema migrations run on launch with native full-text search on whichever engine you chose. Content organization rejects nested-folder sprawl for Spaces, categories, and labels, and the section-based composable editor mixes rich text, Markdown, code blocks, PDFs, diagrams, and embedded Jira or Trello content in one document, with reusable blocks and templates so teams start from standards rather than blank pages. It deliberately unifies internal team docs and customer-facing documentation in one system with granular space-, document-, and action-level permissions deciding who sees what. Where wikis stop, Documize continues: content approval workflows (draft, review, approve, publish), version management, lifecycle control, feedback capture, PDF export, analytics showing what gets read and ignored, activity streams, and audit logs. Keycloak, LDAP, and SSO integrate for enterprise auth. AGPL-licensed.

Writing docs should feel like editing a modern document, not wrangling Markdown files - CodeX Docs delivers that on Editor.js, the block-styled editor its CodeX team builds and thousands of products use. Content is composed from clean blocks (headings, lists, code, images, embeds) with a UI that reads well on both desktop and mobile, and pages render statically with human-readable, SEO-friendly URLs. Structure is free-form: pages nest to any depth, so a flat FAQ and a deep product manual coexist in one instance, and the UI tunes to fit - collapse sections, hide the sidebar. The operational footprint is deliberately tiny. No database is required: the default driver persists to a local folder, with MongoDB available when you want it, and the whole app configures through one YAML file (overridable with APP_CONFIG_ environment variables) covering title, start page, auth password, and JWT secret. Editing mode sits behind password authentication. Thoughtful extras are wired in: readers can report misprints straight to your Telegram or Slack, Hawk error tracking catches frontend and backend exceptions, and Yandex Metrica analytics is a one-line config. A ready-made Helm chart covers Kubernetes. Written in TypeScript.

The entire wiki - content, code, and interface - is built from "tiddlers," small addressable units of information that link, transclude, tag, and filter into each other: TiddlyWiki is a non-linear personal notebook with a design philosophy unlike anything else in this catalog. Instead of pages in a hierarchy, you compose views by pulling tiddlers together on demand, which is why researchers, zettelkasten practitioners, and GTD devotees have sworn by it for two decades. The whole application is JavaScript, and the UI itself is written in hackable WikiText - customization goes as deep as rewriting the interface from inside the wiki. Self-hosting runs the Node.js version, which upgrades the classic single-HTML-file architecture in the ways that matter for a server: every tiddler is stored as an individual text file (Git-friendly, organizable), edits save through the HTTP API from any modern browser including phones, and one installation can serve multiple wikis blending shared and unique content. The plugin ecosystem covers graph visualizations, themes, languages, and hundreds of community extensions, declared per-wiki in a simple tiddlywiki.info file; the newer MultiWikiServer plugin adds multi-user accounts and tiddler sharing. Your notes stay usable for decades, independent of any corporation - the project's founding promise. BSD-licensed.

"Somewhat lightweight, low-friction" is how Silicon Notes' author describes the personal knowledge base - written after DokuWiki's editor "drove me mad" and no existing wiki quite fit. The philosophy is that small frequent annoyances compound into cognitive load with no return, so everything here is optimized for frictionless daily use. Notes are written in plaintext Markdown and rendered as clean HTML with Pygments syntax highlighting for code blocks; pages get bi-directional relationships (backlinks), so the knowledge base becomes a connected web rather than a folder tree; and full-text plus title search retrieves anything fast. A table of contents lives in the left sidebar - "where it belongs" - editable while you read without scrolling away. Page history tracks revisions for auditing and rollback, JSON export/import keeps everything portable, and the mobile layout is genuinely usable. The stack is deliberately minimal: Python and Flask with Mistune for Markdown and SQLite for storage - no big frameworks, just a few small dependencies. One honest caveat: there is no built-in authentication, so deploy it behind a VPN, private network, or reverse-proxy auth layer. For a solo engineer's brain, it is exactly enough.

TriliumNext organizes notes in an infinitely deep tree where any single note can be cloned into multiple branches without duplication, building personal knowledge bases that mirror how ideas actually connect rather than forcing a single rigid folder hierarchy. Carrying forward the original Trilium project under active community stewardship with nearly 37,000 GitHub stars, the application is built on TypeScript with a CKEditor 5 WYSIWYG editor supporting rich text, tables, images, KaTeX math expressions, Mermaid diagrams, Excalidraw canvases, mind maps, spreadsheets with XLSX and CSV import/export, and code blocks with full syntax highlighting. A built-in JavaScript scripting engine runs on both frontend and backend, enabling custom widgets, automated workflows, scheduled tasks, and direct interaction with external REST services through a typed Script API. Full-text and fuzzy search with attribute-based queries locates any note instantly across databases tested at over 100,000 notes without performance degradation. The v0.104 release introduced importers for OneNote, Notion, Google Keep, Anytype, and Obsidian alongside 16 dedicated security fixes. Per-note AES encryption, OpenID Connect authentication, and TOTP two-factor protection safeguard sensitive content. The sync server keeps desktop clients, the progressive web app, and mobile devices in lockstep with zero third-party cloud dependency. Web Clipper captures content directly from browsers. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.