We build documentation that stays true to the code.
Doccupine turns a GitHub repository into a documentation site you own, hosted and deployed for you, and then keeps it honest as the code moves. It is open source, and it is built by a small independent team that uses it every day.
30-day free trial. No credit card. Self-host any time.
Documentation should be the most reliable thing you ship.
Not the fastest to write, and not the prettiest. The one artifact a stranger can trust without having to ask anybody first.
Docs do not go wrong all at once.
They go wrong one merge at a time. A parameter is renamed, an endpoint moves, a flag is retired, and the page explaining it is still sitting there, confidently wrong. Nobody decided to let that happen. It simply was not anyone's job that week.
So we built the job into the tool. Pages know which code they describe, and when that code changes they say so, and rewrite themselves.
- Writing was never the hard part.The hard part is the hundredth time you go back to fix a page because something upstream moved.
- Wrong docs cost more than missing ones.A reader burned once by a bad example stops trusting the rest of the site, including every page that is right.
- AI raised the stakes both ways.Assistants answer from whatever they can read. Stale pages scale into confident wrong answers; current ones scale into correct answers.
// lib/auth.ts changed in 4f2a1c9 Shorten token TTL- Access tokens are valid for 24 hours.+ Access tokens are valid for 15 minutes.+ Refresh tokens are valid for 30 days.
What we believe.
Six opinions that settle almost every question we have to answer.
Docs belong in the repo.
Your documentation is MDX in a GitHub repository you own, with real commits and real history. Anything that does not live next to the code will eventually disagree with it.
Current beats complete.
A short page that is true today is worth more than an exhaustive one that was true last quarter. So keeping pages current is the product, not a chore you schedule.
AI-native, not AI-flavored.
The agent writes pages, records the source each one came from, and rewrites them when that source changes. Every published site ships an MCP server so your tools can read the docs too.
You keep the keys.
Doccupine is open source under the O'Saasy License, your content is plain MDX in your own repo, and you can self-host the whole thing. Leaving should be a copy, never a migration.
Design is not an upsell.
Fonts, a full color palette, dark mode, and custom domains are included. Charging extra to let a docs site look like your company is a strange way to sell a docs tool.
Boring where it counts.
Flat pricing instead of per-seat metering, a spending cap on every AI budget, and first-party analytics with no third-party trackers. Predictability is a feature.
What we build.
One product with four jobs, all of them in service of the same sentence: the docs should still be right tomorrow.
Generate.
Point Doccupine at a GitHub repo and it reads the codebase, plans an outline, and writes a complete MDX site into a repository it creates for you. You start from a draft, not a blank page.
Sync.
Every generated page is pinned to the files and the commit it came from. When that source changes, the page is flagged and rewritten, staged for review or published straight to production.
Answer.
Every published site exposes an MCP server, so Claude, Cursor, and your own agents answer from your live documentation and cite the page they read it from.
Host.
Managed builds, deploys, and custom domains on every plan. Or take the source and run it yourself. Either way the output is an ordinary Next.js site.
Small, independent, in the open.
Doccupine is built by two people, in the open. Luan wanted a documentation tool that was open, well designed, and easy to host. Nothing quite fit, so he started building it.
- Independent.No VC funding and no growth-at-all-costs playbook. The product answers to the people paying for it.
- Open source.Published under the O'Saasy License: MIT with one addition, commercial hosting rights reserved. Read it, run it, modify it, self-host it.
- Founders on support.Email us and one of us answers, usually within a few hours. There is no ticket queue and no tier that decides how fast you hear back.
Start your documentation with the repo you already have.
Point Doccupine at a GitHub repository and watch a documentation site take shape. 30-day free trial, no credit card.