04 · Competitive landscape
The assignment
Section titled “The assignment”Cyberbaser’s Problem page claims no existing tool covers all three corners of the tradeoff triangle (Obsidian fidelity + low-friction contribution + no vendor lock-in). Your job: prove or disprove this claim. If something already does what cyberbaser wants to do, cyberbaser shouldn’t exist. Be honest — not cheerleading.
What to investigate
Section titled “What to investigate”-
Obsidian-native publishers. Obsidian Publish ($10/mo), Quartz v4 (free OSS), Digital Garden plugin (free OSS). For each: fidelity score (wikilinks, callouts, embeds, graph), contribution model (if any), vendor lock-in assessment, pricing.
-
Git-backed CMS platforms. EmDash (Cloudflare, Astro-native), GitBook (free + paid), wiki.js (free OSS), BookStack (free OSS), Outline (free OSS + hosted). Do any of these support Obsidian-flavored markdown AND non-technical contribution AND git as SSOT?
-
Notion/Confluence alternatives. Notion public pages, Confluence, Slite, Nuclino. These are the “easy contribution” incumbents. What would it take for cyberbaser to match their contribution UX while keeping git SSOT + Obsidian fidelity?
-
The Quartz + Decap combo. This is the most dangerous competitor because it’s free: Quartz for Obsidian-aware publishing + Decap Open Authoring for contribution + GitHub Pages for hosting. Has anyone built this? Does it work? What’s missing that cyberbaser would add?
-
AI-native CMS newcomers (2025-2026). EmDash, v0.dev, Bolt.new. Are AI-generated sites making the “build a wiki” problem obsolete? If an agent can scaffold a full wiki from a vault in 5 minutes, does cyberbaser’s translation layer still matter?
-
The honest moat assessment. After surveying all the above: what does cyberbaser do that NONE of them do? Is it a genuine gap, or is it “theoretically better but practically replaceable”?
Context to read first
Section titled “Context to read first”- The Problem — the tradeoff triangle
- Prior Art — current analysis (6 entries)
- Ecosystem — the four layers
- Operational landscape — where value lives
What success looks like
Section titled “What success looks like”- Comparison table: product, Obsidian fidelity (1-5), contribution UX (1-5), git SSOT (Y/N), self-hosted (Y/N), pricing, license
- Gap analysis: which cells in the table are empty (features no one covers)?
- The “Quartz + Decap” test: has it been done? Does it work? What breaks?
- Honest moat statement: “Cyberbaser’s defensible advantage is [X] because [Y]” OR “Cyberbaser’s advantage is marginal because [Z already covers it]”
- Validity: this landscape holds until [date — suggest 6 months given how fast the ecosystem moves]