# Doccupine — full content bundle

> Doccupine is an open-source, AI-ready documentation platform. Markdown and MDX authoring, GitHub-native deploys, custom domains on every plan, an included AI budget or bring-your-own AI model, privacy-first analytics with no third-party trackers, and managed hosting or self-host.

This file concatenates the primary marketing pages of doccupine.com as Markdown for LLM consumption. Each section is separated by a horizontal rule.

---

# Doccupine

> Doccupine is an open-source, AI-ready documentation platform. Markdown and MDX authoring, GitHub-native deploys, custom domains on every plan, an included AI budget or bring-your-own AI model, privacy-first analytics with no third-party trackers, and managed hosting or self-host.

Canonical URL: https://doccupine.com/

## What Doccupine is

Doccupine is the open-source, AI-ready documentation platform. Markdown and MDX authoring. GitHub-native: every doc is a real file in your repo with real commit history. Beautiful out of the box with deep theming (heading, body, and code fonts, 18-color palette, dark mode). Managed hosting or fully self-host.

Every site ships with more than 22 built-in MDX components: Headers and Text, Lists and Tables, Code blocks, Prompts, Callouts, Accordions, Tabs, Steps, File Trees, Cards, Buttons, Badges, Tooltips, Images and Embeds, Frames, Icons, Columns, Side Panels, Spacers, Fields, API Playground, Updates, Color Swatches, and Mermaid diagrams.

## Positioning

- AI assistant on every plan with a monthly spending cap. No per-message metering.
- Bring your own OpenAI, Anthropic, or Google key. Or use our built-in provider.
- MCP server included on every site.
- Privacy-first analytics built in. Native PostHog proxied through your own domain, first-party only, with no third-party trackers.
- Custom domains, custom branding, and team roles included on every paid plan.
- Flat monthly pricing: $200/month Pro, $500/month Enterprise. Team members are included up to the plan limit, not billed per seat.
- Self-hostable under the O'Saasy License (MIT plus a commercial-hosting clause).

## Pricing

- Pro: $200/month. 1 documentation project, up to 5 team members, $20/month AI budget.
- Enterprise: $500/month. 6 documentation projects, unlimited team members, $50/month AI budget.
- Both plans include GitHub repository integration, automatic deployments, custom domain support, the AI documentation assistant, and full theme customization.
- 30-day free trial on both plans, no credit card required on sign-up.

## FAQ

Frequently asked questions are answered at https://doccupine.com/faq.


---

# Generate docs from a GitHub repo

> Paste a GitHub repository and Doccupine's AI reads the code and writes a complete documentation site. Free 30-day trial, no credit card.

Canonical URL: https://doccupine.com/import

## What it does

Point Doccupine at a GitHub repository and its AI crawls the codebase, plans an outline, and writes a complete MDX documentation site into a new repo it creates for you. You start from a real draft rather than a blank page or a template.

## How it works

- Paste a GitHub repo URL. Public repos work without connecting an account.
- The generator reads the repository: structure, routes, handlers, types, and the public surface the project exposes.
- It plans a page outline, then writes each page as MDX using Doccupine's component set.
- The result is committed to a new repository and deployed to managed hosting, ready to edit.

## Cost and limits

- Generation uses the AI credit included with your plan, or your own OpenAI, Anthropic, or Google key if you bring one. The choice is made when the import starts and becomes the project's AI setting.
- Generation is bounded by a per-job page and spend ceiling, so a very large repo produces a solid starting set rather than an unbounded run.
- A 30-day free trial starts on sign-up. No credit card is required.


---

# Self-updating docs with Agent Sync

> Agent Sync automatically links every doc page to the code it documents, then rewrites the affected pages when that code changes - staged for your review, or published automatically.

Canonical URL: https://doccupine.com/self-updating-docs

## The problem it solves

Documentation goes stale because keeping it current is a separate task from shipping the code. Agent Sync removes the separate task: the page knows which code it describes, so a change to that code is what triggers the rewrite.

## How it works

- Link docs to code: the agent connects every page it writes to the exact source files and commit it came from, and Auto-link code maps existing pages to their sources in one click. No manual mapping.
- Ship your code: a push webhook tells Doccupine which linked sources changed, the moment you commit them.
- Docs update themselves: the agent regenerates only the affected pages. Auto-publish, or review the diff first - your call, per project or per page.

## What makes it reliable

- Source-linked pages: every page is automatically mapped to the files it documents and pinned to the commit it was generated from, so drift is exact, not guesswork.
- The source map: every page is shown beside the source files it tracks with a live state - in sync, drifted (with the commits behind), or updating - so the whole doc surface is auditable at a glance.
- Instant drift detection: push webhooks catch changes the moment you commit, so the linked pages are flagged on that same push. Repos without a webhook fall back to a poll every 30 minutes.
- Review or auto-publish: choose per project or per page - stage changes for a quick review, or let them ship straight to production.
- Your edits are safe: a hand-edited page is detected by content hash and always routed to review instead of being overwritten. Detection is by content, not commit authorship, so the agent never flags its own work.
- Monorepo and multi-repo: pull documentation from the project's own repo plus any other source repos you add.

## Billing

Agent Sync runs on the AI credit included with your plan, or on your own provider key if you configure one - the same setting that powers the assistant on your published site. Regeneration is gated by a relevance threshold, so a whitespace or formatting commit does not buy an LLM call.


---

# Documentation solutions for every team

> Documentation generated from your codebase, kept in sync as you ship, and readable by your AI tools. Explore Doccupine by use case (AI-ready/MCP, API & SDK reference, self-updating docs) or by team.

Canonical URL: https://doccupine.com/solutions

## By use case

- Self-updating docs (/self-updating-docs): docs that rewrite themselves when your code changes.
- AI doc generation (/import): point at a repo, get a full documentation site.
- AI-ready docs / MCP (/solutions/ai-ready): answerable by Claude, Cursor, and any MCP client.
- API & SDK reference (/solutions/api-docs): reference docs that never drift from your code.

## By team

- For startups (/solutions/startups): launch-ready docs before you launch.
- For engineering teams: docs in the repo, in sync with every merge.
- For open source: beautiful community docs, GitHub-native.


---

# AI-ready documentation (MCP)

