DevToolsDocumentationSaaSAI

Runbook

An internal doc tool developers will actually keep updated

Problem
Developers have long hated Confluence for its heavy UI, templates, weak search, and disconnection from code, so nobody writes in it. The recurring community question of whether a wiki developers actually like exists has no good answer, and team knowledge ends up split between stale Confluence pages and scattered READMEs.
Solution
Start read-only: auto-extract changes from the repo, PR descriptions, and commit messages to generate a structured weekly changelog and per-service overview pages, with Git as the source of truth. Developers only add a sentence to existing Markdown, and the tool handles aggregation, indexing, and search.
Users
Engineering teams of 10–80, especially small companies on GitHub that are also forced to maintain Confluence
MVP
Read-only GitHub/GitLab connection; auto-generated per-service overview; commit and PR digest timeline; full-text search; optional Confluence/Notion export so teams don't have to migrate
Revenue
Per-seat subscription at $4–6/developer/month; free for public repos, paid for private ones
Why now
LLMs make automatic doc summarization from code cheap for the first time, and Confluence fatigue persists, while a read-only aggregator avoids the migration pitch that kills most doc startups

Source discussions · 1

  1. Hacker NewsAsk HN: Why do developers hate Confluence?1↑ 6
← Back to list