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.

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.

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.

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.

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.

Your team's knowledge already lives in a folder of Markdown files, and CollabMD turns that exact folder into a shared workspace everyone can edit together in the browser, with nothing to migrate and no database swallowing your notes. Point it at an Obsidian vault, a plain docs directory, or a git-backed repository and the filesystem stays the source of truth: files are never moved, renamed, or deleted unless someone does it deliberately in the app. Several people can type in the same document at once with live cursors and presence indicators, follow a collaborator's view while they present, and drop comments anchored to a specific line or text selection instead of scattering feedback across chat threads. Edits made outside the browser, in Obsidian or any text editor, sync back into open documents automatically, so local and remote work never fork. Diagrams are first-class citizens: Mermaid, PlantUML, Structurizr C4 models, Excalidraw canvases, and draw.io files all open and render beside your prose, and a git panel lets you review changes and commit with a message without leaving the tab. Global full-text search, wiki-links with backlinks, team chat, file uploads, and optional password or Google sign-in round out a workspace that respects how your files already live. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

salt.md is an open-source, self-hosted workspace where your team and its AI agents work on the same documents and databases, under the same permissions and with the same history. A slash-menu block editor handles checklists, tables, callouts, columns, code, diagrams, and embeds. Page links, backlinks, and a graph view show how pages connect. Any page can become a collection with typed properties like select, date, person, relation, rollup, and formula, shown as a table, board, list, gallery, calendar, timeline, or form. Ctrl+K searches titles, body text, row values, and the text inside uploaded PDFs. Two people can type in the same paragraph at once with live cursors. Comments, page history, and an activity log record who changed what. Publish a page as a read-only link with an optional password and expiry, or hand people without accounts a form that adds rows to a collection. Agents connect over MCP with 33 tools for searching, writing, building databases, and commenting, using tokens scoped to one workspace or read-only. Signed webhooks, iCalendar feeds, and Google or Microsoft sign-in link it to the rest of your stack. Import Markdown, ZIP archives, or a Notion export, and export pages as Markdown, HTML, or PDF. Use it for handbooks, meeting notes, project boards, and a knowledge base your assistants can read. 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.

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.

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.

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.

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.

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 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 15,900 GitHub stars and 40,000 weekly npm downloads in its first two months, OpenWiki from LangChain has rapidly become the standard for AI-generated codebase documentation. Built on the Deep Agents framework, it deploys a documentation agent that reads your repository's source code, tests, and configuration, then synthesizes a complete linked Markdown wiki with architecture overviews, integration guides, data-flow diagrams, and validated Mermaid visualizations. Two operating modes cover distinct workflows: code mode generates repository documentation in an openwiki/ folder with automatic AGENTS.md and CLAUDE.md integration for Codex, Claude Code, OpenCode, and Cursor, while personal mode builds a local knowledge base from nine connectors including Notion, Slack, Gmail, X/Twitter, Hacker News, LangSmith, Custom MCP, Web Search, and local git repositories. Thirteen model providers are supported out of the box — OpenAI, Anthropic, Gemini, AWS Bedrock, GitHub Copilot, OpenRouter, Nebius, Fireworks, Baseten, NVIDIA NIM, and any OpenAI-compatible endpoint like Ollama or LM Studio. Grounded Claims track every material assertion back to versioned source evidence, flagging stale propositions before they propagate. The interactive visualizer renders wiki pages as an explorable node graph with a side-by-side Markdown reader, exportable as a static site for GitHub Pages or MkDocs. Self-updating CI workflows via GitHub Actions, GitLab CI, or Bitbucket Pipelines open documentation PRs automatically when code changes. 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 1,200+ GitHub stars since its April 2026 launch, Arkon provides an enterprise-grade knowledge management layer that turns scattered organizational documentation into AI-accessible structured context. The platform runs as a centralized MCP server, compiling your SOPs, policies, technical docs, and institutional knowledge into a versioned wiki with draft-approval workflows, then serving that wiki to Claude Desktop, Claude.ai, Cursor, and any MCP-compatible client through a single permission-scoped endpoint. OAuth 2.1 with PKCE authentication eliminates manual token management — employees authenticate through a browser login while the system discovers endpoints automatically via RFC 8414. The RBAC v2 system supports custom roles with granular permissions, department-scoped AI Skills, workspace isolation, and comprehensive audit logging so every query and access event is traceable. RAG retrieval powered by pgvector embeddings enables AI clients to search across all organizational documents with source attribution, while the AI Skills system lets teams define reusable instruction sets scoped to specific departments or roles. The architecture runs seven Docker containers coordinated by Compose: PostgreSQL with pgvector for embeddings and metadata, Redis for caching, MinIO for document storage, a FastAPI backend, two ARQ async workers for embedding generation and document processing, and a Next.js frontend portal accessible on port 3119. API keys are encrypted at rest with Fernet, and no telemetry leaves the deployment. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. PolyForm Internal Use licensed.