> Every Doccupine site ships an MCP server, so Claude, Cursor, and your own agents answer straight from your live docs, with citations, always current.

Canonical URL: https://doccupine.com/solutions/ai-ready

## Why static docs fall short in the AI era

- Users ask AI first. People open Claude or ChatGPT before they open your docs. If those tools can't read your documentation, they answer from stale training data, or not at all.
- LLMs hallucinate your API. Without a live source to read from, models invent endpoints, parameters, and options that were never in your API. Confident, plausible, and wrong.
- Search returns pages, not answers. Full-text search hands back ten links and leaves the reading to the developer. What they wanted was one synthesized answer they can act on.

## How to connect your docs to an MCP client

- Publish your Doccupine site. Every published site exposes an MCP server at /api/mcp automatically. Nothing to configure, nothing extra to deploy.
- Add the server to Claude, Cursor, or your agent: one entry in your mcpServers config pointed at your docs URL.
- Ask in natural language. The client reads straight from your live docs and answers the question, citing the page it came from.

## Configuration example

```json
{
  "mcpServers": {
    "your-docs": {
      "url": "https://docs.yoursite.com/api/mcp"
    }
  }
}
```

## What you get

- Answers that stay accurate: pages are source-linked and drift-synced, so when your code changes the docs behind the MCP server track it.
- Cited, not guessed: every answer points back to the exact page it came from.
- Locked down when you need it: gate the server with an optional DOCS_API_KEY bearer token, so private documentation stays private while public docs stay open.
- No extra infrastructure: the MCP server ships with every published site, on every plan. No separate service to run and no per-message bill for answers.

## Where teams use it

- Deflect support tickets: point your support assistant at your docs so it answers from the source, with a link to the page, before the question reaches your inbox.
- Answers inside the IDE: developers ask Cursor or Claude about your SDK without leaving the editor.
- Power your own agents: give internal agents a reliable, cited source of product knowledge over MCP instead of pasting docs into prompts by hand.


---

# API & SDK documentation that stays in sync

> Generate API and SDK reference docs from your GitHub repo. Every page is source-linked and drift-detected, so your reference updates the moment code changes.

Canonical URL: https://doccupine.com/solutions/api-docs

## How it works

- Import your repo. Doccupine reads your codebase: the routes, handlers, types, and the public surface your SDK exposes.
- AI drafts the reference: endpoints, parameters, and request and response examples, structured into pages so you start from a real draft, not a blank one.
- Deploy to your domain: managed hosting on your own custom domain, git-backed, with no build pipeline or infrastructure to run.

## Why the reference stays correct

- Pinned to the source: every reference page records the exact file and commit it was generated from.
- Flagged when it changes: when that source changes, the page is flagged and rewritten to match the new behavior.
- Review or auto-publish: stage each update for review or publish it straight to production, decided per page.
- Your edits are protected: a page you have touched by hand always routes to review, so the agent never overwrites your wording.

## Writing and refining in place

- AI compose in the editor: draft or rewrite a block from a prompt right at your cursor, without leaving the page you are on.
- Version history from git: every change is a commit you can trace, diff, and roll back.
- MDX components: fields, badges, callouts, tabs, and code blocks out of the box, demonstrated live on the page.


---

# Documentation for startups

> Import your GitHub repo and ship a docs site that looks like a category leader in an afternoon. Your brand, managed hosting, and a 30-day free trial.

Canonical URL: https://doccupine.com/solutions/startups

## Launch in an afternoon

- Import your repo. Point Doccupine at a GitHub repo and get a complete, well-structured draft in minutes. No blank page, no template to wrangle.
- Make it yours. Set your colors, fonts, and components until it looks unmistakably like you. Every bit of theming is included, none of it paywalled.
- Point your domain. Managed hosting builds and deploys for you. Add your custom domain and your docs are live, the same afternoon you started.

## Polish without a design budget

- Beautiful components: callouts, tabs, code groups, and cards built in, demonstrated live on the page.
- Your brand, fully: an 18-color palette with a dedicated dark mode, custom heading, body, and code fonts, and full CSS control when you want to go further.
- No paywalled theming: customization is not gated behind a higher tier. The site that looks like a category leader costs the same as the one that does not.

## Room to grow

- Team roles: invite teammates and control who can edit, publish, or just read.
- Docs that stay in sync: pages are linked to the source they document, and affected pages are rewritten and staged for you when you ship.
- AI + MCP included: a writing assistant and an MCP server ship on every plan. Bring your own model key and set a budget you are comfortable with.

## Infrastructure you do not have to run

- Managed hosting: we build and deploy your docs for you. No servers, no CI pipeline to babysit.
- Custom domains included: no extra add-on, no upsell.
- GitHub-native: your docs live in your repo as MDX, versioned alongside the code they describe.
- Open source and self-hostable under the O'Saasy License.


---

# About Doccupine

> Why Doccupine exists, what the team believes, and who builds it: documentation that lives in your repo, rewrites itself when the code changes, and answers your AI tools.

Canonical URL: https://doccupine.com/about

## Mission

Documentation should be the most reliable thing you ship. Doccupine turns a GitHub repository into a documentation site you own, hosts and deploys it, and keeps it honest as the code moves.

## The problem it exists to solve

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 confidently wrong. Doccupine builds that maintenance into the tool - pages know which code they describe, and say so when it changes.

## Principles

- Docs belong in the repo: MDX in a GitHub repository you own, with real commits and real history.
- Current beats complete: a short page that is true today beats an exhaustive one that was true last quarter.
- AI-native, not AI-flavored: the agent writes pages, records the source each came from, and rewrites them when that source changes. Every published site ships an MCP server.
- You keep the keys: open source under the O'Saasy License, plain MDX in your own repo, self-hostable. Leaving is a copy, not a migration.
- Design is not an upsell: fonts, a full color palette, dark mode, and custom domains are included on every plan.
- Boring where it counts: flat pricing rather than per-seat metering, a spending cap on every AI budget, first-party analytics with no third-party trackers.

## What Doccupine builds

- Generate: point at a GitHub repo and get a complete MDX documentation site written into a repository it creates for you.
- Sync: every page is pinned to the files and commit it came from, then flagged and rewritten when that source changes - 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 docs and cite the page.
- Host: managed builds, deploys, and custom domains on every plan, or self-host the ordinary Next.js site it produces.

