Straight from your repository
Markdown and MDX in your docs folder, reviewed in pull requests like the rest of your codebase. No new editor to learn, no migration, no proprietary format.
Product · Docs
The markdown in your repo, built into a fast, searchable, agent-readable docs site. Push to main and the site, search, and llms.txt update together.
Why git-first
Every team knows the pattern: the product ships on Tuesday, the docs catch up in three weeks, if anyone remembers. Meanwhile developers follow outdated instructions, file support tickets, and quietly lose trust.
The root cause isn't laziness. It's that docs live in a separate tool from the code they describe. Stipple builds docs from your repository, so the commit that changes the product is the commit that changes the docs.
What you get
Git-synced, searchable, and agent-ready. The way documentation should have always worked.
Markdown and MDX in your docs folder, reviewed in pull requests like the rest of your codebase. No new editor to learn, no migration, no proprietary format.
Docs live in the same history as the code they describe. Revert a commit and the docs revert with it. No more "the docs say one thing, the product does another."
docs.yours.com, or a true subdirectory mount at yours.com/docs behind your own proxy — verified, with copy-paste configs for nginx, Cloudflare, and Vercel.
Every build emits llms.txt and llms-full.txt alongside the site, so Claude, Cursor, and ChatGPT answer from your docs — cited, not guessed.
What product and developer-experience teams ask before switching.
Early access is open for engineering teams. Join the list and we'll reach out as spots open.
Or see pricing first.