Sage Wiki turns a pile of unstructured documents into a fully interlinked, searchable wiki by running them through a five-pass LLM compiler pipeline. Inspired by Andrej Karpathy's vision of LLM-compiled knowledge bases, the pipeline processes source files through diff detection, summarization, concept extraction, image captioning, and cross-reference discovery, with parallel LLM calls and checkpoint/resume for vaults scaling to 100,000+ documents. The typed ontology graph stores entities and relations with BFS traversal, configurable relation types, multilingual synonyms, and a promotion/demotion lifecycle backed by grounding verification and consensus scoring. Multi-format ingestion handles Markdown, PDF, Word, Excel, PowerPoint, EPUB, email, CSV, images, and code files without manual tagging. LLM provider support spans Anthropic, OpenAI, Gemini, Ollama, and any OpenAI-compatible API, with per-pass model routing enabling cost optimization by assigning cheaper models to simpler tasks. The built-in MCP server exposes 17 tools over SSE transport for integration with Claude, Cursor, and any MCP-compatible agent, while native Obsidian vault overlay ensures existing note workflows remain undisrupted. Team deployment supports Git-synced shared wikis, centralized server access, and hub federation across multiple projects. Ships as a single Go binary with Docker Compose multi-arch images serving the web UI on port 3333. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Real-time collaborative Markdown behind your own firewall: HedgeDoc (formerly CodiMD, descended from HackMD's open-source edition) keeps team notes on team infrastructure. Share a note's URL and collaborators are editing together instantly - live cursors, changes appearing keystroke by keystroke - in a three-mode interface that toggles between raw Markdown, rendered preview, and side-by-side split. The Markdown dialect is extended where engineers need it: Mermaid, Graphviz, and Vega-Lite diagrams, MathJax for equations, syntax-highlighted code blocks, embedded content, and a presentation mode that turns a note into reveal.js slides with a single YAML header. A dropdown permission system controls each note - freely editable, limited to signed-in users, or locked read-only - and published notes become clean read-only pages for wider distribution. Revisions track every change with the ability to revert to any earlier version. The AGPL-3.0 codebase is light enough to run on a Raspberry Pi and deploys via Docker with PostgreSQL, MySQL, or SQLite. Authentication covers LDAP, SAML, OAuth2, and email. It deliberately stays a focused document editor - no page trees or kanban - and does that one job with excellent keyboard-first ergonomics for meeting notes, RFCs, runbooks, and shared scratchpads.

A project brief and the task board tracking it belong together, and Litpage keeps pages, databases, and team discussion in one self-hosted workspace instead of scattering them across subscriptions. Write in a block editor with 41 block types, a slash menu, markdown shortcuts, drag and drop, mentions, equations, and highlighted code blocks. The same data becomes a table, board, list, gallery, calendar, timeline, chart, dashboard, feed, form, or map, with typed fields, formulas, relations, and rollups underneath. Automations and buttons turn those databases into working tools, while templates keep repeated projects consistent. Teammates edit together live, comment, suggest edits, and revisit version history, with page-level and field-level permissions deciding who sees what. Pages can be shared publicly or published as sites, and Markdown, CSV, HTML, Word, and PDF files import into the tree. Optional AI runs on the provider and key you configure: chat that searches your workspace, custom agents on schedules or triggers, writing help, database autofill, and meeting-note summaries. Administrators get member and guest management, security policies, an audit log, analytics, passkeys, and two-step verification. A REST API with personal tokens, webhooks, and an MCP endpoint open everything to your other tools. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.