## Who builds it

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 started building it. Small, independent team. No VC funding. Founders answer support email directly at team@doccupine.com, and the community is on Discord at https://discord.gg/E9BufYGPhG.


---

# Doccupine pricing

> Flat monthly pricing: $200/month Pro and $500/month Enterprise. Custom domains, full theming, the AI assistant, and an MCP server are included on every plan. 30-day free trial, no credit card.

Canonical URL: https://doccupine.com/pricing

## Plans

- Pro: $200/month. 1 documentation project, up to 5 team members, $20/month AI budget.
- Enterprise: $500/month. 6 documentation projects, unlimited team members, $50/month AI budget.
- Both plans include GitHub repository integration, automatic deployments, custom domain support, the AI documentation assistant, and full theme customization.
- The plans differ by scale, not by feature set. Nothing is withheld from the smaller plan.

## How billing works

- 30-day free trial on both plans, no credit card required to start.
- Flat monthly pricing, not per seat: team members are included up to the plan limit, so adding a teammate never changes the invoice.
- Month to month with no cancellation fee. Cancel from billing settings at any time.
- Payments are processed by Stripe; Doccupine never sees or stores card details.
- AI is not metered per message. Every plan includes a monthly AI budget, and you can bring your own OpenAI, Anthropic, or Google key instead - in which case the spend goes to your provider and you can cap it per run.

## What is included at no extra cost

- Managed hosting: builds and deploys on every push, with no CI pipeline to run and no build minutes to buy.
- Custom domains, with certificates handled. Not an add-on and not a higher tier.
- Full theming: an 18-color palette with a dedicated dark mode, custom heading, body and code fonts, and every MDX component.
- The AI writing assistant and an MCP server on every plan.
- Self-updating docs: pages are linked to the source they document and rewritten when it changes.

## The free alternative

Doccupine is open source under the O'Saasy License (MIT plus a commercial-hosting clause), so it can be read, modified, and self-hosted at no cost. A paid plan buys managed hosting, deployments, custom domain management, and the AI pipeline run for you. Documentation is plain MDX in a GitHub repository you own, so leaving is a copy rather than a migration.


---

# Contact Doccupine

> How to reach the Doccupine team: email team@doccupine.com for support, sales, billing, and security reports; Discord for community questions; GitHub for bugs and feature requests.

Canonical URL: https://doccupine.com/contact

## Email

team@doccupine.com is the one address for support, sales, billing, press, and security reports. It is read by the founders, Luan Gjokaj and Drew Strojny, and answered within one business day on weekdays. Doccupine is operated by Jestro LLC, 7901 4th Street North, Suite 300, St. Petersburg, Florida 33702, United States.

## Community and code

- Discord: https://discord.gg/E9BufYGPhG for questions, feedback, and talking to other teams running Doccupine.
- GitHub: https://github.com/doccupine (platform) and https://github.com/doccupine/cli (the CLI that builds every site). Open an issue for bugs and feature requests.
- Documentation: https://docs.doccupine.com.

## Security

Report vulnerabilities privately by email to team@doccupine.com rather than in a public issue. Reports are acknowledged within one business day.


---

# Doccupine FAQ

> Answers about what Doccupine is, Markdown and MDX authoring, the AI assistant and MCP server, pricing and the free trial, self-hosting under the O'Saasy License, and how to get support.

Canonical URL: https://doccupine.com/faq

## The product

**What is Doccupine, and who is it for?**

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.

**Do I write in Markdown or MDX? What components do I get?**

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.

**Where do my docs live, and who owns them?**

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.

**Do I have to use Git to edit a page?**

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.

**Can I put my docs on my own domain?**

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.

**Can my whole team work on the docs?**

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

**Can Doccupine write the first draft for me?**

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.

**How do docs update themselves when my code changes?**

Agent Sync automatically 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.

**What is the MCP server, and do I have to set it up?**

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.

**Whose AI key pays for this? Can I turn AI off?**

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

**Is there a free trial? Do I need a credit card?**

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.

**What does Doccupine cost, and what is included?**

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.

**I already use Mintlify, GitBook, ReadMe, or Docusaurus. How hard is the move?**

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 is behind the project? What's the story?**

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.

**Is this really open source? Can I run it for free on my own?**

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.

**What is the difference between managed hosting and self-hosting?**

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.

**How do I get support?**

Email us at team@doccupine.com 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.


---

# Compare documentation platforms

> Side-by-side comparisons of Doccupine against the top documentation platforms: GitBook, Mintlify, ReadMe, and Docusaurus.

Canonical URL: https://doccupine.com/compare

## Why teams choose Doccupine

- AI assistant included on every plan, not metered per message
- Self-updating docs: pages are linked to the code they document and rewritten when it changes, staged for review or published automatically
- AI writing assistant inside the editor, on your included AI budget or your own model key
- Open source and self-hostable under the O'Saasy License
- Actually customizable: fonts, full color palettes, dark mode, MDX components
- Transparent flat pricing: custom domains and branding included

## Head-to-head comparisons

### Doccupine vs GitBook

GitBook moved to per-site billing in 2024: you pay per site and then again per user on top. Doccupine is flat pricing, with AI, custom domains, and full branding included.

Full comparison: https://doccupine.com/compare/gitbook

### Doccupine vs Mintlify

Mintlify makes great docs. Their Pro plan is $450/month billed annually, or $540/month month-to-month, and AI usage runs on metered credits that bill at $0.01 each once you pass your monthly allowance. Doccupine gives you AI docs with a budget you set, and you can self-host it if you want.

Full comparison: https://doccupine.com/compare/mintlify

### Doccupine vs ReadMe

ReadMe is excellent at API docs. But each paid plan covers a single project, AI is a $150/month add-on on top of your plan, and removing ReadMe's own logo from your docs requires their $3,000+/month Enterprise tier.

Full comparison: https://doccupine.com/compare/readme

### Doccupine vs Docusaurus

Docusaurus is free and widely used, but "free" doesn't account for the 8-40 hours of engineering time to set it up, or the ongoing maintenance. Doccupine is also open source, but includes managed hosting and AI out of the box.

Full comparison: https://doccupine.com/compare/docusaurus


---

# Doccupine vs GitBook

