Frequently asked questions

Straight answers, no runaround.

What Doccupine is, what it costs, what the AI actually does, and what happens to your content if you leave. If something is missing here, email us and a founder will answer.

30-day free trial. No credit card. Cancel anytime.

The product.

What Doccupine is, how you write, and where your documentation actually lives.

Doccupine turns Markdown or MDX files into a modern documentation website. You write the pages; we build, deploy, and host them. It is made for software teams who want docs that look like a category leader without hiring a design team or babysitting a build pipeline: startups shipping their first docs site, engineering teams keeping a reference in sync with the code, and open source projects that want community docs people actually enjoy reading.
Both. Plain Markdown works on its own, and MDX unlocks the component set. More than 22 components ship built in: callouts, tabs, code blocks and code groups, accordions, steps, file trees, cards, buttons, badges, tooltips, fields, columns, frames, icons, images and embeds, color swatches, an API playground, and Mermaid diagrams. Drop them straight into your MDX with simple syntax. No extra setup, nothing to install per component.
In a GitHub repository, as real MDX files with real commit history. You can create the repo on your own GitHub account, let us create a managed one for you, or connect a repo you already have and we will use it in place. When the repo is yours, it stays yours: Doccupine never creates or deletes a repository it does not manage. There is no proprietary format to unwind, so the day you want to leave, your content walks out with you.
No. The Doccupine editor runs in the browser with a live MDX preview, syntax highlighting, autocompletion, and drag-and-drop uploads for images, fonts, and PDFs. Edits are staged as pending changes, so you can review a batch and publish it as one clean commit when you are ready. Everything is still tracked as Git commits underneath, which means you can browse the full revision history, preview any past version, and restore it instantly.
Yes, on every plan, with no add-on fee. Point docs.yourcompany.com at your site with a single DNS record (an A record for an apex domain, a CNAME for a subdomain) and we verify it for you and track the status while DNS propagates. Custom domains and custom branding are included, not sold as an upgrade.
Yes. Invite teammates by email and give each one of four roles: Owner, Editor, Viewer, or Billing. Editors change files, settings, domains, and environment variables; viewers get read access; the billing role manages the subscription and nothing else; only the owner can invite people or change a role. Members count toward your plan limit rather than adding a per-seat charge.

AI and MCP.

What the AI actually does, whose key pays for it, and how to switch it off.

Yes. Paste a GitHub repository into the import flow and the AI reads your actual source (structure, routes, handlers, types, and the public surface your project exposes), plans an outline, writes a complete multi-page MDX site, commits it, and deploys it. It is not boilerplate: the pages describe what your project really does. That first generation is funded by us rather than billed against your AI budget, and it is bounded by a per-job page and spend ceiling, so a very large repository produces a solid starting set instead of an unbounded run.
Agent Sync links every page the agent writes to the exact source files and commit it came from. When you push a change to one of those files, a webhook tells Doccupine which pages are affected and the agent rewrites just those pages. You decide, per project or per page, whether the rewrite is staged for review or published straight to production. A page you have edited by hand always routes to review: hand edits are detected by content hash rather than commit authorship, so the agent never overwrites your wording and never flags its own work. Repos without a webhook fall back to a poll every 30 minutes. More on Agent Sync.
Every published Doccupine site exposes an MCP server at /api/mcp automatically. Nothing to configure, nothing extra to deploy. Add one entry to the mcpServers config in Claude, Cursor, or your own agent and it answers questions straight from your live docs, citing the page each answer came from. It is included on every plan with no per-message bill, and you can gate it behind a bearer token so private documentation stays private. How AI-ready docs work.
The writing assistant and Agent Sync run on your account's AI budget, which is a monthly cap you can see, spend against, and top up. The one exception is the initial import generation, which we fund. On your published site the assistant can use our built-in provider with zero setup, or your own OpenAI, Anthropic, or Google key with your choice of model and temperature. And if you would rather not have AI at all, a single toggle disables it entirely, with no residual scripts left behind.

Pricing and billing.

Flat plans, a real free trial, and what you get before you pay anything.

There is a 30-day free trial and no credit card is required to start it. The trial begins the moment you sign up rather than when you enter payment details, so you can create a project, generate docs, connect a custom domain, and publish before you decide anything. Cancel at any time.
Two flat monthly plans that differ by scale, not by feature set. Pro is $200 a month and covers 1 documentation project, up to 5 team members, and a $20 monthly AI budget. Enterprise is $500 a month and covers 6 documentation projects, unlimited team members, and a $50 monthly AI budget. Both include GitHub repository integration, automatic deployments, custom domain support, the AI documentation assistant, and full theme customization. Nothing about how your docs look is gated behind the higher tier. See the plans and billing detail.
Usually an afternoon. Doccupine reads Markdown and MDX natively, so there is no proprietary format to unwind: export your pages, put them in a repo, and connect it. Existing MDX largely just works. Coming off a self-managed Docusaurus site, you hand over the CI/CD, DNS, SSL, and hosting and keep your content as it is. Because custom domains, branding, and the AI assistant are included rather than sold as upgrades, there is usually nothing to re-buy on the other side. We keep a dated, sourced comparison for each of them: see the comparisons.

Open source and support.

Who builds this, what the license lets you do, and how to reach a human.

Doccupine is built by Luan Gjokaj and Drew Strojny. Luan wanted a documentation tool that was open, well-designed, and easy to host. Nothing quite fit, so he decided to build it himself. We're a small, independent team. No VC funding, no growth-at-all-costs playbook. When you email us, you'll hear back from the founders directly.
Yes, absolutely! We publish our code under the O'Saasy License because we think you should be able to read, run, and modify the software you depend on. It's the MIT license with one addition: commercial hosting rights are reserved for us. That means you can't offer a competing service hosting Doccupine. We feel that's fair.
Managed hosting is the default: we build and deploy your site, run the infrastructure, and handle custom domains, so there are no servers to run and no CI pipeline to babysit. Self-hosting is the same software on your own infrastructure, with your data and your rules, and full control over deployments and customization. Managed hosting exists because most teams would rather not run a build pipeline, not because the software is locked to it.
Email us at [email protected] or join our Discord. We're a small team so you won't be routed through a ticketing system or talk to a chatbot. You'll get a real answer from someone who actually works on the product, usually within a few hours.

Try it, then decide.

Thirty days, no credit card, and your docs stay in your own repo the whole time. If it is not for you, there is nothing to uninstall.