Mintlify alternatives

Ten of them, with prices quoted from their own pricing pages. Most ask you to trade something for the upgrade — your format, your budget, or your weekends. One of them reads the repo you already have.

Your docs.json renders here unchanged. Try it in one command.

Why people move here specifically

Four claims, each one checkable against the table below it.

Your content stays yours

Nothing to convert

We read the same docs.json + MDX. Your repo renders unchanged, and if you ever leave, leaving is a DNS record — not an export project.

SSO without a sales call

$65/mo, self-serve

Single sign-on and role-based access are on the Team plan. At Mintlify, ReadMe and GitBook they’re an Enterprise conversation.

Production docs at $250

Not $450/mo

Pro delivers workflows, insights, and production limits without the category's typical enterprise pricing. Optional hosted AI credits, not the headline feature.

Run it yourself, today

One command

npx papervine dev serves the real renderer with no database and no account. No enterprise engagement, no 45-vCPU cluster, no procurement.

The 10 alternatives, side by side

Prices as of 2026-08-31. “Top self-serve tier” is the most you can pay without a sales call — where a growing team lands before Enterprise.

Platform	Starts at	Top self-serve tier	SSO / RBAC on	Hosting	Content format
Papervine(ours)	Free	$250/mo (Pro)	$65/mo (Team)	Hosted or self-host	docs.json + MDX
Mintlify	Free (Starter)	$450/mo (Pro, billed annually)	Enterprise	Hosted (self-host on Enterprise)	docs.json + MDX
GitBook	Free (1 user)	$249 per site/mo + $12/user (Ultimate)	Enterprise (SAML)	Hosted	GitBook editor, optional Git Sync
ReadMe	Free (1 project)	$250/mo (Pro, annual) + $20/admin	Enterprise	Hosted	OpenAPI + Markdown, bi-directional sync
Redocly	$10/seat/mo (Pro)	$24/seat/mo (Enterprise)	$24/seat/mo (Enterprise)	Hosted or self-host	OpenAPI-first + Markdown
Scalar	Free (1 editor seat)	$72/mo (Pro)	Enterprise	Hosted or self-host	OpenAPI-first
Docusaurus	Free (MIT)	Free — you pay for hosting	You build it	Self-host	MDX + React
Starlight (Astro)	Free (MIT)	Free — you pay for hosting	You build it	Self-host	Markdown / MDX + Astro
Fumadocs	Free (MIT)	Free — you pay for hosting	You build it	Self-host	MDX + Next.js
MkDocs + Material	Free (MIT)	Free — you pay for hosting	You build it	Self-host	Markdown + YAML config

The ten, and what each one costs you

Ours first, because we think it wins for most teams reading this. If your writers will genuinely never open a pull request, GitBook is the better tool and we’d rather you knew that from us.

Papervine

that’s us

The repo you already have, live in minutes, with SSO at $65 instead of a sales call

Point it at your existing repo and you’re done — Papervine reads the same docs.json + MDX, so there is nothing to convert, no export, and no re-authoring. Everything the rest of this page sells as an upgrade is included with the repo: full-text search, an AI assistant with citations, an embeddable widget for your own product, MCP servers so your docs work inside Claude and Cursor, browser editing with an agent, and analytics that separate human readers from crawling agents. SSO and role-based access are on the $65 Team plan — the category holds both for an enterprise negotiation. Pro is $250/mo for scheduled workflows, insights, and production limits, with optional hosted AI credit pools. Every account starts with a 30-day free trial of Pro and 10,000 credits, no card. BYOK available from day one, and npx papervine dev runs the same renderer on your laptop with no database and no signup.

One thing to know: We’re the newest name here, and we’d rather you find that out from us: bring your repo, run it locally in one command, and judge the render instead of the logo. The CLI is source-available under the Elastic License 2.0 — read it, run it, self-host it; you just can’t resell it as a hosted service.

Starts at: Free
Top self-serve tier: $250/mo (Pro)
SSO / RBAC on: $65/mo (Team)
Hosting: Hosted or self-host
Content format: docs.json + MDX
Source: Our pricing

Mintlify

Staying where you are — if $450/mo and an enterprise call for SSO both work for you

