you ship the code and we write the docs for you.
Keep the open runtime. Add the layer for editing, search, analytics, AI, knowledge graphs and docs operations.
Join the waitlist
Get first access.
Tell us what should ship first and we’ll use that to shape the first release.
What cloud adds
Cloud should feel built into the docs runtime.
These are the first cloud surfaces teams should actually use: edit, retrieve, review, and ship.
You ship the code. Cloud drafts the docs, keeps frontmatter clean, and opens pull requests.
docs/getting-started.mdx
Frontmatter, markdown, and nav updates in one editor.
Run search, retrieval, and cited answers from the same docs graph.
Retry policy
Guide · section hit
Webhook delivery
Reference · API docs
Troubleshooting retries
Support · docs health
Sync • search • review • ship
One loop to sync, search, review, and ship docs.
Ingest the repo graph, write the markdown updates you need, sync the dashboard, and end with a live docs URL, a draft PR, or a commit back to main.
Pull content, structure, and metadata from GitHub so search, AI, and release workflows stay current.
Draft with AI in the dashboard. Publish through GitHub.
Sync sections, rank better results, answer with citations.
Track feedback, review changes, and ship clean releases.
How it works
Keep your docs runtime. Add the cloud layer around it.
Keep the repo and deploy model you already trust. Add the layer around it.
Connect the docs project
Link the repo and sync the docs model that already lives in your MDX files.
Operate it from one control plane
Draft with AI help, search, analyze, and manage providers from one place.
Push back to GitHub and deploy
Keep GitHub canonical. The repo still remains the thing that ships.
Cloud dashboard
Operate docs from one place.
Indexed sections
12.4k
Search misses
16
Open drafts
08
Healthy pages
91%
GitHub sync
main · docs branch
Search provider
Algolia hybrid
Agent delivery
MCP + llms.txt
First release scope
The first release should feel operational, not abstract. These are the product areas teams should touch first.
# Content
04# Search
04# Agents
04# Ops
04Works at every size
Self-host first. Add cloud when it saves time.
The point is not lock-in. Self-host stays powerful. Cloud adds deploys, retrieval ops, branding, and knowledge workflows at a price smaller teams can actually use.
# Everything core stays open
Self-hostable
Run the full docs runtime yourself. Themes, AI hooks, MCP delivery, API pages, and search integrations stay available without forcing the managed layer.
# Built for small teams too
Affordable cloud
Add managed deploys, RAG pipelines, knowledge workers, branded docs, and search operations at a price that still makes sense for solos and small teams.
# For teams that need a partner
Enterprise layer
Get the whole managed stack, migration support, deeper branding, private workflows, exclusive maintenance, and long-term support as the docs platform evolves with your team.
Managed flow
Sync the graph, write docs, open a draft PR, and ship a live URL.
You ship the code. Cloud writes the docs for you, then opens a draft PR or commits the generated updates to main without replacing the GitHub flow you already trust.
Early access
Help shape the first release around the parts your team actually needs.
Tell us which part of your docs stack is hardest today. We’re using that to shape the first release.