People keep asking us "is ShipDocs basically Mintlify?" or "isn't this just NotebookLM for code?" The short answer is no - ShipDocs starts where those tools stop. Mintlify, GitBook, NotebookLM, Cursor, and Sourcegraph each do one piece of the puzzle. ShipDocs does the whole job: it generates the docs, hosts them, grounds AI chat in them, and ships features the others don't have.
This is a side-by-side comparison from the team that builds ShipDocs. We'll be specific about where ShipDocs already wins, and where features that look like gaps today are landing in v2 (months away) or v3 (later this year).
What each tool actually does
| Tool | Core job |
|---|---|
| Mintlify | A polished hosted site you write Markdown / MDX into. |
| GitBook | A hosted wiki / publishing platform you write into. |
| NotebookLM | RAG Q&A grounded in documents you upload. |
| Cursor | An AI-native IDE that edits code. |
| Sourcegraph | Cross-repo code search and navigation. |
| ShipDocs | Generates structured docs from your repo, hosts them, grounds AI chat in them. |
The first five each cover one slice. ShipDocs covers the whole pipeline - generate, host, browse, search, chat - and pulls features from each of the other categories under one roof.
The wide comparison
| Capability | ShipDocs | Mintlify | GitBook | NotebookLM | Cursor | Sourcegraph |
|---|---|---|---|---|---|---|
| Auto-generate docs from real source | yes | no | no | no | n/a | partial (refs) |
| Per-component module breakdown | yes | no | no | no | no | no |
| AI chat grounded in your code | yes (cites paths) | over docs | over docs | over uploads | yes | yes |
| Editable Markdown output you own | yes (WYSIWYG) | yes | yes | no | yes (via IDE) | no |
| Hosted public docs portal | showcase pages, portal w/ templates v2 | yes | yes | no | no | no |
| Markdown-first / LLM-portable | yes | partial | partial | no | n/a | partial |
| Versioned docs | v2 | yes | yes | no | n/a | n/a |
| Scheduled / on-push auto-regen | v2 | n/a | n/a | no | n/a | n/a |
| Multi-language docs (DeepL) | v2 | partial (manual) | partial (manual) | no | no | no |
| Visual dependency diagram | v3 | no | no | no | partial | partial |
| Cross-repo code intelligence | per-account workspace | no | no | no | partial | yes |
| Private repo support | yes | yes | yes | partial | yes | yes |
| CLI: upload your cwd in one command | yes | no | no | no | n/a | partial |
| Markdown twins for AI agents | yes | no | no | no | n/a | no |
| Encrypted at rest with per-project keys | yes | partial | partial | partial | partial | partial |
| Code never used for AI training | yes | partial | partial | partial | no | partial |
| Team members + roles | v2 | yes | yes | no | yes | yes |
| SSO / SAML | v3 | enterprise | enterprise | no | enterprise | enterprise |
| Slack / Teams integration | v3 | partial | partial | no | no | partial |
| Free tier | 2 repos, full docs | small project | small workspace | yes | trial | OSS / starter |
The "v2" and "v3" entries are firm roadmap items, not aspirational — they ship to every account as they land.
ShipDocs vs Mintlify
Mintlify is built around handwritten Markdown / MDX with a polished hosted theme. That's most of what it does - and it's good at it.
The catch is that Mintlify expects the docs to already exist. Someone still has to sit down and write the SDK overview, the API reference walkthroughs, the architecture sections. For an internal codebase or a side project, that someone is usually nobody, which is how most Mintlify sites end up half-empty.
ShipDocs starts where that wall is. We generate the structured docs from your repo automatically - Overview, per-component breakdown, exports, dependencies - then host them at a permanent URL through public showcase pages today and the public docs portal with templates landing in v2. Versioning is on the same v2 train. Multi-language docs via DeepL ships in v2 as well. The hosted-publishing surface that Mintlify is known for is something ShipDocs is filling in over the next two releases, on top of the auto-generation Mintlify will never do.
For most teams, ShipDocs covers both jobs from a single tool - generation today, polished publishing as v2 lands.
ShipDocs vs GitBook
GitBook is a hosted wiki / publishing platform. Same shape as Mintlify but more team-wiki flavored - branching, comments, knowledge-base UX.
The same gap applies: GitBook starts from "you write the docs." If your team has tried hand-writing internal docs and watched them go stale within six months - that's the problem ShipDocs solves directly. We generate docs from the actual current state of the repo, so they reflect what's deployed instead of what someone meant to write down 18 months ago.
GitBook's nicest features - multi-author editing, hosted portal, versioned releases - are inside our v2 roadmap (team members + roles, public docs portal, doc versioning).
ShipDocs vs NotebookLM
NotebookLM is Google's RAG tool: upload sources, ask questions grounded in them. For PDFs and transcripts it's superb. For codebases it's the wrong shape:
- Upload friction. A repo isn't a document. Slicing one into NotebookLM-friendly inputs is awkward and lossy. ShipDocs ingests Git URLs, zip uploads, or your local working directory through
curl -fsSL shipdocs.sh | sh. - No structure. NotebookLM doesn't know that this file is a worker entry point and that one is a migration. Its answers reflect that - surface-level, missing cross-cutting concerns. ShipDocs detects components from the file tree, generates structured per-component docs, then grounds chat in those docs. Every answer cites a file path.
If you're already on NotebookLM for documents, ShipDocs slots in next to it without conflict - it's the codebase-shaped tool you don't have yet.
ShipDocs vs Cursor
Cursor is an AI IDE - it edits code. ShipDocs documents code. They live at different points in the workflow.
Where it gets interesting is that Cursor (and every other AI assistant - Claude Code, Continue, Cody, Copilot) gets dramatically better when ShipDocs has produced an Overview and per-component map of the repo. The agent picks the right files first instead of guessing. Inline suggestions stop inventing function signatures because the docs say what actually exists.
ShipDocs' own grounded chat handles the "explain this codebase" surface inside the product. The visual dependency diagram in v3 layers a navigable graph view on top of the per-component docs - the part of "code intelligence" Cursor doesn't try to cover.
You don't have to choose. You keep your IDE; ShipDocs feeds it better context.
ShipDocs vs Sourcegraph
Sourcegraph has been the cross-repo search leader for a decade. It answers "find every callsite of this function across 400 repos." It's reference-graph-first.
ShipDocs is narrative-and-component-first. It answers "explain this codebase top-down to a new engineer or an AI assistant." Both are useful; they overlap less than the names suggest.
Inside ShipDocs, the workspace already covers cross-repo navigation across the projects on your account, and v3 ships a visual dependency diagram and deeper cross-repo intelligence. For most teams adopting ShipDocs that's enough - the polyrepo-search use case Sourcegraph specializes in is a narrow slice of what most engineers actually need to do.
When ShipDocs is the right pick
- You have at least one repo whose documentation is incomplete, stale, or absent - and nobody is going to handwrite it.
- Your team uses (or wants to use) AI assistants whose effectiveness depends on having a structured map of the codebase.
- You want auto-generated docs with the option to edit on top, instead of writing every word from scratch.
- You care about encryption, private repos, and not having your code used to train AI models.
- You want a public docs URL for an OSS project without standing up a docs site.
- You want one tool that covers generation, hosting, AI chat, versioning, and team access - instead of stitching together five.
That last point is the heart of the comparison. Most of what each tool above does well is on the ShipDocs roadmap and ships to every account as it lands.
Pricing snapshot
| Tool | Free tier | Paid entry |
|---|---|---|
| ShipDocs | 2 repos, full docs | $29/mo (Pro) |
| Mintlify | Limited | Per-seat / page |
| GitBook | Small workspace | Per-user |
| NotebookLM | Free | Pro tier |
| Cursor | 14-day trial | $20/mo |
| Sourcegraph | OSS / starter | Enterprise |
Try ShipDocs
Free tier covers two repos with full structured docs and 100 AI chat messages a month - no credit card required. Paid plans start at $29/mo.
- Get started → shipdocs.sh
- Showcase - see ShipDocs runs on real OSS projects.
- Free tools - README generator, complexity score, explain-in-a-tweet. No signup.
FAQ
Does ShipDocs do everything Mintlify and GitBook do? The auto-generation, AI chat, encryption, and Markdown-first surface are already shipping. The hosted-portal-with-templates and versioned docs land in v2.
Can I use ShipDocs alongside Cursor or Claude Code? Yes - and they get noticeably better when they do. ShipDocs gives your AI tools a structured map of the codebase that they otherwise have to reconstruct from raw source on every query.
What about MDX / interactive docs components?
ShipDocs is Markdown-first by design - it makes the docs portable to LLMs (every page has a text/markdown twin) and keeps the surface clean. The hosted portal landing in v2 covers the polished publishing surface MDX is usually used for.
Do you have versioned docs / scheduled regeneration / team seats? Versioned docs and scheduled / on-push auto-regen ship in v2. Team members + roles ship in v2. SSO/SAML and Slack/Teams integration ship in v3.
Do you have on-prem / self-hosted? Not today. Zero-knowledge mode (per-project keys derived from your passphrase, ciphertext-only at rest) covers most of the use cases that drive on-prem requests. Full self-hosted is on the longer-term roadmap.
Is the comparison fair? We tried. We're biased - we built ShipDocs. If you think we got something wrong about a competitor's product, email us at [email protected] and we'll update the post.
Ready to try ShipDocs? Get started →