The incumbent, and the reason this page exists. Starter is free with 5 editor seats and most of the platform. The AI features people actually come for — agent, assistant, automations, preview deployments — start at Pro: $450/mo billed annually ($540 monthly) with 10,000 credits. Non-commercial open source projects can get Pro free through their OSS program, which is genuinely generous and explicitly not available to companies.

The trade: The jump from free to $450/mo is the whole reason this page gets searched for. SSO, SCIM, role-based permissions, SLAs and insights are Enterprise, i.e. a sales call. Self-hosting is an Enterprise engagement shipping proprietary containers — their own guide sizes a production deployment at roughly 45–60 vCPU, 160–220 GB of memory and about 1 TB of SSD, over "typically weeks", with cloud-dependent integrations unavailable and AI off by default.

Starts at: Free (Starter)
Top self-serve tier: $450/mo (Pro, billed annually)
SSO / RBAC on: Enterprise
Hosting: Hosted (self-host on Enterprise)
Content format: docs.json + MDX
Source: Their pricing page

GitBook

Editors who want a document, if you’re willing to pay per site and per user

The strongest option if the people writing your docs want a document, not a repo. Block-based editing, review flows, and Git Sync when you do want the content mirrored into a repository. Premium is $65 per site/mo plus $12 per user/mo on annual billing; Ultimate is $249 per site/mo plus the same per-user fee and adds authenticated access and the assistant.

The trade: Priced per site AND per user, so the bill grows on two axes at once — a second product's docs is another $65 or $249 a month before anyone edits them. The free tier is one user with the agent capped at 10 messages a week. Content lives in GitBook's model, so leaving is an export-and-convert project rather than a DNS change.

Starts at: Free (1 user)
Top self-serve tier: $249 per site/mo + $12/user (Ultimate)
SSO / RBAC on: Enterprise (SAML)
Hosting: Hosted
Content format: GitBook editor, optional Git Sync
Source: Their pricing page

ReadMe

An API reference as the product — priced per project, then per admin

Built around the API reference: an interactive explorer, per-endpoint usage metrics, and personalized keys for logged-in developers. Starter is free for one project and one published version. Pro is $250/mo billed annually with 5 admins included ($20 for each one after), unlimited projects and versions, branching and reviews, and custom MDX components.

The trade: The free tier's single project and single version rule it out for anything versioned. Ask AI is a $150/mo add-on on top of the plan. User roles and access control, audit logs and SSO are Enterprise, annual-only.

Starts at: Free (1 project)
Top self-serve tier: $250/mo (Pro, annual) + $20/admin
SSO / RBAC on: Enterprise
Hosting: Hosted
Content format: OpenAPI + Markdown, bi-directional sync
Source: Their pricing page

Redocly

API governance at scale, if 100 pages and per-seat modules fit your shape

The most serious option for treating your API descriptions as governed artifacts: linting, a catalog, scorecards, and a docs frontend over them. Seat-priced rather than site-priced — $10/seat/mo on Pro, $24/seat/mo on Enterprise, which is also where SSO, RBAC, AI search, analytics and MCP servers arrive. Notably the cheapest route to SSO on this page for a small team.

The trade: Pro is capped at 1 project and 100 pages; Enterprise at 500. The product is modular (Revel, Reef, Realm), and the modules stack per seat — a realistic docs-plus-catalog setup is a multiple of the headline seat price, so price the combination you actually need rather than the entry number.

Starts at: $10/seat/mo (Pro)
Top self-serve tier: $24/seat/mo (Enterprise)
SSO / RBAC on: $24/seat/mo (Enterprise)
Hosting: Hosted or self-host
Content format: OpenAPI-first + Markdown
Source: Their pricing page

Scalar

A sharp OpenAPI reference — if your docs are mostly reference, not prose

An excellent API reference and a genuinely good API client, with a free tier that gives one editor seat and unlimited viewers, and a $72/mo Pro tier with unlimited editors and hosted MCP servers. The API client is MIT-licensed and offline-first, which is a real commitment rather than a marketing line.

The trade: It's an API-reference platform first. If most of your site is prose — guides, tutorials, concept pages — you're using the narrower half of the tool, and the hosted docs product isn't the open-source part.

Starts at: Free (1 editor seat)
Top self-serve tier: $72/mo (Pro)
SSO / RBAC on: Enterprise
Hosting: Hosted or self-host
Content format: OpenAPI-first
Source: Their pricing page