> Doccupine vs GitBook: features, pricing, AI and customization compared side by side. See why teams switch from GitBook after the 2024 pricing change.

Canonical URL: https://doccupine.com/compare/gitbook

## Verdict

Pick Doccupine for flat, predictable pricing with AI, custom domains, and full branding included. Pick GitBook if real-time WYSIWYG co-editing is a hard requirement for your team.

## Best for

- Doccupine: Teams that want AI, custom domains and branding without per-user or per-site surprises.
- GitBook: Teams of non-technical writers who live in a WYSIWYG editor with real-time collaboration.

## Choose Doccupine if

- AI is part of your docs workflow and you don't want to pay extra for it
- You're tired of per-site plus per-user billing math
- Your brand needs more than a default theme with limited color options
- You want to own your infrastructure with a self-hostable, open-source platform
- Your workflow is GitHub-first and you want deployments to just happen

## Choose GitBook if

- Multiple people on your team need to edit the same page at the same time
- Your writers aren't comfortable with Markdown and need a full WYSIWYG experience
- Your team is already deep in the GitBook ecosystem and migration isn't worth it
- You need a free tier for public open-source docs

## Feature comparison

### Core Features

| Feature | Doccupine | GitBook |
| --- | --- | --- |
| MDX / Markdown support | Yes | Yes |
| Visual editor | Yes | Yes (WYSIWYG with real-time collab) |
| Version history | Yes | Yes |
| Media management | Yes | Yes |
| Auto-generated navigation | Yes | Yes |
| Custom components | Yes (Full MDX component library) | Partial (Limited to built-in blocks) |

### AI & Automation

| Feature | Doccupine | GitBook |
| --- | --- | --- |
| AI assistant | Yes (Included at every tier) | Paid add-on (Assistant on Ultimate ($249/site/mo)) |
| AI writing in the editor | Yes (Included, bring your own model + monthly cap) | Paid add-on (AI writing and editing, Premium and above) |
| Auto-update docs from code | Yes (Agent Sync: pages linked to source, review or auto-publish) | Partial (Agent connects GitHub as a source (Ultimate)) |
| MCP server | Yes (Every site includes MCP) | Yes (Free plan and above) |
| Bring your own AI model | Yes | No |
| AI budget control | Yes (Monthly spending caps) | No |

### Deployment & Hosting

| Feature | Doccupine | GitBook |
| --- | --- | --- |
| Custom domains | Yes (All plans) | Paid add-on (Premium ($65/mo) and above) |
| Automatic deployments | Yes | Yes |
| GitHub integration | Yes | Yes |
| Managed hosting | Yes | Yes |
| Self-hosting option | Yes (Fully open source) | No |
| Privacy-first analytics | Yes (Built-in PostHog, first-party and self-proxied) | Paid add-on (Insights on Premium ($65/mo) and above) |
| Password-protected sites | Yes (One-toggle shared password, included) | Paid add-on (Visitor authentication on higher plans) |

### Collaboration

| Feature | Doccupine | GitBook |
| --- | --- | --- |
| Team roles & permissions | Yes | Yes |
| Team member limits | Partial (5 on Pro, unlimited on Enterprise) | Partial ($12/user/mo beyond first user) |
| Real-time co-editing | No | Yes |

### Customization

| Feature | Doccupine | GitBook |
| --- | --- | --- |
| Theme colors | Yes | Partial |
| Custom fonts | Yes (Heading, body & code fonts) | No |
| Dark mode | Yes | Yes |
| Custom logo & branding | Yes | Paid add-on |
| Full CSS control | Yes (Open source = full control) | No |

## Pricing

- Doccupine starting price: $200/mo
- GitBook starting price: $65/site/mo + $12/user/mo (billed annually)

- GitBook Premium bills $65 per site/month billed annually, plus $12 per user/month after the first. A team of 5 runs $113/mo before you look at features
- GitBook publishes no monthly-billing rate on its pricing page — the annual plan is the only figure shown
- Want a custom domain? AI features? Your own branding? Those are all behind paywalls on GitBook
- GitBook's Ultimate tier is $249 per site/month, again plus $12 per user/month
- With Doccupine, AI, custom domains, and full theming come standard on every plan

GitBook pricing verified on 2026-07-19 from https://www.gitbook.com/pricing. Prices change without notice; treat this figure as accurate only as of that date.

## What GitBook does well

- Been around since 2014 with 450,000+ users. It's battle-tested
- Real-time co-editing is genuinely great for teams with non-technical contributors
- The free tier for public and open-source docs is generous
- The WYSIWYG editor is solid if your team doesn't want to touch Markdown
- AI-powered translations are a nice touch for multi-language docs (paid plans only)

## Where GitBook falls short

- Paying per site and then again per user means costs climb on two axes at once as a team grows
- Free plan went from 3 users to 1. Custom domains used to be free; now they're paid
- Customization options are shallow. If you want control over layout and design, you'll hit walls quickly
- Sync issues and occasional lost work come up regularly in user reviews
- Support is a weak spot. Slow responses are a common complaint

## Migration

Switching from GitBook is straightforward

- Export your GitBook content as Markdown. Doccupine reads Markdown and MDX natively, so there's no proprietary format to unwind
- Point Doccupine at your GitHub repo. Your docs become real files in your repo with real commit history
- Wire up your custom domain and AI on day one. No upgrade tier to unlock, no add-ons to configure

## FAQ

### Why choose Doccupine over GitBook?

AI is part of your docs workflow and you don't want to pay extra for it You're tired of per-site plus per-user billing math Your brand needs more than a default theme with limited color options You want to own your infrastructure with a self-hostable, open-source platform Your workflow is GitHub-first and you want deployments to just happen

### When does GitBook make more sense than Doccupine?

Multiple people on your team need to edit the same page at the same time Your writers aren't comfortable with Markdown and need a full WYSIWYG experience Your team is already deep in the GitBook ecosystem and migration isn't worth it You need a free tier for public open-source docs

### What does GitBook do well?

Been around since 2014 with 450,000+ users. It's battle-tested Real-time co-editing is genuinely great for teams with non-technical contributors The free tier for public and open-source docs is generous The WYSIWYG editor is solid if your team doesn't want to touch Markdown AI-powered translations are a nice touch for multi-language docs (paid plans only)

### Where does GitBook fall short?

