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.

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.

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.

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.

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.

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.

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.

Transform complex code repositories into searchable, interactive wikis with DeepWiki, an automated documentation platform that maps architectural relationships and provides instant answers to technical questions about any codebase. Software engineers can submit public or private repositories from GitHub, GitLab, or Bitbucket to generate comprehensive project overviews, component breakdowns, and interactive Mermaid diagrams illustrating data pipelines and class hierarchies. The built-in Ask interface allows developers to query system logic using retrieval-augmented answers grounded directly in repository source files. Teams can trigger iterative deep research sessions that perform multi-step codebase investigations to explain intricate execution paths, uncover hidden dependencies, and summarize complex algorithms across hundreds of files. Interactive Codemap tours provide guided walkthroughs of critical entry points, letting reviewers inspect synchronized code viewer panels with exact line references while onboarding to unfamiliar services. Developers can export complete wiki structures for offline sharing, customize documentation depth from high-level summaries to granular module analyses, and connect local or cloud model endpoints to process sensitive internal code securely. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

OpenDeepWiki transforms code repositories from GitHub, GitLab, Gitee, Gitea, and AtomGit into structured, searchable knowledge bases by leveraging Microsoft's Semantic Kernel for AI orchestration across OpenAI, Azure OpenAI, Anthropic, and DeepSeek providers. The three-phase Gather-Think-Write pipeline analyzes repository tree structures, generates README summaries, project overviews, wiki catalogs, and document content while producing Mermaid mind maps and optional Graphify visualization artifacts. Repository-scoped MCP endpoints at /api/mcp/{owner}/{repo} expose indexed knowledge to external AI tools, while the built-in chat assistant, embedded chat APIs, and share links provide conversational access to repository understanding. The Next.js 16 frontend serves public documentation on SEO-friendly routes with multi-language translation support, and the admin console manages repositories, users, roles, API keys, AI provider and model configuration, skills, and GitHub App imports. Background workers handle incremental updates using LibGit2Sharp to keep documentation synchronized with evolving codebases, while Polly integration provides transient failure retry handling for LLM requests. The platform supports SQLite, PostgreSQL, and MySQL database backends with Entity Framework Core providers. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT 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.

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.

The de facto dashboard of observability: Grafana is the open-source frontend that turns the data stores you already run into interactive graphs. It does not store metrics itself; it connects to the data stores you already run and turns their contents into interactive dashboards. Supported sources number over 150 via plugins: Prometheus, Loki, Tempo, InfluxDB, Elasticsearch, MySQL, PostgreSQL, Microsoft SQL Server, AWS CloudWatch, Azure Monitor, Google Cloud Monitoring, and many more. Dashboards are built from a large library of panel types (time series, heatmaps, tables, gauges, logs) with template variables for reusable, parameterized views. Unified alerting evaluates rules against any connected data source, not just Prometheus, and routes notifications to Slack, PagerDuty, email, and other channels with grouping and silencing - unlike Prometheus Alertmanager, a single rule can combine a Loki log pattern, a PostgreSQL query result, and a CloudWatch metric. Dashboards serialize to JSON and data sources configure via provisioning files, so the entire observability setup can live in Git and deploy repeatably across environments. Explore mode adds ad-hoc querying outside dashboards, with split view for correlating a metric spike against the matching log lines, and access control spans organizations, teams, folder permissions, and OAuth, LDAP, and SAML integration. Written in Go and TypeScript, AGPL-licensed. Self-hosting gives you unlimited users, dashboards, and queries at flat hosting cost, without Grafana Cloud's usage-based pricing.

Across logs, traces, and metrics, Monoscope gives engineering teams one self-hosted workspace for finding what broke, asking questions in plain English, and hearing about problems before users do. Start in the Explorer: search events with KQL or an Ask AI prompt, flip between log rows, bar and line charts, log patterns, and sessions, and narrow results with facets for service, level, and HTTP status. Open any span to read its attributes, then follow the full trace across services in a waterfall, timeline, or map view. Live Tail streams new events as they arrive, and the Service Map draws every dependency with its error rate, latency, and requests per second. Build dashboards from widgets with copyable KQL and SQL, then set scheduled monitors with warn and alert thresholds, cron monitors, and uptime checks. An Issues inbox gathers API changes, errors, and log patterns so each one can be acknowledged, archived, or marked as spam, while Reports send scheduled summaries by email. Telemetry arrives over OTLP gRPC on port 4317 from OpenTelemetry SDKs and collectors. The monoscope CLI emits JSON for scripts, and an MCP server at /api/v1/mcp lets Claude, Cursor, and Cline search events and triage issues. Natural-language search uses the OpenAI-compatible model you configure. 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.

With 20,500+ GitHub stars and over 6,000 organizations running it in production — including a Fortune 100 company ingesting more than 4 PB per day — OpenObserve is the open-source observability platform that replaces your entire Datadog, Splunk, or ELK stack with a single Rust binary deploying in under two minutes. Apache Parquet columnar storage with zstd compression on S3-compatible object storage delivers 140x lower storage costs than Elasticsearch while providing better query performance on a quarter of the hardware. Ingest logs, metrics, and distributed traces via native OpenTelemetry OTLP endpoints with no vendor lock-in. Query logs and traces with standard SQL, metrics with SQL or PromQL — no proprietary query language to learn. The built-in dashboard builder offers 19 chart types including time-series graphs, heatmaps, gauges, tables, and top-K lists with drag-and-drop layout combining data from all signal types. Data pipelines process, enrich, redact, or normalize ingestion streams using Vector Remap Language for real-time transformations including PII redaction and logs-to-metrics conversion. Real User Monitoring captures frontend performance with session replay. The Service Catalog provides topology-based trace analysis with side-panel drill-downs into database queries and error details. Alerting supports real-time and scheduled rules with SQL and PromQL conditions. Native multi-tenancy isolates organizations and streams with complete data separation. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPLv3 licensed.