Docusaurus

Total control, if you have an engineer to spend on docs infrastructure

Meta's docs framework and the default answer to "just self-host it": MDX, React components, real versioning, and the largest plugin ecosystem of any option here. If your docs are a build artifact of your repo and you want no platform in the middle, this is the well-trodden path.

The trade: It's a framework, not a product — search (Algolia DocSearch or a local plugin), analytics, authentication, AI answers, editing for non-developers and the deploy pipeline are all yours to wire up and keep working. Free until you count the engineer maintaining it.

Starts at: Free (MIT)
Top self-serve tier: Free — you pay for hosting
SSO / RBAC on: You build it
Hosting: Self-host
Content format: MDX + React
Source: Their pricing page

Starlight (Astro)

The nicest defaults of the DIY options — and still DIY

Astro's docs theme, and the option with the best defaults: one command gives you an accessible, fast, searchable site with search built in rather than bolted on. Lighter to customize than Docusaurus and quicker to first deploy.

The trade: Same trade as any framework — no hosted editor, no AI answers, no reader authentication, no analytics unless you add them. Versioning is less battle-tested than Docusaurus's.

Starts at: Free (MIT)
Top self-serve tier: Free — you pay for hosting
SSO / RBAC on: You build it
Hosting: Self-host
Content format: Markdown / MDX + Astro
Source: Their pricing page

Fumadocs

Building your docs as an app, when you want to own every component

A Next.js-native docs framework with OpenAPI generation and typed code samples in the box. The natural pick when the docs live in the same repo as a Next app and you'd rather own the components than configure a theme.

The trade: The youngest option here, with the smallest ecosystem to fall back on. You are building an application, not adopting a product — every non-rendering feature is a decision you make and maintain.

Starts at: Free (MIT)
Top self-serve tier: Free — you pay for hosting
SSO / RBAC on: You build it
Hosting: Self-host
Content format: MDX + Next.js
Source: Their pricing page

MkDocs + Material

Markdown and YAML, if you can live without components

Write Markdown, configure one YAML file, get a polished site with client-side search, dark mode, content tabs and admonitions built in. The Material theme's design system is excellent and its previously paid features are now free.

The trade: Markdown, not MDX — no components in your content, so a docs.json-shaped repo does not port over. Python tooling in a JavaScript shop is a small ongoing tax, and the same framework caveat applies: AI, auth, editing and analytics aren't in scope.

Starts at: Free (MIT)
Top self-serve tier: Free — you pay for hosting
SSO / RBAC on: You build it
Hosting: Self-host
Content format: Markdown + YAML config
Source: Their pricing page

Four things this category gets wrong

Not opinions — four facts about how docs platforms are priced, each one checkable on the page it links to.

The gap between free and $450

Mintlify’s Starter is free and Pro is $450/mo billed annually ($540 monthly), with nothing in between. A two-person team that outgrows free gets a bill that reads like a seed-stage line item for a docs site. Our Team plan exists because of exactly that shape: $65/mo, with SSO, RBAC, and AI search already in it — filling the gap the category created.

Source

SSO shouldn't need a sales call

Single sign-on is this category’s classic enterprise hostage: Enterprise-only at Mintlify and at ReadMe, SAML-on-Enterprise at GitBook. Two options on this page will just sell it to you — Redocly at $24/seat/mo, and us at $65/mo flat, no seat math and no procurement thread. Locking your docs down should be a checkbox, not a quarter.

Source

"Self-hosted" means very different things

Read the fine print before you count it as a feature. Mintlify’s self-hosting is an Enterprise engagement delivering proprietary containers: their own guide sizes production at roughly 45–60 vCPU, 160–220 GB of memory and about 1 TB of SSD, over "typically weeks", with cloud-dependent integrations unavailable and AI disabled by default. A framework like Docusaurus is the opposite extreme — free, yours, and entirely your problem. Ours is one command on a laptop today (npx papervine dev, no database, no account), and Postgres plus object storage when you want the whole control plane.

Source

AI is metered now, everywhere