Paying per site and then again per user means costs climb on two axes at once as a team grows Free plan went from 3 users to 1. Custom domains used to be free; now they're paid Customization options are shallow. If you want control over layout and design, you'll hit walls quickly Sync issues and occasional lost work come up regularly in user reviews Support is a weak spot. Slow responses are a common complaint

### Is Doccupine open source?

Yes. Doccupine is open source under the O'Saasy License (MIT plus a commercial-hosting clause). You can self-host, read the code, and modify it freely.

### How long does it take to migrate from GitBook?

Switching from GitBook is straightforward. Export your GitBook content as Markdown. Doccupine reads Markdown and MDX natively, so there's no proprietary format to unwind Point Doccupine at your GitHub repo. Your docs become real files in your repo with real commit history Wire up your custom domain and AI on day one. No upgrade tier to unlock, no add-ons to configure


---

# Doccupine vs Mintlify

> Doccupine vs Mintlify: features, AI pricing, and customization compared. See why teams switch from Mintlify's $450/mo Pro plan and metered AI credits.

Canonical URL: https://doccupine.com/compare/mintlify

## Verdict

Pick Doccupine if predictable AI costs and open-source ownership matter. Pick Mintlify if its codebase-watching Agent (Autopilot) and enterprise compliance are core to your workflow.

## Best for

- Doccupine: Teams that want AI docs with a monthly budget they control, not per-message metering.
- Mintlify: API-first companies that want a mature, well-resourced platform with the Mintlify Agent and enterprise compliance.

## Choose Doccupine if

- $450/month on annual billing (or $540 month-to-month) doesn't match your budget
- You want to pick your own AI model instead of being locked into one provider
- Owning your docs infrastructure matters to you (open source, self-hostable)
- You care about theming beyond what's offered out of the box (custom fonts, full color palettes, dark mode)
- Predictable AI costs matter. No per-message billing surprises

## Choose Mintlify if

- You want doc automations that can run on a cron as well as on a push, and open a pull request against your repo
- Your enterprise needs SSO, SLAs, and SOC 2 compliance
- You want an API playground with years of production polish behind it
- Having a 40+ person team behind the product and dedicated enterprise support is important to you

## Feature comparison

### Core Features

| Feature | Doccupine | Mintlify |
| --- | --- | --- |
| MDX / Markdown support | Yes | Yes |
| Visual editor | Yes | Yes (Web editor released in 2025) |
| Version history | Yes | Yes (Git-based) |
| Media management | Yes | Yes |
| Auto-generated navigation | Yes | Yes |
| Custom components | Yes | Yes (MDX components) |
| API playground | Yes (OpenAPI-driven, live authenticated requests) | Yes (From OpenAPI specs) |

### AI & Automation

| Feature | Doccupine | Mintlify |
| --- | --- | --- |
| AI assistant | Yes (Included on all plans) | Paid add-on (Pro and above; metered credits, $0.01/credit overage) |
| MCP server | Yes | Yes |
| Bring your own AI model | Yes (OpenAI, Anthropic, Google + 12 models) | No |
| AI budget control | Yes (Monthly spending caps) | Partial (Metered credit billing) |
| AI writing in the editor | Yes (Included, bring your own model + monthly cap) | Yes (Agent in the dashboard and Slack) |
| Auto-update docs from code | Yes (Agent Sync: pages linked to source, review or auto-publish) | Yes (Automations (beta): push or schedule, opens a PR) |

### Deployment & Hosting

| Feature | Doccupine | Mintlify |
| --- | --- | --- |
| Custom domains | Yes | Yes (Free tier included) |
| Automatic deployments | Yes | Yes |
| GitHub integration | Yes | Yes |
| Managed hosting | Yes | Yes |
| Self-hosting option | Yes (Fully open source) | No |
| Privacy-first analytics | Yes (Built-in PostHog, first-party and self-proxied) | Partial (Built-in but basic for the price) |
| Password-protected sites | Yes (One-toggle shared password, included) | Paid add-on (Authentication on Pro and above) |

### Collaboration

| Feature | Doccupine | Mintlify |
| --- | --- | --- |
| Team roles & permissions | Yes | Paid add-on (Enterprise only) |
| Team member limits | Partial (5 on Pro, unlimited on Enterprise) | Partial (5 on Pro, +$20/seat/mo extra) |
| Preview deployments | Yes | Paid add-on (Pro only) |

### Customization

| Feature | Doccupine | Mintlify |
| --- | --- | --- |
| Theme colors | Yes (18-color palette + dark mode palette) | Yes |
| Custom fonts | Yes (Heading, body & code fonts) | Partial (Limited font options) |
| Dark mode | Yes | Yes |
| Custom logo & branding | Yes | Yes |
| Full CSS control | Yes (Open source = full control) | Partial (Custom CSS on Pro) |

## Pricing

- Doccupine starting price: $200/mo
- Mintlify starting price: $450/mo (Pro, billed annually)

- Mintlify Pro is $450/month billed annually, or $540/month if you pay month-to-month. AI runs on credits: Pro includes a monthly allowance and overages bill at $0.01 per credit
- A single AI assistant response costs 23 credits and an editor agent run averages 115, so heavy AI use is a variable line item, not a fixed one
- AI features are not available on Mintlify's free Starter plan at all — the assistant, agent, and automations start at Pro
- Pro includes 10,000 credits/month (~434 assistant responses). More credits are sold in packs: 25,000 for $145/mo, 50,000 for $370/mo, 100,000 for $800/mo
- Overages are $0.01 per credit, default to off, and must be enabled on the dashboard Usage page. Up to 50% of unused credits roll over, capping any month at 1.5x your limit
- Need more than 5 editors? That's $20/month per extra seat on Mintlify
- Enterprise plans run $15,000-$25,000/year if you need SSO and SLAs
- Doccupine includes the AI assistant with a monthly budget you control. No per-message billing

Mintlify pricing verified on 2026-07-22 from https://mintlify.com/pricing. Prices change without notice; treat this figure as accurate only as of that date.

## What Mintlify does well

- Mintlify Agent (Autopilot) is genuinely impressive. It watches your codebase and proposes doc updates automatically
- The output looks great out of the box. Minimal configuration needed to get polished docs
- Serious enterprise customers: Anthropic, Cursor, Coinbase, Microsoft, PayPal
- Their OpenAPI playground is mature and battle-tested, with years of polish
- $21M in funding from a16z and a 40+ person team. They're well-resourced

