Diff: reference/wiki-provider-landscape.es
From 4bd58eb to 4bd58eb
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| schema: foundry-doc-v1 | schema: foundry-doc-v1 |
| title: "Wiki provider landscape" | title: "Wiki provider landscape" |
| slug: wiki-provider-landscape | slug: wiki-provider-landscape |
| short_description: "An audit of 25 wiki platforms across four groups documents structural reasons no competitor has closed Wikipedia's encyclopedic gap, and identifies the governance software, navigation primitives, and editorial culture required to do so." | short_description: "An audit of 25 wiki platforms across four groups documents structural reasons no competitor has closed Wikipedia's encyclopedic gap, and identifies the governance software, navigation primitives, and editorial culture required to do so." |
| status: active | status: active |
| category: reference | category: reference |
| type: topic | type: topic |
| quality: complete | quality: complete |
| last_edited: 2026-05-14 | last_edited: 2026-05-14 |
| editor: pointsav-engineering | editor: pointsav-engineering |
| audience: vendor-public | audience: vendor-public |
| bcsc_class: no-disclosure-implication | bcsc_class: no-disclosure-implication |
| paired_with: wiki-provider-landscape.es.md | paired_with: wiki-provider-landscape.es.md |
| cites: | cites: |
| - ni-51-102 | - ni-51-102 |
| - osc-sn-51-721 | - osc-sn-51-721 |
| --- | --- |
| The PointSav documentation wiki at `documentation.pointsav.com` is one | The PointSav documentation wiki at `documentation.pointsav.com` is one |
| entrant in a field where twenty-five distinguishable providers ship some | entrant in a field where twenty-five distinguishable providers ship some |
| variation of "wiki-shaped knowledge surface" in 2026. Most of them are | variation of "wiki-shaped knowledge surface" in 2026. Most of them are |
| not encyclopedic-knowledge platforms; they are private-team productivity | not encyclopedic-knowledge platforms; they are private-team productivity |
| tools, developer-documentation site generators, or personal-knowledge | tools, developer-documentation site generators, or personal-knowledge |
| networked-thought systems. None of them has replaced Wikipedia for | networked-thought systems. None of them has replaced Wikipedia for |
| general-knowledge encyclopedic depth. This article documents the field, | general-knowledge encyclopedic depth. This article documents the field, |
| names the structural reasons no provider has closed the gap, and | names the structural reasons no provider has closed the gap, and |
| identifies the genuine advantages each provider has over Wikipedia — | identifies the genuine advantages each provider has over Wikipedia — |
| features worth preserving as the [[app-mediakit-knowledge|substrate]] iterates. | features worth preserving as the [[app-mediakit-knowledge|substrate]] iterates. |
| The audit is structural, not promotional. Each provider is described | The audit is structural, not promotional. Each provider is described |
| factually with its strongest published positioning and the structural | factually with its strongest published positioning and the structural |
| limitation that prevents it from filling the encyclopedic-knowledge | limitation that prevents it from filling the encyclopedic-knowledge |
| gap. The conclusion is not "PointSav wins"; it is "the gap is structural | gap. The conclusion is not "PointSav wins"; it is "the gap is structural |
| and is not closing under the current commercial-incentive structure of | and is not closing under the current commercial-incentive structure of |
| the wiki market." | the wiki market." |
| ## 1. The four groups | ## 1. The four groups |
| Twenty-five providers in four groups by their target use case. | Twenty-five providers in four groups by their target use case. |
| - **Group A — Collaborative knowledge bases**: Notion, Confluence, | - **Group A — Collaborative knowledge bases**: Notion, Confluence, |
| Coda, ClickUp Docs. Built for private organisational knowledge | Coda, ClickUp Docs. Built for private organisational knowledge |
| management. Sell seat licenses to enterprise IT. | management. Sell seat licenses to enterprise IT. |
| - **Group B — Public-facing wiki engines**: Wiki.js, BookStack, | - **Group B — Public-facing wiki engines**: Wiki.js, BookStack, |
| Outline, MediaWiki (what Wikipedia runs on), Fandom, Wikidot, | Outline, MediaWiki (what Wikipedia runs on), Fandom, Wikidot, |
| DokuWiki, TiddlyWiki. The closest in shape to a Wikipedia-class | DokuWiki, TiddlyWiki. The closest in shape to a Wikipedia-class |
| platform; widest variance in editorial governance. | platform; widest variance in editorial governance. |
| - **Group C — Developer documentation site generators**: Docusaurus, | - **Group C — Developer documentation site generators**: Docusaurus, |
| MkDocs Material, VitePress, Nextra, Fumadocs, Astro Starlight, | MkDocs Material, VitePress, Nextra, Fumadocs, Astro Starlight, |
| GitBook, Read the Docs. Generate docs sites for software projects; | GitBook, Read the Docs. Generate docs sites for software projects; |
| static-site-first; collaborative-editing-second or none. | static-site-first; collaborative-editing-second or none. |
| - **Group D — Personal/networked-thought tools**: Obsidian Publish, | - **Group D — Personal/networked-thought tools**: Obsidian Publish, |
| Roam Research, Logseq, Capacities, Quartz v4. Single-author | Roam Research, Logseq, Capacities, Quartz v4. Single-author |
| personal-knowledge-management primarily; some publish surfaces. | personal-knowledge-management primarily; some publish surfaces. |
| ## 2. Per-provider one-pagers | ## 2. Per-provider one-pagers |
| ### Notion (notion.com) | ### Notion (notion.com) |
| In 2026 Notion repositions itself as "The AI workspace that works for | In 2026 Notion repositions itself as "The AI workspace that works for |
| you" — an enterprise productivity suite with Custom Agents, autonomous | you" — an enterprise productivity suite with Custom Agents, autonomous |
| Q&A routing, and integration across Gmail, Slack, GitHub, and HubSpot. | Q&A routing, and integration across Gmail, Slack, GitHub, and HubSpot. |
| The article shell is a free-form block canvas: headings, callouts, | The article shell is a free-form block canvas: headings, callouts, |
| toggles, inline databases — no fixed structure and no enforced schema. | toggles, inline databases — no fixed structure and no enforced schema. |
| The encyclopedic-depth gap is categorical: Notion has no concept of a | The encyclopedic-depth gap is categorical: Notion has no concept of a |
| canonical article namespace, no red-link discovery, no Talk-page | canonical article namespace, no red-link discovery, no Talk-page |
| editorial debate, no Neutral Point of View policy, no notability gate, | editorial debate, no Neutral Point of View policy, no notability gate, |
| and no footnote-citation infrastructure where references are | and no footnote-citation infrastructure where references are |
| load-bearing rather than decorative. A Notion knowledge base degrades | load-bearing rather than decorative. A Notion knowledge base degrades |
| to informal, inconsistent prose at scale because there is no editorial | to informal, inconsistent prose at scale because there is no editorial |
| constitution enforcing it. | constitution enforcing it. |
| ### Confluence (atlassian.com/software/confluence) | ### Confluence (atlassian.com/software/confluence) |
| Confluence in 2026 is "An AI-powered workspace — One place for all | Confluence in 2026 is "An AI-powered workspace — One place for all |
| your ideas, docs, knowledge, and teammates," backed by Atlassian's | your ideas, docs, knowledge, and teammates," backed by Atlassian's |
| Gartner Magic Quadrant Leader designation. The article shell is a | Gartner Magic Quadrant Leader designation. The article shell is a |
| Confluence page in nested spaces with structured templates. Reviewer | Confluence page in nested spaces with structured templates. Reviewer |
| consensus: native search returns broad, poorly-ranked results; without | consensus: native search returns broad, poorly-ranked results; without |
| governance, pages sprawl and go stale; simultaneous-edit conflicts | governance, pages sprawl and go stale; simultaneous-edit conflicts |
| corrupt content; permission model is complex enough to drive new-user | corrupt content; permission model is complex enough to drive new-user |
| abandonment. At encyclopedic scale Confluence has no equivalent of | abandonment. At encyclopedic scale Confluence has no equivalent of |
| Wikipedia's category graph, "What links here," or Manual of Style — the | Wikipedia's category graph, "What links here," or Manual of Style — the |
| knowledge graph is a flat filing cabinet rather than a navigable | knowledge graph is a flat filing cabinet rather than a navigable |
| semantic network. | semantic network. |
| ### Coda (coda.io) | ### Coda (coda.io) |
| Coda is "Your all-in-one collaborative workspace" combining docs, | Coda is "Your all-in-one collaborative workspace" combining docs, |
| databases, and applications. The article shell blends document and | databases, and applications. The article shell blends document and |
| spreadsheet — packs of tables, buttons, formulas, and automations | spreadsheet — packs of tables, buttons, formulas, and automations |
| co-exist on a page. The encyclopedic-depth gap: Coda's structural power | co-exist on a page. The encyclopedic-depth gap: Coda's structural power |
| is relational (cross-doc formulas, synced tables) — useful for project | is relational (cross-doc formulas, synced tables) — useful for project |
| tracking, but creates no stable article-topology. There is no article | tracking, but creates no stable article-topology. There is no article |
| schema discipline, no citation surface, no Talk-layer, and no discovery | schema discipline, no citation surface, no Talk-layer, and no discovery |
| mechanism beyond search. | mechanism beyond search. |
| ### ClickUp Docs (clickup.com/features/docs) | ### ClickUp Docs (clickup.com/features/docs) |
| ClickUp positions Docs as "Beautiful, collaborative docs right where | ClickUp positions Docs as "Beautiful, collaborative docs right where |
| you work" — explicitly contextual knowledge management embedded in task | you work" — explicitly contextual knowledge management embedded in task |
| and project management. The article shell is a nested-pages rich text | and project management. The article shell is a nested-pages rich text |
| editor with task-embedding. The encyclopedic gap is structural by | editor with task-embedding. The encyclopedic gap is structural by |
| design: docs live inside projects and inherit project context; there is | design: docs live inside projects and inherit project context; there is |
| no concept of a standalone encyclopedic article. Real-time | no concept of a standalone encyclopedic article. Real-time |
| collaboration degrades above five concurrent editors. | collaboration degrades above five concurrent editors. |
| ### Wiki.js (js.wiki) | ### Wiki.js (js.wiki) |
| Wiki.js is "The most powerful and extensible open source Wiki software" | Wiki.js is "The most powerful and extensible open source Wiki software" |
| — self-hosted Node.js, Markdown / visual / HTML editors, with storage | — self-hosted Node.js, Markdown / visual / HTML editors, with storage |
| backends including Git, AWS, Azure, and 50+ authentication | backends including Git, AWS, Azure, and 50+ authentication |
| integrations. Current stable v2.5.312. Encyclopedic gap: Wiki.js has | integrations. Current stable v2.5.312. Encyclopedic gap: Wiki.js has |
| the right bones (version history, multi-language, wikilinks) but ships | the right bones (version history, multi-language, wikilinks) but ships |
| no editorial governance layer — no NPOV policy, no notability criteria, | no editorial governance layer — no NPOV policy, no notability criteria, |
| no Manual of Style enforcement, no Talk-page infrastructure in the | no Manual of Style enforcement, no Talk-page infrastructure in the |
| Wikipedia sense, and no red-link system. A powerful authoring engine | Wikipedia sense, and no red-link system. A powerful authoring engine |
| that requires an editorial culture to be built entirely from scratch on | that requires an editorial culture to be built entirely from scratch on |
| top. | top. |
| ### BookStack (bookstackapp.com) | ### BookStack (bookstackapp.com) |
| BookStack is "Simple & Free Wiki Software" — self-hosted PHP/Laravel, | BookStack is "Simple & Free Wiki Software" — self-hosted PHP/Laravel, |
| MIT licensed, content organised in Books → Chapters → Pages. The | MIT licensed, content organised in Books → Chapters → Pages. The |
| article shell is a WYSIWYG page in a rigid three-tier hierarchy. The | article shell is a WYSIWYG page in a rigid three-tier hierarchy. The |
| hierarchical model is the central limitation at encyclopedic scale: | hierarchical model is the central limitation at encyclopedic scale: |
| Wikipedia's article graph is a flat namespace with a category overlay, | Wikipedia's article graph is a flat namespace with a category overlay, |
| not a tree. Knowledge does not respect a single hierarchy. BookStack | not a tree. Knowledge does not respect a single hierarchy. BookStack |
| works well for documentation with clear ownership but collapses under | works well for documentation with clear ownership but collapses under |
| cross-cutting topics that belong to multiple conceptual parents | cross-cutting topics that belong to multiple conceptual parents |
| simultaneously. | simultaneously. |
| ### Outline (getoutline.com) | ### Outline (getoutline.com) |
| Outline is "Your team's knowledge base" — team-oriented with real-time | Outline is "Your team's knowledge base" — team-oriented with real-time |
| multiplayer editing, AI-powered search, Slack integration, cloud or | multiplayer editing, AI-powered search, Slack integration, cloud or |
| self-hosted. The article shell is a Notion-like block editor with | self-hosted. The article shell is a Notion-like block editor with |
| Markdown and slash commands. The encyclopedic gap mirrors Notion's: | Markdown and slash commands. The encyclopedic gap mirrors Notion's: |
| Outline is a private-team tool with no public-epistemics layer. No | Outline is a private-team tool with no public-epistemics layer. No |
| citation surface, no Talk-page equivalent, no category graph, no | citation surface, no Talk-page equivalent, no category graph, no |
| red-link system. | red-link system. |
| ### MediaWiki (mediawiki.org) | ### MediaWiki (mediawiki.org) |
| MediaWiki is the reference implementation — Wikipedia's engine. | MediaWiki is the reference implementation — Wikipedia's engine. |
| Structural primitives: flat article namespace; `[[wikilink]]` with | Structural primitives: flat article namespace; `[[wikilink]]` with |
| red-link signalling; category graph; Talk: namespace per article; | red-link signalling; category graph; Talk: namespace per article; |
| Special:Random; Special:WhatLinksHere; Special:RecentChanges; full | Special:Random; Special:WhatLinksHere; Special:RecentChanges; full |
| revision history; Wikidata integration; citation template system where | revision history; Wikidata integration; citation template system where |
| references are structurally load-bearing. The platform runs "tens of | references are structurally load-bearing. The platform runs "tens of |
| thousands of websites." The 2026 gap is the opposite of competitors: | thousands of websites." The 2026 gap is the opposite of competitors: |
| it has the structural depth, but a 2000s-era UX that new contributors | it has the structural depth, but a 2000s-era UX that new contributors |
| find hostile. The visual editor exists; the learning curve for template | find hostile. The visual editor exists; the learning curve for template |
| syntax, Lua modules, and citation formatting remains steep. | syntax, Lua modules, and citation formatting remains steep. |
| ### Fandom (fandom.com) | ### Fandom (fandom.com) |
| Fandom is a MediaWiki-based platform hosting fan wikis for games, | Fandom is a MediaWiki-based platform hosting fan wikis for games, |
| film, TV, and entertainment properties. New CEO Jay Sullivan (appointed | film, TV, and entertainment properties. New CEO Jay Sullivan (appointed |
| February 2026) brings a background from Mozilla, Twitter, and Facebook. | February 2026) brings a background from Mozilla, Twitter, and Facebook. |
| The article shell is MediaWiki with Fandom-specific extensions: | The article shell is MediaWiki with Fandom-specific extensions: |
| interactive maps, Table Progress Tracking, Game Companion tools. | interactive maps, Table Progress Tracking, Game Companion tools. |
| Encyclopedic gap: Fandom inherits MediaWiki's structural depth but | Encyclopedic gap: Fandom inherits MediaWiki's structural depth but |
| deploys it inside an ad-supported commercial context, driving the | deploys it inside an ad-supported commercial context, driving the |
| ongoing migration of communities to independent wikis. Audience and | ongoing migration of communities to independent wikis. Audience and |
| scope are fanbase-specific rather than general; the commercial ad | scope are fanbase-specific rather than general; the commercial ad |
| overlay creates trust and UX friction. | overlay creates trust and UX friction. |
| ### Wikidot (wikidot.com) | ### Wikidot (wikidot.com) |
| Wikidot is a cloud-hosted wiki-site builder with 106 million pages, | Wikidot is a cloud-hosted wiki-site builder with 106 million pages, |
| 10.3 million registered users, and 24,653 daily edits, on a freemium | 10.3 million registered users, and 24,653 daily edits, on a freemium |
| model. Encyclopedic gap: stagnation. No significant platform updates | model. Encyclopedic gap: stagnation. No significant platform updates |
| in years; non-standard syntax; community ecosystem fragmented. Notable | in years; non-standard syntax; community ecosystem fragmented. Notable |
| deployments maintain their own editorial cultures independent of | deployments maintain their own editorial cultures independent of |
| platform tooling. A maintenance-mode product rather than an advancing | platform tooling. A maintenance-mode product rather than an advancing |
| platform. | platform. |
| ### DokuWiki (dokuwiki.org) | ### DokuWiki (dokuwiki.org) |
| DokuWiki is a flat-file PHP-based wiki platform that stores content | DokuWiki is a flat-file PHP-based wiki platform that stores content |
| in plain text files rather than a database — easy to back up, | in plain text files rather than a database — easy to back up, |
| version-control externally, and migrate. Preferred for intranet | version-control externally, and migrate. Preferred for intranet |
| technical documentation among sysadmin communities. Encyclopedic gap: | technical documentation among sysadmin communities. Encyclopedic gap: |
| flat-file storage without structured metadata or semantic graph means | flat-file storage without structured metadata or semantic graph means |
| cross-article discovery is search-only. No category graph, no red | cross-article discovery is search-only. No category graph, no red |
| links, no Talk pages in the MediaWiki sense. | links, no Talk pages in the MediaWiki sense. |
| ### TiddlyWiki (tiddlywiki.com) | ### TiddlyWiki (tiddlywiki.com) |
| TiddlyWiki v5.4.0 is "a non-linear personal web notebook" — | TiddlyWiki v5.4.0 is "a non-linear personal web notebook" — |
| self-contained, single-HTML-file knowledge system. The fundamental | self-contained, single-HTML-file knowledge system. The fundamental |
| primitive is the tiddler (an atomic note); structure is entirely | primitive is the tiddler (an atomic note); structure is entirely |
| graph-based via linking. The UX is maximally personal and maximally | graph-based via linking. The UX is maximally personal and maximally |
| unfamiliar to new readers. No concept of a public-facing article | unfamiliar to new readers. No concept of a public-facing article |
| optimised for readers who are not the author. | optimised for readers who are not the author. |
| ### Docusaurus (docusaurus.io) | ### Docusaurus (docusaurus.io) |
| Docusaurus is Meta's React/MDX-based static site generator: "Build | Docusaurus is Meta's React/MDX-based static site generator: "Build |
| optimized websites quickly, focus on your content." Target: open-source | optimized websites quickly, focus on your content." Target: open-source |
| projects and technical documentation teams. The article shell is an MDX | projects and technical documentation teams. The article shell is an MDX |
| page rendered to static HTML with sidebar navigation, versioning, and | page rendered to static HTML with sidebar navigation, versioning, and |
| Algolia search. Encyclopedic gap: Docusaurus generates a docs site, | Algolia search. Encyclopedic gap: Docusaurus generates a docs site, |
| not a wiki. No inter-article linking discovery, no red links, no Talk | not a wiki. No inter-article linking discovery, no red links, no Talk |
| pages, no category graph, no collaborative in-browser editing. Every | pages, no category graph, no collaborative in-browser editing. Every |
| Docusaurus site looks structurally identical because it ships a single | Docusaurus site looks structurally identical because it ships a single |
| enforced layout. | enforced layout. |
| ### MkDocs Material (squidfunk.github.io/mkdocs-material) | ### MkDocs Material (squidfunk.github.io/mkdocs-material) |
| MkDocs Material is "Documentation that simply works" — Python-based | MkDocs Material is "Documentation that simply works" — Python-based |
| static site generator with 50,000+ users, instant browser-side search, | static site generator with 50,000+ users, instant browser-side search, |
| responsive layout, extensive theming. **Entered maintenance mode | responsive layout, extensive theming. **Entered maintenance mode |
| November 2025** — bug fixes and security patches continue, no new | November 2025** — bug fixes and security patches continue, no new |
| features. Same encyclopedic gap as Docusaurus: docs site, not wiki. | features. Same encyclopedic gap as Docusaurus: docs site, not wiki. |
| Navigation primitive is a fixed sidebar tree which cannot represent a | Navigation primitive is a fixed sidebar tree which cannot represent a |
| multi-parent category graph. | multi-parent category graph. |
| ### VitePress (vitepress.dev) | ### VitePress (vitepress.dev) |
| VitePress is "Markdown to beautiful docs in minutes" — Vue/Vite-powered | VitePress is "Markdown to beautiful docs in minutes" — Vue/Vite-powered |
| with hot-reload. The article shell is a Markdown file with Vue-powered | with hot-reload. The article shell is a Markdown file with Vue-powered |
| layout, sidebar, theme. Powers Vue's own documentation. Encyclopedic | layout, sidebar, theme. Powers Vue's own documentation. Encyclopedic |
| gap: same category as Docusaurus. "Beautiful docs in minutes" is | gap: same category as Docusaurus. "Beautiful docs in minutes" is |
| precisely the wrong metric for encyclopedic reference — it optimises | precisely the wrong metric for encyclopedic reference — it optimises |
| for designer-smooth surfaces rather than structural rigour. | for designer-smooth surfaces rather than structural rigour. |
| ### Nextra (nextra.site) | ### Nextra (nextra.site) |
| Nextra is "Simple, powerful and flexible site generation framework" | Nextra is "Simple, powerful and flexible site generation framework" |
| built on Next.js and MDX — the Next.js-ecosystem equivalent of | built on Next.js and MDX — the Next.js-ecosystem equivalent of |
| Docusaurus. Server Components and ISR support give it rendering | Docusaurus. Server Components and ISR support give it rendering |
| flexibility beyond typical static generators. Encyclopedic gap: | flexibility beyond typical static generators. Encyclopedic gap: |
| developer documentation tool with no wiki primitives. | developer documentation tool with no wiki primitives. |
| ### Fumadocs (fumadocs.dev) | ### Fumadocs (fumadocs.dev) |
| Fumadocs is "Build excellent documentations, your style" — React.js | Fumadocs is "Build excellent documentations, your style" — React.js |
| documentation framework for component libraries and developer tools, | documentation framework for component libraries and developer tools, |
| with minimal aesthetics, headless customisation, React Server | with minimal aesthetics, headless customisation, React Server |
| Components. Endorsed by Vercel engineers and shadcn/ui's creator. | Components. Endorsed by Vercel engineers and shadcn/ui's creator. |
| Encyclopedic gap: explicitly positioned at component-library | Encyclopedic gap: explicitly positioned at component-library |
| documentation; no public-wiki primitives, no editorial governance | documentation; no public-wiki primitives, no editorial governance |
| surface, no reader-navigation affordances beyond sidebar and search. | surface, no reader-navigation affordances beyond sidebar and search. |
| ### Astro Starlight (starlight.astro.build) | ### Astro Starlight (starlight.astro.build) |
| Starlight is "Make your docs shine" — Astro's documentation site | Starlight is "Make your docs shine" — Astro's documentation site |
| builder with built-in i18n, search, dark mode, sidebar, accessibility | builder with built-in i18n, search, dark mode, sidebar, accessibility |
| focus. Framework-agnostic via Astro's island architecture. Encyclopedic | focus. Framework-agnostic via Astro's island architecture. Encyclopedic |
| gap: same category as Docusaurus and VitePress. The accessibility | gap: same category as Docusaurus and VitePress. The accessibility |
| emphasis is a floor requirement, not a differentiator for encyclopedic | emphasis is a floor requirement, not a differentiator for encyclopedic |
| depth. | depth. |
| ### GitBook (gitbook.com) | ### GitBook (gitbook.com) |
| GitBook in 2026 is "Turn documentation into your product's knowledge | GitBook in 2026 is "Turn documentation into your product's knowledge |
| system" — a commercial SaaS documentation platform with AI Agent | system" — a commercial SaaS documentation platform with AI Agent |
| monitoring, Git Sync, embedded AI assistants, SOC2/ISO27001 compliance. | monitoring, Git Sync, embedded AI assistants, SOC2/ISO27001 compliance. |
| The 2026 pivot to "AI-ready docs" and "knowledge system" language | The 2026 pivot to "AI-ready docs" and "knowledge system" language |
| positions it against internal company knowledge tools rather than | positions it against internal company knowledge tools rather than |
| public encyclopedias. Encyclopedic gap: closed-source, commercially | public encyclopedias. Encyclopedic gap: closed-source, commercially |
| oriented, migrated away from open-source roots. No Talk-page model, no | oriented, migrated away from open-source roots. No Talk-page model, no |
| red-link mechanism, no NPOV policy surface, no category graph. | red-link mechanism, no NPOV policy surface, no category graph. |
| ### Read the Docs (about.readthedocs.com) | ### Read the Docs (about.readthedocs.com) |
| Read the Docs is "Docs as Code for everyone" — documentation hosting | Read the Docs is "Docs as Code for everyone" — documentation hosting |
| and build-automation supporting Sphinx, MkDocs, Docusaurus, Jupyter | and build-automation supporting Sphinx, MkDocs, Docusaurus, Jupyter |
| Book, others. Provides build pipeline, versioning, PR previews, hosted | Book, others. Provides build pipeline, versioning, PR previews, hosted |
| search. Encyclopedic gap: an infrastructure platform, not a | search. Encyclopedic gap: an infrastructure platform, not a |
| knowledge-graph engine. Solves the CI/CD problem for documentation but | knowledge-graph engine. Solves the CI/CD problem for documentation but |
| adds nothing to article-structure, editorial-governance, or | adds nothing to article-structure, editorial-governance, or |
| navigation-primitive dimensions. | navigation-primitive dimensions. |
| ### Obsidian Publish (obsidian.md/publish) | ### Obsidian Publish (obsidian.md/publish) |
| Obsidian Publish is "$8/month per site — The easiest way to publish | Obsidian Publish is "$8/month per site — The easiest way to publish |
| your wiki, knowledge base, documentation, or digital garden." Converts | your wiki, knowledge base, documentation, or digital garden." Converts |
| local Obsidian vaults into public-facing sites with hover previews, | local Obsidian vaults into public-facing sites with hover previews, |
| stacked pages, backlinks, graph view. The article shell is a Markdown | stacked pages, backlinks, graph view. The article shell is a Markdown |
| note with `[[wikilinks]]` and frontmatter — structurally the closest | note with `[[wikilinks]]` and frontmatter — structurally the closest |
| of any Group D tool to Wikipedia's article model. Encyclopedic gap: | of any Group D tool to Wikipedia's article model. Encyclopedic gap: |
| single-author publication tool, not a multi-author collaborative wiki. | single-author publication tool, not a multi-author collaborative wiki. |
| No collaborative in-browser editing, no Talk-page discussion layer, no | No collaborative in-browser editing, no Talk-page discussion layer, no |
| NPOV enforcement, no notability gate, no community moderation | NPOV enforcement, no notability gate, no community moderation |
| infrastructure. | infrastructure. |
| ### Roam Research (roamresearch.com) | ### Roam Research (roamresearch.com) |
| Roam Research is "A note taking tool for networked thought" — the | Roam Research is "A note taking tool for networked thought" — the |
| originator of the modern bidirectional-link paradigm at $15/month, | originator of the modern bidirectional-link paradigm at $15/month, |
| significantly more expensive than alternatives while offering less | significantly more expensive than alternatives while offering less |
| customisation. By 2026 Logseq has absorbed most of Roam's market. The | customisation. By 2026 Logseq has absorbed most of Roam's market. The |
| article shell is a page of nested bullets with `[[wikilinks]]` and | article shell is a page of nested bullets with `[[wikilinks]]` and |
| block references, optimised for the author's non-linear associative | block references, optimised for the author's non-linear associative |
| workflow. Encyclopedic gap: a personal thought-capture tool. The | workflow. Encyclopedic gap: a personal thought-capture tool. The |
| structural model is explicitly anti-encyclopedic — no article-length | structural model is explicitly anti-encyclopedic — no article-length |
| atomic unit, no concept of a reader who is not the author. | atomic unit, no concept of a reader who is not the author. |
| ### Logseq (logseq.com) | ### Logseq (logseq.com) |
| Logseq is "A privacy-first, open-source knowledge base" — local-first, | Logseq is "A privacy-first, open-source knowledge base" — local-first, |
| open-source, block-based, with bidirectional links, graph view, | open-source, block-based, with bidirectional links, graph view, |
| Org-mode/Markdown support. In 2026 "the better choice" over Roam due | Org-mode/Markdown support. In 2026 "the better choice" over Roam due |
| to free tier and open codebase. Encyclopedic gap: same as Roam. The | to free tier and open codebase. Encyclopedic gap: same as Roam. The |
| block-outline model is a personal-knowledge primitive, not an | block-outline model is a personal-knowledge primitive, not an |
| encyclopedic-article primitive. Multi-author collaborative publishing | encyclopedic-article primitive. Multi-author collaborative publishing |
| is not a supported workflow. | is not a supported workflow. |
| ### Capacities (capacities.io) | ### Capacities (capacities.io) |
| Capacities is "A studio for your mind" — a personal knowledge | Capacities is "A studio for your mind" — a personal knowledge |
| management system built on typed objects rather than files in folders. | management system built on typed objects rather than files in folders. |
| Object-based relationship modelling surfaces connections automatically | Object-based relationship modelling surfaces connections automatically |
| via "Related Content." Funded by users rather than venture capital; | via "Related Content." Funded by users rather than venture capital; |
| EU-hosted with full data export. The article shell is a typed object | EU-hosted with full data export. The article shell is a typed object |
| with properties, linked to other typed objects — the most semantically | with properties, linked to other typed objects — the most semantically |
| rich data model in Group D. Encyclopedic gap: explicitly | rich data model in Group D. Encyclopedic gap: explicitly |
| individual-focused; no collaborative editing, no public-epistemics | individual-focused; no collaborative editing, no public-epistemics |
| model, no article-level citation infrastructure, no community | model, no article-level citation infrastructure, no community |
| governance layer. | governance layer. |
| ### Quartz v4 (quartz.jzhao.xyz) | ### Quartz v4 (quartz.jzhao.xyz) |
| Quartz v4 is "a fast, batteries-included static-site generator that | Quartz v4 is "a fast, batteries-included static-site generator that |
| transforms Markdown content into fully functional websites" — targeting | transforms Markdown content into fully functional websites" — targeting |
| students, developers, and teachers publishing personal notes and | students, developers, and teachers publishing personal notes and |
| digital gardens. Native Obsidian compatibility, `[[wikilinks]]`, graph | digital gardens. Native Obsidian compatibility, `[[wikilinks]]`, graph |
| visualisation, LaTeX, popover previews, full-text search. Encyclopedic | visualisation, LaTeX, popover previews, full-text search. Encyclopedic |
| gap: a single-author static site generator. Ships graph view and | gap: a single-author static site generator. Ships graph view and |
| backlinks natively (more than most competitors) but no collaborative | backlinks natively (more than most competitors) but no collaborative |
| editing, no Talk-page layer, no notability mechanism, no NPOV | editing, no Talk-page layer, no notability mechanism, no NPOV |
| infrastructure, no red-link system. | infrastructure, no red-link system. |
| ## 3. Cross-cutting failure modes | ## 3. Cross-cutting failure modes |
| The eight structural reasons no provider in this audit has replaced | The eight structural reasons no provider in this audit has replaced |
| Wikipedia for general encyclopedic knowledge: | Wikipedia for general encyclopedic knowledge: |
| **(i) Audience mismatch.** Notion, Confluence, Coda, ClickUp, Outline, | **(i) Audience mismatch.** Notion, Confluence, Coda, ClickUp, Outline, |
| and BookStack were built for private organisational knowledge | and BookStack were built for private organisational knowledge |
| management. Access-control model, pricing model, and UX assume a known | management. Access-control model, pricing model, and UX assume a known |
| trusted team. Public-encyclopedic publishing requires the opposite — | trusted team. Public-encyclopedic publishing requires the opposite — |
| anonymous editors, verifiable sourcing, reader-first navigation. These | anonymous editors, verifiable sourcing, reader-first navigation. These |
| products cannot pivot without dismantling their commercial model. | products cannot pivot without dismantling their commercial model. |
| **(ii) No editorial constitution.** Wikipedia's NPOV, Notability, | **(ii) No editorial constitution.** Wikipedia's NPOV, Notability, |
| Reliable Sources, No Original Research, and Manual of Style constitute | Reliable Sources, No Original Research, and Manual of Style constitute |
| a multi-decade-refined editorial constitution. No provider in this | a multi-decade-refined editorial constitution. No provider in this |
| audit ships an equivalent. The absence is a missing governance | audit ships an equivalent. The absence is a missing governance |
| organisation, not a missing feature. | organisation, not a missing feature. |
| **(iii) Information density floor.** Docusaurus, MkDocs, VitePress, | **(iii) Information density floor.** Docusaurus, MkDocs, VitePress, |
| GitBook, and Obsidian Publish optimise for prose elegance, developer | GitBook, and Obsidian Publish optimise for prose elegance, developer |
| aesthetics, and clean typography. Wikipedia articles are deliberately | aesthetics, and clean typography. Wikipedia articles are deliberately |
| dense — infoboxes, hatnotes, references with 100+ footnotes, navboxes, | dense — infoboxes, hatnotes, references with 100+ footnotes, navboxes, |
| stub tags, disambiguation pages. No documentation site generator ships | stub tags, disambiguation pages. No documentation site generator ships |
| this density model because target users actively want the opposite. | this density model because target users actively want the opposite. |
| **(iv) Navigation primitive missing.** Wikipedia's navigation stack — | **(iv) Navigation primitive missing.** Wikipedia's navigation stack — |
| `[[wikilink]]` with red-link signalling, Special:Random, | `[[wikilink]]` with red-link signalling, Special:Random, |
| Special:WhatLinksHere, category graph, disambiguation pages, navbox | Special:WhatLinksHere, category graph, disambiguation pages, navbox |
| templates, sister-project interlinking — exists complete in MediaWiki | templates, sister-project interlinking — exists complete in MediaWiki |
| and at most one or two members elsewhere. Most competitors do not even | and at most one or two members elsewhere. Most competitors do not even |
| ship the red-link mechanism, which is structural to Wikipedia's growth | ship the red-link mechanism, which is structural to Wikipedia's growth |
| model. | model. |
| **(v) Citations are decorative, not load-bearing.** Wikipedia's | **(v) Citations are decorative, not load-bearing.** Wikipedia's |
| footnote system makes claims verifiable at the statement level. Across | footnote system makes claims verifiable at the statement level. Across |
| Group A, C, and D providers, citations are absent entirely, implemented | Group A, C, and D providers, citations are absent entirely, implemented |
| as inline hyperlinks with no formal structure, or supported as | as inline hyperlinks with no formal structure, or supported as |
| page-level frontmatter rather than claim-level. | page-level frontmatter rather than claim-level. |
| **(vi) No Talk-page substrate.** Each Wikipedia article has a Talk: | **(vi) No Talk-page substrate.** Each Wikipedia article has a Talk: |
| page that is the public record of editorial dispute. Confluence and | page that is the public record of editorial dispute. Confluence and |
| Notion have inline comments — not archived public editorial debate. | Notion have inline comments — not archived public editorial debate. |
| **(vii) Structural brittleness.** Notion's block format, Coda's pack | **(vii) Structural brittleness.** Notion's block format, Coda's pack |
| structure, and ClickUp's embedded docs are proprietary serialisation | structure, and ClickUp's embedded docs are proprietary serialisation |
| formats. Content created in 2020 is at vendor-lock-in risk by 2026. | formats. Content created in 2020 is at vendor-lock-in risk by 2026. |
| Wikipedia's wikitext is plain text that can be exported, archived, and | Wikipedia's wikitext is plain text that can be exported, archived, and |
| mirrored. | mirrored. |
| **(viii) Template homogenisation.** Every Docusaurus, Starlight, | **(viii) Template homogenisation.** Every Docusaurus, Starlight, |
| VitePress, and MkDocs site looks structurally identical. This is the | VitePress, and MkDocs site looks structurally identical. This is the |
| documentation aesthetic every engineering team knows. It is also what | documentation aesthetic every engineering team knows. It is also what |
| a Wikipedia reader does *not* associate with encyclopedic authority. | a Wikipedia reader does *not* associate with encyclopedic authority. |
| ## 4. What each provider does better than Wikipedia | ## 4. What each provider does better than Wikipedia |
| The honesty floor of the audit. Each provider has a genuine advantage | The honesty floor of the audit. Each provider has a genuine advantage |
| over Wikipedia in some dimension. The leapfrog candidates worth | over Wikipedia in some dimension. The leapfrog candidates worth |
| considering: | considering: |
| | Provider | Genuine advantage | | | Provider | Genuine advantage | |
| |---|---| | |---|---| |
| | Notion | Inline @-mentions linking people, tasks, dates inside prose; database-as-page model embedding live structured data | | | Notion | Inline @-mentions linking people, tasks, dates inside prose; database-as-page model embedding live structured data | |
| | Confluence | Macro ecosystem for dynamic content embedding (Jira ticket status, roadmaps); enterprise SSO and granular permissions | | | Confluence | Macro ecosystem for dynamic content embedding (Jira ticket status, roadmaps); enterprise SSO and granular permissions | |
| | Coda | Cross-document formula language: relational knowledge made visible without a separate database | | | Coda | Cross-document formula language: relational knowledge made visible without a separate database | |
| | ClickUp Docs | Contextual attachment: docs live adjacent to the tasks they describe | | | ClickUp Docs | Contextual attachment: docs live adjacent to the tasks they describe | |
| | Wiki.js | Git-backed storage: every article version is a git commit, fully portable and diffable with standard tooling | | | Wiki.js | Git-backed storage: every article version is a git commit, fully portable and diffable with standard tooling | |
| | BookStack | Operational simplicity: runs on a $2.50 VPS with a single PHP install — lowest cost-to-first-article of any self-hosted wiki engine | | | BookStack | Operational simplicity: runs on a $2.50 VPS with a single PHP install — lowest cost-to-first-article of any self-hosted wiki engine | |
| | Outline | Real-time multiplayer editing with operational-transform conflict resolution; smoother concurrent editing than MediaWiki's section-locking | | | Outline | Real-time multiplayer editing with operational-transform conflict resolution; smoother concurrent editing than MediaWiki's section-locking | |
| | MediaWiki | Everything that is the benchmark — full navigation primitive stack, NPOV enforcement, category graph, Talk pages, Wikidata integration | | | MediaWiki | Everything that is the benchmark — full navigation primitive stack, NPOV enforcement, category graph, Talk pages, Wikidata integration | |
| | Fandom | Interactive maps and progress-tracking tables embedded natively in wiki articles; best media-gallery integration | | | Fandom | Interactive maps and progress-tracking tables embedded natively in wiki articles; best media-gallery integration | |
| | Wikidot | Community-site builder supporting custom CSS per wiki plus sub-wikis under a shared domain | | | Wikidot | Community-site builder supporting custom CSS per wiki plus sub-wikis under a shared domain | |
| | DokuWiki | Zero-database flat-file storage — most portable, least infrastructure-dependent knowledge store | | | DokuWiki | Zero-database flat-file storage — most portable, least infrastructure-dependent knowledge store | |
| | TiddlyWiki | Single-file portability — entire knowledge base is one HTML file; extreme durability | | | TiddlyWiki | Single-file portability — entire knowledge base is one HTML file; extreme durability | |
| | Docusaurus | MDX: React components embedded in Markdown enabling interactive documentation (live code playgrounds, API sandboxes) | | | Docusaurus | MDX: React components embedded in Markdown enabling interactive documentation (live code playgrounds, API sandboxes) | |
| | MkDocs Material | Instant client-side search with offline support and zero external dependencies; fastest search-to-result | | | MkDocs Material | Instant client-side search with offline support and zero external dependencies; fastest search-to-result | |
| | VitePress | Hot-module reload during authoring: sub-second preview updates as you write | | | VitePress | Hot-module reload during authoring: sub-second preview updates as you write | |
| | Nextra | Server Components: docs pages can fetch live data at render time | | | Nextra | Server Components: docs pages can fetch live data at render time | |
| | Fumadocs | Headless architecture: complete design-system override without forking | | | Fumadocs | Headless architecture: complete design-system override without forking | |
| | Astro Starlight | Island architecture: zero JavaScript shipped by default; best Lighthouse scores | | | Astro Starlight | Island architecture: zero JavaScript shipped by default; best Lighthouse scores | |
| | GitBook | Git bidirectional sync: write in IDE or visual editor; both stay synchronised | | | GitBook | Git bidirectional sync: write in IDE or visual editor; both stay synchronised | |
| | Read the Docs | PR preview builds with visual diffs | | | Read the Docs | PR preview builds with visual diffs | |
| | Obsidian Publish | Graph view with hover-preview; most visually legible representation of a personal knowledge graph | | | Obsidian Publish | Graph view with hover-preview; most visually legible representation of a personal knowledge graph | |
| | Roam Research | Block-level transclusion: any block embeddable by reference into any other document | | | Roam Research | Block-level transclusion: any block embeddable by reference into any other document | |
| | Logseq | Free plus open-source plus local-first with bidirectional links — the combination Roam never offered | | | Logseq | Free plus open-source plus local-first with bidirectional links — the combination Roam never offered | |
| | Capacities | Typed objects with automatic relationship discovery — closest to a semantic knowledge graph | | | Capacities | Typed objects with automatic relationship discovery — closest to a semantic knowledge graph | |
| | Quartz v4 | Native Obsidian vault publishing with wikilinks, popover previews, graph view in a static site | | | Quartz v4 | Native Obsidian vault publishing with wikilinks, popover previews, graph view in a static site | |
| Three of these advantages are particularly worth integrating into a | Three of these advantages are particularly worth integrating into a |
| Wikipedia-class chrome without breaking the muscle-memory contract: | Wikipedia-class chrome without breaking the muscle-memory contract: |
| MkDocs Material's instant client-side search; Capacities' typed-object | MkDocs Material's instant client-side search; Capacities' typed-object |
| relationship surface rendered as navigable article metadata; and | relationship surface rendered as navigable article metadata; and |
| Obsidian Publish's hover-preview popover on `[[wikilinks]]`. | Obsidian Publish's hover-preview popover on `[[wikilinks]]`. |
| ## 5. Why the gold-standard market gap exists in 2026 | ## 5. Why the gold-standard market gap exists in 2026 |
| The gap is structural and has five reinforcing causes. | The gap is structural and has five reinforcing causes. |
| **Commercial incentive misalignment.** Notion, Confluence, GitBook, | **Commercial incentive misalignment.** Notion, Confluence, GitBook, |
| Coda, and ClickUp make money by selling seat licenses to organisations | Coda, and ClickUp make money by selling seat licenses to organisations |
| managing internal knowledge. Their roadmaps are driven by enterprise IT | managing internal knowledge. Their roadmaps are driven by enterprise IT |
| buyers — investing in NPOV enforcement, Talk-page infrastructure, or | buyers — investing in NPOV enforcement, Talk-page infrastructure, or |
| red-link discovery does not convert to enterprise seat revenue. | red-link discovery does not convert to enterprise seat revenue. |
| **The editorial-labour problem cannot be automated.** Wikipedia's | **The editorial-labour problem cannot be automated.** Wikipedia's |
| structural authority is twenty years of accumulated editorial labour. | structural authority is twenty years of accumulated editorial labour. |
| Generated content cannot replicate the transparent editorial process, | Generated content cannot replicate the transparent editorial process, |
| source verification standards, or community governance that make | source verification standards, or community governance that make |
| Wikipedia trusted. Replicating the credibility surface requires | Wikipedia trusted. Replicating the credibility surface requires |
| replicating the governance — and no commercial entity has bootstrapped | replicating the governance — and no commercial entity has bootstrapped |
| that from a product launch. | that from a product launch. |
| **Open-source coordination cost.** MediaWiki's codebase is 25 years | **Open-source coordination cost.** MediaWiki's codebase is 25 years |
| old, carries enormous legacy compatibility surface, and requires | old, carries enormous legacy compatibility surface, and requires |
| sustained foundation resources to maintain. No independent open-source | sustained foundation resources to maintain. No independent open-source |
| project has shipped a "MediaWiki v2 with modern UX" because the | project has shipped a "MediaWiki v2 with modern UX" because the |
| coordination cost is prohibitive. | coordination cost is prohibitive. |
| **Scope creep on one side, narrow scope on the other.** Group A | **Scope creep on one side, narrow scope on the other.** Group A |
| providers expanded into "everything platforms"; their knowledge-base | providers expanded into "everything platforms"; their knowledge-base |
| features compete with AI agents, project management, and enterprise | features compete with AI agents, project management, and enterprise |
| integrations. Group C providers are deliberately minimal static-site | integrations. Group C providers are deliberately minimal static-site |
| generators — no collaborative editing model by design. | generators — no collaborative editing model by design. |
| **The "Wikipedia muscle memory" gap.** No competitor has invested in | **The "Wikipedia muscle memory" gap.** No competitor has invested in |
| replicating the specific reader-navigation UX that billions of | replicating the specific reader-navigation UX that billions of |
| Wikipedia users know by reflex. This is an information-architecture | Wikipedia users know by reflex. This is an information-architecture |
| commitment, not a CSS problem. Documentation sites ship sidebars | commitment, not a CSS problem. Documentation sites ship sidebars |
| because their readers navigate a product's API. Encyclopedia readers | because their readers navigate a product's API. Encyclopedia readers |
| arrive from search, orient via the infobox, follow blue links | arrive from search, orient via the infobox, follow blue links |
| sideways, and exit via categories. | sideways, and exit via categories. |
| ## 6. What this means for documentation.pointsav.com | ## 6. What this means for documentation.pointsav.com |
| Closing the gap requires simultaneously building governance software, a | Closing the gap requires simultaneously building governance software, a |
| navigation primitive set, and an editorial culture. PointSav's | navigation primitive set, and an editorial culture. PointSav's |
| substrate-sovereignty design, three-tier compute routing under the | substrate-sovereignty design, three-tier compute routing under the |
| optional [[four-tier-slm-substrate|Intelligence Layer]], [[apprenticeship-substrate|apprenticeship-corpus capture]], and the | optional [[four-tier-slm-substrate|Intelligence Layer]], [[apprenticeship-substrate|apprenticeship-corpus capture]], and the |
| editorial pipeline are the three preconditions no commercial competitor | editorial pipeline are the three preconditions no commercial competitor |
| can simultaneously match. | can simultaneously match. |
| The wiki engine [[app-mediakit-knowledge]] is intended to become the | The wiki engine [[app-mediakit-knowledge]] is intended to become the |
| customer-installable demonstration of that substrate. The structural | customer-installable demonstration of that substrate. The structural |
| argument for the leapfrog claim is what this article documents: the gap | argument for the leapfrog claim is what this article documents: the gap |
| exists because of the five structural causes above; closing it requires | exists because of the five structural causes above; closing it requires |
| the three preconditions above; the substrate has those preconditions as | the three preconditions above; the substrate has those preconditions as |
| design intent. The award framings in knowledge-wiki-home-page-design | design intent. The award framings in knowledge-wiki-home-page-design |
| §5 and article-shell-leapfrog §5 are the planned downstream | §5 and article-shell-leapfrog §5 are the planned downstream |
| consequences. | consequences. |
| ## 7. Open editorial item | ## 7. Open editorial item |
| This audit was conducted in April 2026 with primary research across | This audit was conducted in April 2026 with primary research across |
| all 25 providers. Provider positioning shifts; an annual re-audit cadence | all 25 providers. Provider positioning shifts; an annual re-audit cadence |
| is planned to keep this article current. The next re-audit is intended | is planned to keep this article current. The next re-audit is intended |
| for approximately April 2027. If a provider in this list ships a | for approximately April 2027. If a provider in this list ships a |
| structural change between audits — for example, MediaWiki ships a | structural change between audits — for example, MediaWiki ships a |
| modern UX layer, or Wiki.js adds NPOV-style editorial discipline — this | modern UX layer, or Wiki.js adds NPOV-style editorial discipline — this |
| article is amended in transit. Forward-looking framings carry stated | article is amended in transit. Forward-looking framings carry stated |
| assumptions and cautionary language per NI 51-102 and OSC Staff Notice | assumptions and cautionary language per NI 51-102 and OSC Staff Notice |
| 51-721. | 51-721. |
| ## See also | ## See also |
| - [[app-mediakit-knowledge]] — the wiki engine that implements the leapfrog claim documented here | - [[app-mediakit-knowledge]] — the wiki engine that implements the leapfrog claim documented here |
| - [[editorial-philosophy]] — the editorial model that the platform wiki implements | - [[editorial-philosophy]] — the editorial model that the platform wiki implements |
| - [[compounding-substrate]] — the compounding improvement loop that advances content quality over time | - [[compounding-substrate]] — the compounding improvement loop that advances content quality over time |