Every hosted platform here meters AI separately from seats: Mintlify’s Pro includes 10,000 credits, GitBook caps assistant answers, ReadMe charges $150/mo for Ask AI on top of the plan. It’s the axis that grows with your READERS rather than your team, which is why it’s the one that surprises people. We support BYOK from day one on all plans, with optional hosted credit pools available on Team and Pro. We put a chart on the usage page showing which feature spent them, and hard-cap by default so there is no surprise invoice — overage is something you opt into.

Source

Moving without rewriting anything

Every list like this one is written by somebody who wants you to move in. Here is the part they leave out: if the next platform reads the same docs.json your repo already has, then moving is a DNS change — and so is moving back out again if you don’t like it. That symmetry is the whole point, and it is the reason to care about the format rather than the feature grid.

1
Run it on your own repo first
npx papervine dev in your docs directory. No account, no database, no signup — the same renderer the hosted product uses, reading your existing docs.json.
2
Connect the repo as a new site
You get a complete working copy at a Papervine address while your current site keeps serving its own traffic. Nothing is irreversible until DNS moves.
3
Compare your ten most-visited pages
Side by side with the live site. This finds real problems faster than reading any compatibility matrix, including this one.
4
Add your domain, let the certificate issue, then flip DNS
In that order, so the certificate is ready before traffic arrives. Leave the old site up for a day or two — reverting is a DNS change back.

Read the migration guide See the source

Questions people ask

Is there a free Mintlify alternative?

Yes, and there are two kinds. The frameworks — Docusaurus, Starlight, Fumadocs, MkDocs — are free and MIT-licensed, and everything a docs platform does beyond rendering (search, auth, analytics, AI, editing) is yours to build. Among hosted platforms, Papervine’s free tier renders your existing docs.json with search included, and every new account gets a 30-day free trial of Pro plus 10,000 AI credits without a card.

Can I self-host Mintlify?

Only on an Enterprise plan, and it isn't an open-source deployment: their guide describes a scoped engagement with your account team delivering versioned proprietary containers, production sizing of roughly 45–60 vCPU, 160–220 GB of memory and about 1 TB of SSD, taking "typically weeks", with cloud-dependent integrations unavailable and AI features disabled by default.

Do I have to rewrite my MDX to switch?

Not if you pick a platform that reads the format you already have. Papervine renders docs.json + MDX directly — frontmatter, navigation, components, your OpenAPI spec — so the repo goes up unchanged and the migration is a DNS record. Moving to a platform with its own content model (GitBook) or an authoring format without components (MkDocs) is a conversion project, and should be scoped as one before anyone promises a date.

What is docs.json, and does it lock me in?

It’s the config file describing a docs site — navigation, theme, metadata — beside a tree of MDX pages, all of it in your own Git repository. On its own it’s the opposite of lock-in, but only because more than one renderer reads it: the moment two platforms speak your format, your switching cost is a DNS record in either direction. That’s the single best reason to choose on format rather than on a feature grid.

What's the cheapest way to get SSO on a docs site?

As of 2026-08-31, two options will sell it to you without a call: Redocly at $24 per seat/month, and Papervine’s Team plan at $65/month flat — which also includes role-based access, the AI assistant and 1,000 credits. At Mintlify, ReadMe and GitBook, single sign-on is an Enterprise conversation.

Is Mintlify free for open source projects?

Yes — their OSS program gives Pro free to non-commercial open source projects: a recognized license (MIT, Apache 2.0, GPL), no venture or revenue funding, and not owned or primarily maintained by a for-profit company.

Is Papervine open source?

Source-available rather than OSI open source, and we’d rather say so plainly than fudge it: the CLI and renderer ship under the Elastic License 2.0. You can read the code, run it, and self-host it — the one thing you can’t do is resell it as a hosted service. npx papervine dev serves a docs repo with no account and no database, which is more than most of this category will let you do at any price.

Try it against your own repo

Nothing to convert and nothing to decide: point it at the docs you already have and see what renders. Locally in one command, or hosted with 30 days of everything and 10,000 AI credits — no card.

Start free See pricing

Your existing docs.json renders unchanged

Papervine is not affiliated with, endorsed by, or sponsored by any product named on this page; all names and trademarks belong to their owners. Prices and limits are quoted from each vendor's own pricing page as of 2026-08-31 — check the linked page for what's current, and tell us if we've got something wrong.