## Where Mintlify falls short

- Going from free to $450/month (or $540 month-to-month) is one of the steepest jumps in the docs space
- AI is metered, so a busy month costs more than a quiet one. At 23 credits per assistant response, Pro's 10,000 monthly credits cover about 434 answers before overages or a credit pack
- The MDX-first workflow is great for developers but can be rough for non-technical contributors
- Analytics are pretty basic for what you're paying
- No self-hosting option. Your docs live on their infrastructure, full stop

## Migration

Mintlify to Doccupine in an afternoon

- Your existing MDX files just work. Doccupine's MDX component library covers the common blocks you're already using
- Connect your GitHub repo in a click. Doccupine builds and deploys automatically, same as Mintlify does
- Swap your OpenAI, Anthropic, or Google key into Doccupine's AI config and cap what a single run may spend. No more per-message math

## FAQ

### Why choose Doccupine over Mintlify?

$450/month on annual billing (or $540 month-to-month) doesn't match your budget You want to pick your own AI model instead of being locked into one provider Owning your docs infrastructure matters to you (open source, self-hostable) You care about theming beyond what's offered out of the box (custom fonts, full color palettes, dark mode) Predictable AI costs matter. No per-message billing surprises

### When does Mintlify make more sense than Doccupine?

You want doc automations that can run on a cron as well as on a push, and open a pull request against your repo Your enterprise needs SSO, SLAs, and SOC 2 compliance You want an API playground with years of production polish behind it Having a 40+ person team behind the product and dedicated enterprise support is important to you

### What does Mintlify do well?

Mintlify Agent (Autopilot) is genuinely impressive. It watches your codebase and proposes doc updates automatically The output looks great out of the box. Minimal configuration needed to get polished docs Serious enterprise customers: Anthropic, Cursor, Coinbase, Microsoft, PayPal Their OpenAPI playground is mature and battle-tested, with years of polish $21M in funding from a16z and a 40+ person team. They're well-resourced

### Where does Mintlify fall short?

Going from free to $450/month (or $540 month-to-month) is one of the steepest jumps in the docs space AI is metered, so a busy month costs more than a quiet one. At 23 credits per assistant response, Pro's 10,000 monthly credits cover about 434 answers before overages or a credit pack The MDX-first workflow is great for developers but can be rough for non-technical contributors Analytics are pretty basic for what you're paying No self-hosting option. Your docs live on their infrastructure, full stop

### Is Doccupine open source?

Yes. Doccupine is open source under the O'Saasy License (MIT plus a commercial-hosting clause). You can self-host, read the code, and modify it freely.

### How long does it take to migrate from Mintlify?

Mintlify to Doccupine in an afternoon. Your existing MDX files just work. Doccupine's MDX component library covers the common blocks you're already using Connect your GitHub repo in a click. Doccupine builds and deploys automatically, same as Mintlify does Swap your OpenAI, Anthropic, or Google key into Doccupine's AI config and cap what a single run may spend. No more per-message math


---

# Doccupine vs ReadMe

> Doccupine vs ReadMe: features, per-project pricing, and AI add-on costs compared. See why multi-product teams outgrow ReadMe's per-project plans.

Canonical URL: https://doccupine.com/compare/readme

## Verdict

Pick Doccupine if your docs include guides, tutorials and product content and you want AI and branding included. Pick ReadMe if a full developer hub — changelogs, forums, and API log analytics around your reference — is the centerpiece of your workflow.

## Best for

- Doccupine: Product and platform teams whose docs go beyond pure API reference.
- ReadMe: API-first products that want a full developer hub: interactive reference, changelogs, forums, and API log analytics.

## Choose Doccupine if

- Your docs go beyond API reference into guides, tutorials, and product documentation
- You don't want your bill to multiply every time you add a new project
- Your brand matters and you want real control over fonts, colors, and layout
- Self-hosting and owning your infrastructure is important
- AI should be included, not a $150/month add-on

## Choose ReadMe if

- Auto-generated code samples in 20+ languages and API log analytics are core to your developer hub
- API docs are your primary (or only) documentation need
- You want changelogs, discussion forums, and developer onboarding in one place
- Enterprise compliance (SSO, audit logs, dedicated support) is non-negotiable

## Feature comparison

### Core Features

| Feature | Doccupine | ReadMe |
| --- | --- | --- |
| MDX / Markdown support | Yes | Yes (MDX on Startup+) |
| Visual editor | Yes | Yes (WYSIWYG with Markdown) |
| Version history | Yes | Yes (API versioning) |
| Media management | Yes | Yes |
| Auto-generated navigation | Yes | Yes |
| Custom components | Yes | Partial (Limited to built-in blocks) |
| Interactive API playground | Yes (OpenAPI-driven, live authenticated requests) | Yes (Live authenticated requests) |
| Changelog & forums | Partial (Changelogs via the Update component; no forums) | Yes (Startup+ plans) |

### AI & Automation

| Feature | Doccupine | ReadMe |
| --- | --- | --- |
| AI assistant | Yes (Included on all plans) | Paid add-on (Owlbot AI, $150/mo add-on for advanced) |
| AI writing in the editor | Yes (Included, bring your own model + monthly cap) | Yes (Agent chat panel drafts, edits and researches) |
| Auto-update docs from code | Yes (Agent Sync: pages linked to source, review or auto-publish) | Yes (GitHub AI Writer, proposes updates from pull requests) |
| MCP server | Yes | Yes (Free tier) |
| Bring your own AI model | Yes | No |
| AI budget control | Yes | No |

### Deployment & Hosting

| Feature | Doccupine | ReadMe |
| --- | --- | --- |
| Custom domains | Yes (All plans) | Paid add-on (Paid plans only) |
| Automatic deployments | Yes | Yes |
| GitHub integration | Yes | Yes (Bidirectional sync on Startup+) |
| Managed hosting | Yes | Yes |
| Self-hosting option | Yes (Fully open source) | No |
| Privacy-first analytics | Yes (Built-in PostHog, first-party and self-proxied) | Partial (API metrics built-in, doc analytics is a paid add-on) |
| Password-protected sites | Yes (One-toggle shared password, included) | Paid add-on (Private docs on paid tiers) |

