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.

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.

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.

In seven wizard steps, PandaWiki sets up a product docs, manual, FAQ, or blog site whose built-in AI answers visitors using only your own content. Those visitors can chat with an assistant that cites its sources and accepts image questions, or switch to a docs-only search that lists ranked pages with summaries. Publishing stays under control: each document has three switches, visible in navigation, reachable by URL, and answerable by AI, and nothing appears or gets learned until it is published. Authors write in a Markdown and HTML editor, or import from URLs, RSS and Atom feeds, sitemaps, offline .txt, .md, .xlsx, .docx, and .pdf files, Notion, Yuque, SiYuan, Wiki.js, Feishu, Confluence, and DingTalk. Pages export to Word, PDF, or Markdown. The wizard covers models, domain, HTTP or HTTPS ports, import, publishing, answer testing, and page decoration. One knowledge base can also feed a web widget and DingTalk, Feishu, WeCom, and Discord bots. Administrators get a dashboard of visits, questions, visitor regions, hot documents, and referring domains. Chat models come from Baizhi Cloud, DeepSeek, OpenAI, or Ollama, while vector and reranking models are built in. The open-source edition covers one wiki site, 300 documents, and one admin, and its console and documentation are in Chinese. 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.

Every page in a DokuWiki knowledge base is just a plain text file on disk, so a team wiki can run for years on modest hardware with no database to feed, ever. Writers edit pages in a clean, readable syntax, fix just one section of a long document at a time, and lean on the toolbar, breadcrumbs, automatic tables of contents, and conflict locking to keep collaboration painless. Every change is kept as a revision with colored side-by-side diffs, recent-changes feeds go out over RSS, and an index-based full-text search finds content across thousands of pages in milliseconds. Namespaces organize content into a browsable tree, while built-in access control lists decide per page or per branch who may read, edit, upload, or administer, with logins checked against LDAP and other backends. Media uploads embed straight into pages, configuration happens in the browser, and the whole installation backs up by copying a folder, which makes migrations and disaster recovery almost boringly simple. When the basics stop being enough, more than twelve hundred community plugins and a hundred templates add galleries, multilingual structures, diagrams, and data tables without changing how the wiki itself works. 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 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.

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.

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.

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.

Tela keeps a team's documentation as canonical markdown in a self-hosted wiki that AI agents read, search, and write alongside humans through a built-in MCP server. People edit together with live multi-cursor collaboration, threaded comments, backlinks, and full revision history, so every page shows who changed what and why. PostgreSQL full-text search works immediately, and adding an embedder unlocks semantic retrieval and grounded ask-your-docs answers that cite their sources. Connect Claude, Cursor, or another MCP client with a personal access token and the agent can search the wiki, draft and patch pages, answer comment threads, build spreadsheets with real formulas, and assemble presentation decks exportable to PDF and PPTX. Atlas, the built-in documentation engine, points at a git repository or Jira project and drafts cited wiki pages, then keeps them fresh as the sources change. Teams organize work into spaces, invite members by email, and flip any space public to publish a login-free blog with per-author home pages. Content syncs over WebDAV and exports to zip or PDF, and optional AI features run against your own endpoint or a bundled local Ollama profile, so nothing leaves your server unless you wire it up. 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.

DocsMint is a self-hosted knowledge workspace where your team writes documentation once and both people and AI agents retrieve it through hybrid search and a built-in MCP server. Documents live in a rich visual editor with Markdown import and export, organized by folders, categories, and tags, with sharing and version history. Search blends exact title matches, multilingual keyword search, typo-tolerant fuzzy matching, and semantic vectors, then widens results through graph relationships between documents, so a query in one language or phrasing still finds the right page. Every edit quietly refreshes the index in the background; nothing needs manual re-embedding. Agents connect through 22 MCP tools covering search, reading, creation, updates, folders, snapshots, and export, over a local stdio bridge or the HTTP endpoint on your own installation. Category-scoped API keys hand each integration only the slice of the library it may read, edit, or write, while a global key serves trusted automation. The same operations are available through the REST API, a typed TypeScript SDK, and a terminal CLI for scripts. The web application installs as a PWA with offline reading, and AI features run on your choice of an OpenRouter key or a fully local Ollama setup. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 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.

