Codebase-as-Wiki Knowledge Base

Teams increasingly store company knowledge (meeting notes, user feedback, strategy docs) directly in their codebase instead of using Notion or Linear, leveraging Git for collaboration and version history. A tool that makes it seamless to treat your repo as a knowledge base with better organization and search could formalize this workflow. Target users: technical founders, engineering-heavy teams.

The rise of "docs-as-code" and tools like GitHub Copilot have pushed more teams toward treating Markdown files in Git as first-class documentation, and there's genuine friction in navigating that content at scale — especially search and cross-linking. Obsidian handles local Markdown knowledge bases well, and GitHub itself renders docs natively, so the substitutes aren't nothing. Revenue band is genuinely unclear because this sits in a graveyard of developer tools that teams adopt enthusiastically and refuse to pay for, and "unknown" is the honest answer. The biggest risk is that the workflow this formalizes is already good enough for most teams at the scale that would adopt it — once a repo gets large enough to need serious knowledge management, orgs typically have budget for Notion or Confluence and the political will to use them.