### Collaboration

| Feature | Doccupine | ReadMe |
| --- | --- | --- |
| Team roles & permissions | Yes | Paid add-on (Enterprise only) |
| Team member limits | Partial (5 on Pro, unlimited on Enterprise) | Partial (Varies by plan) |

### Customization

| Feature | Doccupine | ReadMe |
| --- | --- | --- |
| Theme colors | Yes | Yes |
| Custom fonts | Yes | Paid add-on (Higher paid tiers) |
| Dark mode | Yes | Yes |
| Custom logo & branding | Yes | Yes |
| Full CSS control | Yes (Open source = full control) | Paid add-on (Business plan, CSS/HTML only) |
| Remove vendor branding | Yes (All plans) | Paid add-on (Enterprise ($3,000+/mo) only) |

## Pricing

- Doccupine starting price: $200/mo
- ReadMe starting price: $250/mo (Pro, billed annually)

- ReadMe Pro is $250/month, billed annually, and covers a single project. Multiple products means Enterprise, which starts at $3,000/month
- Ask AI is a $150/month add-on on top of your base plan, on every tier
- Removing the ReadMe logo from your own docs is an Enterprise-only feature — it is not available on Pro at any price
- Pro includes 5 admins; additional admins are $20/month each
- With Doccupine, AI, custom branding, and domains are included at a flat rate on every plan

ReadMe pricing verified on 2026-07-19 from https://readme.com/pricing. Prices change without notice; treat this figure as accurate only as of that date.

## What ReadMe does well

- The API playground is mature and deeply integrated, with live authenticated calls plus API log analytics on top
- It's a full developer hub: API reference, changelogs, forums, and onboarding all in one place
- Code sample auto-generation in 20+ languages from your API specs saves a ton of manual work
- API log analytics give you real insight into how developers actually use your API
- Trusted by serious enterprises: IBM, Microsoft, Intercom. It's a proven platform

## Where ReadMe falls short

- Paid plans cover a single project, so a second API or product means the Enterprise tier at $3,000+/month
- If your docs go beyond API reference (think guides, tutorials, knowledge bases), ReadMe feels limited
- Ask AI is a $150/month add-on, and extended dashboard history is another $100/month, both on top of your plan
- Removing ReadMe's logo from your own docs is Enterprise-only, so vendor branding stays unless you are paying $3,000+/month
- No self-hosting, and content uses proprietary blocks. Migrating away is painful

## Migration

Consolidate your docs onto a flat plan

- Export your ReadMe guides and reference pages to Markdown. Doccupine reads them directly with no proprietary block conversion
- Bring every product and API onto a single Doccupine Enterprise plan instead of paying per-project on ReadMe
- Flip on the built-in AI assistant and remove the ReadMe branding paywall in one go. Both are included, not add-ons

## FAQ

### Why choose Doccupine over ReadMe?

Your docs go beyond API reference into guides, tutorials, and product documentation You don't want your bill to multiply every time you add a new project Your brand matters and you want real control over fonts, colors, and layout Self-hosting and owning your infrastructure is important AI should be included, not a $150/month add-on

### When does ReadMe make more sense than Doccupine?

Auto-generated code samples in 20+ languages and API log analytics are core to your developer hub API docs are your primary (or only) documentation need You want changelogs, discussion forums, and developer onboarding in one place Enterprise compliance (SSO, audit logs, dedicated support) is non-negotiable

### What does ReadMe do well?

The API playground is mature and deeply integrated, with live authenticated calls plus API log analytics on top It's a full developer hub: API reference, changelogs, forums, and onboarding all in one place Code sample auto-generation in 20+ languages from your API specs saves a ton of manual work API log analytics give you real insight into how developers actually use your API Trusted by serious enterprises: IBM, Microsoft, Intercom. It's a proven platform

### Where does ReadMe fall short?

Paid plans cover a single project, so a second API or product means the Enterprise tier at $3,000+/month If your docs go beyond API reference (think guides, tutorials, knowledge bases), ReadMe feels limited Ask AI is a $150/month add-on, and extended dashboard history is another $100/month, both on top of your plan Removing ReadMe's logo from your own docs is Enterprise-only, so vendor branding stays unless you are paying $3,000+/month No self-hosting, and content uses proprietary blocks. Migrating away is painful

### Is Doccupine open source?

Yes. Doccupine is open source under the O'Saasy License (MIT plus a commercial-hosting clause). You can self-host, read the code, and modify it freely.

### How long does it take to migrate from ReadMe?

Consolidate your docs onto a flat plan. Export your ReadMe guides and reference pages to Markdown. Doccupine reads them directly with no proprietary block conversion Bring every product and API onto a single Doccupine Enterprise plan instead of paying per-project on ReadMe Flip on the built-in AI assistant and remove the ReadMe branding paywall in one go. Both are included, not add-ons


---

# Doccupine vs Docusaurus

> Doccupine vs Docusaurus: managed hosting vs self-hosting, AI, setup time, and true cost compared. See why teams pick managed open source over DIY.

Canonical URL: https://doccupine.com/compare/docusaurus

## Verdict

Pick Doccupine if you want open source without standing up CI, DNS, hosting and a visual editor yourself. Pick Docusaurus if you have engineering time to spend and want full React-level control.

## Best for

- Doccupine: Teams that want open source plus managed hosting, AI, and a web editor on day one.
- Docusaurus: React-strong teams with the DevOps bandwidth to own the stack themselves.

## Choose Doccupine if

- You'd rather ship docs today than spend a week setting up CI/CD, DNS, and hosting
- AI-powered writing and search are part of how you want to work
- Not everyone on your team is a developer, and they need a visual editor
- Custom domains, deployments, and team management should just work without DevOps
- Your engineers' time is better spent on the product than on docs infrastructure

## Choose Docusaurus if

- You have engineering resources to set up and maintain the infrastructure, and budget is tight
- You want total customization with React components and a large plugin ecosystem
- Built-in doc versioning per release and i18n are requirements
- You're building docs for a large open-source project with community contributors

## Feature comparison

### Core Features