Documentation deserves better than a database nobody wants to maintain. Typemill is an open-source flat-file CMS for informational websites, manuals, knowledge bases, and handbooks: content lives as Markdown files in folders, so a site can be copied, versioned, backed up, and moved with ordinary file tools and no database server anywhere in the stack. Authors get a visual block editor for nontechnical writing and a raw Markdown editor when precision matters, with a navigation tree, drag-and-drop structure, media library, page metadata, and publish states in one workspace. The same source then publishes three ways: as a themed website, as a printable PDF manual, or as an EPUB eBook through the eBook studio, making single-source publishing real for teams tired of maintaining docs, PDFs, and handbooks as three diverging copies. Themes are built from HTML and Twig; plugins add search, analytics, diagrams, math, and integrations; and an optional AI assistant interface connects writing help to the editor. User management, restricted pages, redirects, and a REST API cover the operational side, and the whole application is small enough to run comfortably on modest shared-style hosting or a tiny server while still feeling instant. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Gramax keeps your documentation in a Git repository as plain Markdown, gives writers a visual editor that feels like a word processor, and publishes the result as a searchable website. Writers format pages with tabs, tables, code blocks, embedded videos, and diagrams drawn in Mermaid, Excalidraw, or Diagrams.net, plus Swagger descriptions that render live API references. Every change is a normal Git commit, so review happens in pull requests on GitHub, GitLab, Bitbucket, or Gitea, and the full history of every page stays auditable. Catalogs organize articles into a hierarchy for a product portal, an internal knowledge base, or project documentation, and styles can be customized to match your brand. Teams moving off older tools import existing pages from Confluence and Notion with formatting and hierarchy preserved. Documentation can be written in 17 languages, with parallel catalogs for each audience. The editor runs on Windows, Mac, and Linux or straight in the browser, always working on local files that open in any text editor. A built-in AI agent answers questions over your catalog and helps draft pages from inside the editor. On the server, the portal container pulls fresh content from your repository on an interval you set, so publishing a page is just merging a branch. Readers get a dedicated, customizable documentation website instead of raw repository files. 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.

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.

Most wikis bury your writing inside a database you can never quite export cleanly; Mycorrhiza keeps every page as a plain file you can open, edit, and back up with ordinary tools. Each unit of content is a hypha, a page that can be an article, an image, or a video, and hyphae transclude and link to one another so related notes weave into a dense hypertext network instead of a stack of isolated pages. You write in Mycomarkup, a markup language designed to stay unambiguous while remaining quick to type, and categories organize pages without forcing a rigid hierarchy, although nested hyphae are there when you want one. Every edit is committed to Git automatically, giving the wiki a complete, inspectable history, and recent changes flow out as RSS, Atom, and JSON feeds. Keyboard shortcuts drive navigation for people who live in the editor, authorization supports plain accounts or Telegram login, and Open Graph metadata makes shared pages preview properly elsewhere. Interwiki links connect your wiki to others, and because there is no database to provision, a single small binary serves the whole site. 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.

Knowledge scattered across chat threads, tickets, and shared drives gets one permanent, searchable home in JSPWiki, a wiki engine that any team member can edit from the browser. Pages can be written in classic JSPWiki markup or in Markdown, and new syntaxes plug in alongside. Every page carries its own history through the versioning file provider, so edits can be compared and rolled back, and page locking keeps two editors from colliding. Files attach directly to pages, templates restyle the whole wiki, and three interchangeable search providers, including full-text indexing, make old decisions findable again. Access stays precise: authentication and per-page access control lists decide who can view or edit each page, which suits mixed audiences of staff, partners, and the public. Plugins and page filters extend rendering with dynamic content, and one installation can host multiple separate wikis for different teams. Readers get custom preferences and internationalized interfaces. Run it as a WAR on Tomcat or pull the Docker image and open port 8080. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache License 2.0 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.

Folio is a self-hosted team wiki that stores every page as a plain Markdown file in a Git repository you own, while your team writes together in the browser in real time. People work in Reading, Live edit, or Source mode, keep editing offline until the connection returns, and watch changes land in the page history as commits they can restore. Data tables with nine column types, filters, and views sit beside the documents, and forms write submissions straight into those tables without requiring an account. Whiteboards, Mermaid diagrams, and a visual diagram editor cover the pictures, while uploads like PDF, Word, Excel, and PowerPoint files open as previewable pages inside the tree. Confluence spaces import with their trees, images, and whiteboards converted, so a migration keeps its structure instead of flattening into a pile of attachments. AI agents read and write the same pages through an MCP server with 41 tools, authenticated by personal tokens or OAuth 2.1, and the built-in assistant answers questions read-only or makes supervised edits. Administrators control access down to a single page, sign people in with SAML, SCIM, or OpenID Connect, hand out expiring share links, and publish a space as a public read-only website. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

When an alert fires at 3 a.m., the live chart, the runbook, and the fix are already on one page of Oxynote, a self-hosted technical wiki. The chart is a Live Metrics block that runs its own Prometheus or SQL query and draws a time series, bar chart, or gauge. Several such blocks side by side make a dashboard inside the page. Around it, the editor works like Notion, with checklists, callouts, titled code blocks, Mermaid diagrams, Figma embeds, images, and files. Internal APIs get Stripe-style reference pages with the endpoint, a curl example, and a sample response beside the explanation. Mark a page reviewable and every edit lands in a draft. A block-aware diff shows renamed endpoints, fields, and reworded sentences in one red and green view until a reviewer approves. Freshness hooks watch GitHub files, container images, web pages, or dates, and remind maintainers when something a page depends on changes. Teammates edit together live and see who holds which block. Comments attach to a word, a diagram line, or a whole chart, with replies and an inbox for mentions. The Rubber Duck assistant edits pages and runs block queries with Anthropic, OpenAI, Google, OpenRouter, or a local Ollama model, and MCP lets Claude Code and Codex read and write the docs. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.