Documentation should move at the speed of your code. Most teams treat docs as an afterthought — a separate repo, a different deploy pipeline, a stale set of pages no one wants to own. We built Doccupine because we wanted the docs side of our work to feel exactly like the engineering side: versioned in Git, reviewed in pull requests, deployed automatically, and live behind a clean URL within minutes.
This post is a quick tour of what Doccupine gives you out of the box.
Docs that live where your code lives
Doccupine spins up a private GitHub repository for every documentation project, then handles the GitHub → Vercel → custom domain pipeline so your team can focus on writing. No Vercel App to install, no DNS detours, no separate CI to maintain. Push markdown, get a live page.
Every project gets a managed GitHub repo, a Vercel deployment, and an SSL-secured subdomain — provisioned automatically the moment you click Create project.
Get started in three steps
Sign in, click New project, give it a name. Doccupine creates the repo, sets up the deploy hook, and assigns you a *.doccupine.app subdomain so your docs are live before you finish typing.
Use the in-app editor to draft, preview, and publish — or clone the repo locally and push from VS Code. Both flows work the same way: every commit becomes a deploy.
Drop in a CNAME in the dashboard, point your DNS at us, and we handle the SSL handshake, the redirect logic, and the propagation wait. You ship docs at docs.yourcompany.com without writing a line of devops code.
Built for the way you actually write
Markdown gets you 80% of the way to a clean docs site. The rest — callouts, tabs, accordions, syntax-highlighted code — is what makes a page feel polished. Doccupine ships them all as drop-in components you write inline in your markdown.
Fenced code blocks render with syntax highlighting, a GitHub-style chrome, and a one-click copy button.
class HelloWorld {
public static void main(String[] args) {
System.out.println("Hello, World!");
}
}Versioned, auditable, and yours
Every change in Doccupine is a Git commit on a repository you own. Cancel your subscription tomorrow and you walk away with the entire history — no export step, no proprietary lock-in, no scramble to migrate. We think this is how every documentation tool should work.
Documentation that you don't own isn't really yours.
That principle shapes the rest of the product. Every domain is yours. Every page lives at a stable URL you control. Every team member has their own GitHub identity attached to their commits.
More than a markdown editor
A documentation platform isn't really useful until your whole team can use it. Doccupine ships the team-scale features in the box.
Each member can generate their own AI key for drafting, rewriting, and summarising. Usage is attributed to the user who wrote the prompt — no shared quota, no surprise bills landing on the project owner. Bring your own model preference; we route through OpenRouter so you're not locked to one provider.
Four roles cover how docs actually get written: owners manage the project, editors ship content, viewers read drafts before publication, and billing members manage the subscription without touching files. Every commit carries the editor's GitHub identity, so reviewing who shipped what is the same workflow you already use for code.
Hosted plans get the Powered by Doccupine footer hidden automatically — verified at build time with an Ed25519 signature, so you don't have to maintain a fork of the renderer. Add your custom domain, and the only branding readers see is yours.
Try it today
Sign up, create a project, and watch a documentation site go from empty to live in under five minutes. We'd love your feedback while it's fresh.
If you run into anything, find us at [email protected]. Every email gets a reply.