| Feature | Doccupine | Docusaurus |
| --- | --- | --- |
| MDX / Markdown support | Yes | Yes |
| Visual editor | Yes | No (File-based editing only) |
| Version history | Yes (Git-based with UI) | Yes (Built-in doc versioning) |
| Media management | Yes (Drag-and-drop uploads) | No (Manual file management) |
| Auto-generated navigation | Yes | Yes (Via sidebar config) |
| Custom components | Yes | Yes (Full React component support) |
| Doc versioning (per release) | No | Yes (First-class support) |
| Internationalization (i18n) | No | Yes (Built-in multi-language) |

### AI & Automation

| Feature | Doccupine | Docusaurus |
| --- | --- | --- |
| AI assistant | Yes (Built-in on all plans) | No (Requires third-party (Algolia)) |
| AI writing in the editor | Yes (Included, bring your own model + monthly cap) | No (No hosted editor: you write files in your own IDE) |
| Auto-update docs from code | Yes (Agent Sync: pages linked to source, review or auto-publish) | No |
| MCP server | Yes | No |
| Bring your own AI model | Yes | No |
| AI-powered search | Yes | Partial (Via Algolia DocSearch v4) |

### Deployment & Hosting

| Feature | Doccupine | Docusaurus |
| --- | --- | --- |
| Custom domains | Yes (One-click setup) | Partial (Self-managed DNS configuration) |
| Automatic deployments | Yes (Built-in) | Partial (Requires CI/CD setup (GitHub Actions, etc.)) |
| GitHub integration | Yes | Yes |
| Managed hosting | Yes | No (Self-host on Vercel, Netlify, GitHub Pages, etc.) |
| Privacy-first analytics | Yes (Built-in PostHog, first-party and self-proxied) | No (Requires third-party (Google Analytics, Plausible, etc.)) |
| Password-protected sites | Yes (One-toggle shared password, included) | No (DIY, no built-in gate) |

### Collaboration

| Feature | Doccupine | Docusaurus |
| --- | --- | --- |
| Team roles & permissions | Yes | No (Use GitHub permissions) |
| Web-based editing | Yes | No (Requires local dev environment) |
| Pending changes workflow | Yes (Stage edits before deploying) | No (Use Git branches/PRs) |

### Customization

| Feature | Doccupine | Docusaurus |
| --- | --- | --- |
| Theme colors | Yes | Yes |
| Custom fonts | Yes | Yes (Via CSS configuration) |
| Dark mode | Yes | Yes |
| Custom logo & branding | Yes | Yes |
| Full CSS control | Yes | Yes (Complete control via React/CSS) |
| Plugin ecosystem | No | Yes (Large plugin & theme ecosystem) |

## Pricing

- Doccupine starting price: $200/mo
- Docusaurus starting price: Free (open source, MIT)

- Docusaurus costs $0 on paper. In practice, expect 8-40 hours of engineering time for initial setup and 2-10 hours/month to keep things running
- At typical engineering rates, that's $400-$1,100/month in labor for a small team. "Free" is relative
- Hosting, custom domains, CI/CD, SSL, CDN? All on you. There's no managed option
- Doccupine handles the infrastructure so your team can focus on writing docs, not maintaining them

Docusaurus pricing verified on 2026-07-19 from https://github.com/facebook/docusaurus/blob/main/LICENSE. Prices change without notice; treat this figure as accurate only as of that date.

## What Docusaurus does well

- Truly free and open source (MIT). No vendor, no lock-in, no strings
- If you know React, the customization ceiling is basically unlimited. Plugins, themes, the works
- Doc versioning and i18n are first-class features, not afterthoughts
- Backed by Meta with 64,000+ GitHub stars and a huge community
- Static output means excellent performance. Route-based code splitting, fast loads

## Where Docusaurus falls short

- The setup cost is real. CI/CD, hosting, DNS, SSL, monitoring. Someone on your team is maintaining all of it
- Editing is purely file-based. No visual editor, no web UI, no collaboration tools
- Need analytics, auth, access control, or user feedback? You're adding third-party tools for all of it
- Meaningful customization requires React expertise. Basic config only gets you so far
- When your docs go down at 2am, that's your problem. No managed hosting means no one else is on call

## Migration

Get your weekends back

- Your Markdown and MDX content carries over directly. Doccupine uses the same authoring primitives
- Hand off the CI/CD, DNS, SSL and hosting. Doccupine provisions and manages it with one-click custom domains
- Add AI-powered search and an assistant on day one. No Algolia keys, no plugins to wire up

## FAQ

### Why choose Doccupine over Docusaurus?

You'd rather ship docs today than spend a week setting up CI/CD, DNS, and hosting AI-powered writing and search are part of how you want to work Not everyone on your team is a developer, and they need a visual editor Custom domains, deployments, and team management should just work without DevOps Your engineers' time is better spent on the product than on docs infrastructure

### When does Docusaurus make more sense than Doccupine?

You have engineering resources to set up and maintain the infrastructure, and budget is tight You want total customization with React components and a large plugin ecosystem Built-in doc versioning per release and i18n are requirements You're building docs for a large open-source project with community contributors

### What does Docusaurus do well?

Truly free and open source (MIT). No vendor, no lock-in, no strings If you know React, the customization ceiling is basically unlimited. Plugins, themes, the works Doc versioning and i18n are first-class features, not afterthoughts Backed by Meta with 64,000+ GitHub stars and a huge community Static output means excellent performance. Route-based code splitting, fast loads

### Where does Docusaurus fall short?

The setup cost is real. CI/CD, hosting, DNS, SSL, monitoring. Someone on your team is maintaining all of it Editing is purely file-based. No visual editor, no web UI, no collaboration tools Need analytics, auth, access control, or user feedback? You're adding third-party tools for all of it Meaningful customization requires React expertise. Basic config only gets you so far When your docs go down at 2am, that's your problem. No managed hosting means no one else is on call

### Is Doccupine open source?

Yes. Doccupine is open source under the O'Saasy License (MIT plus a commercial-hosting clause). You can self-host, read the code, and modify it freely.

### How long does it take to migrate from Docusaurus?

Get your weekends back. Your Markdown and MDX content carries over directly. Doccupine uses the same authoring primitives Hand off the CI/CD, DNS, SSL and hosting. Doccupine provisions and manages it with one-click custom domains Add AI-powered search and an assistant on day one. No Algolia keys, no plugins to wire up