Documentation built for
developers and agents.

Stipple turns the markdown in your repo into a fast, searchable docs site, with llms.txt, search, and sitemaps regenerated on every push. Your docs stay in sync with your product, and readable by every agent.

See how it works

Your product moved. Your docs didn’t.

Every engineering team writes docs constantly. They’re scattered across a wiki, a README, and a hand-rolled site nobody rebuilds, outdated the moment you ship again.

stale · 4 moNotion wiki

The docs

stale · 2 wkREADME.md

The quickstart

driftingHand-rolled site

The reference

three places, three versions of the truth, all aging

One commit. Every surface updates.

Your repo is the source of truth. Push to main and Stipple rebuilds the site, the search index, the sitemap, and the llms.txt agents read, all from the same commit. Docs can’t drift from the product they describe.

git push
Markdown & MDX
docs.json nav
Branding assets
your repo, built
Docs siteCURRENT
Full-text searchCURRENT
llms.txtCURRENT
Sitemap & SEOCURRENT

push once; site, search, and agent surfaces rebuild together

From git push to published docs.

CONNECT

Connect the repo your docs already live in

Point Stipple at a docs/ folder of markdown. No migration, no new format. A docs.json for name and navigation, and you're live.

WRITE

Write in Markdown and MDX

Code blocks, callouts, and components, reviewed in pull requests like the rest of your codebase, versioned with the product.

AGENTS

Readable by every agent

Every build emits llms.txt and llms-full.txt alongside the site, so Claude, Cursor, and your customers' agents cite your docs, not a guess.

SERVE

Serve it at docs.yours.com, or yours.com/docs

Custom domains and true subdirectory mounts behind your own proxy. Edge-served, SSL handled, search included.

Your developers don’t browse. They ask.

Half your users ask Google. The other half ask Claude, Cursor, and ChatGPT. Stipple ships schema-rich pages for one and llms.txt for the other, so both answer from your docs, not from a guess.

GGoogle · search result
“yourproduct api authentication”
yourteam.com › docs › authentication · Send a bearer token from Settings → API keys. Tokens scope to a single project…
rich result · indexed 4 min after publish
AI assistant · answer
“how do I authenticate against the yourproduct API?”
Send a bearer token in the Authorization header, created under Settings → API keys. According to yourteam.com/docs
cited: your docs, via llms.txt

one build, both discovery systems answered

Retire the duct tape.

A serious docs site today means five tools and a prayer. Stipple is one system: building, hosting, search, and agent surfaces included.

Static-site generator + 14 pluginsdocs site
Algolia contract + index scriptssearch
Hand-written llms.txt (last touched: never)agents
Nginx config for /docs on the main domainserving
“Whose job is rebuilding the docs?”ops
Stipple

One system from repo to reader. Migration included: point us at your markdown and we move it for you.

Docs live in a day, not a quarter.

We migrate your existing docs from ReadMe, GitBook, Docusaurus, or plain Markdown, wire up your repo and domain, and hand you a working site, not an empty template.

Point us at your repoWe structure & migrateLive on your domainPublishing · Live

“Documentation isn’t a website problem. It’s a sync problem: docs are written next to the code, but published somewhere the code can’t reach. Stipple closes that gap. Git-first, agent-native, built on plain markdown you can take anywhere.”

Read what we believe

Everything included. Nothing bolted on.

Git sync · docs build from your repo on every push
Markdown & MDX · code blocks, callouts, components
docs.json config · name, navigation, branding, versioned in git
Full-text search · indexed at build time, no Algolia contract
llms.txt + llms-full.txt · generated on every build for agents
Custom domains · docs.yours.com with SSL handled
Subdirectory mounts · yours.com/docs behind your own proxy
Edge hosting · perfect Core Web Vitals, zero maintenance
Sitemaps & SEO · schema-rich pages, generated per build
Analytics · traffic, sources, top pages built in
Versioned by git · every change reviewed in a pull request
Themes · your brand via docs.json, no code required
Team access · engineering owns docs like code
Atomic deploys · site, search, and llms.txt from one commit
No migration cliff · plain markdown in, plain markdown out
Concierge migration · we move your docs for you

Questions, answered.

Connect a GitHub repo and point Stipple at your docs folder. Every push to your default branch rebuilds the site, the search index, the sitemap, and llms.txt, all from the same commit.

Push it. Your docs are already live.

Docs that stay in sync with your product and readable by every agent. Early access is open for engineering teams.

Or see pricing first.