ReadMe vs Fern: How Teams Choose Between an SDK Pipeline and a Docs Hub

Two products that overlap on the docs page and diverge almost everywhere else.

ReadMe and Fern end up on the same shortlist because both publish an API reference from an OpenAPI spec. They are built around different first questions. Fern starts from "how do we ship correct client libraries in every language," and Fern's docs are the surface on top of that pipeline. ReadMe starts from "what happens to a developer after they read the page."

That difference decides most of this, and it decides it faster than pricing does.

At a glance

ReadMe pricing from readme.com/pricing and Fern pricing from buildwithfern.com/pricing, both checked September 9, 2026. Fern's plan structure changed recently, so read their live page rather than any comparison, including this one.

Start with the free tier, because it is the real story

Fern's free plan covers 10 team members, 1,000 pages, a custom domain, API references, the API explorer, the web editor, version and product switching, Ask Fern, Fern Writer and an MCP server, with 250 AI credits a month.

That is not a trial. For a team of ten with under a thousand pages, that is a complete documentation site at no cost, and any comparison that skips past it is not worth reading.

Current Postman customers get a bigger version of it. A toggle on Fern's pricing page, labeled "Postman Customer," raises Free to 25 team members, 2,500 pages, 500 AI credits a month and 5,000 page generations a month, roughly 2.5x the standard ceiling on the same feature set. It is gated, not automatic: the page reads "For current Postman customers... Reach out to apply." Checked live, September 9, 2026.

ReadMe's Starter plan is also free, and it's narrow on seats, not capability: one admin, one project, one published version, with a custom domain, Bi-directional sync with GitHub, GitLab and Bitbucket, the AI Dropdown, LLMs.txt and the MCP Server all included. A single maintainer can run the whole thing from Git, under their own domain, for nothing. ReadMe Pro at $250/mo is where more admins seats, branching, review, Multiplayer editing and MDX-ish components arrive.

So if you are ten people, under a thousand pages, comfortable in Git, and what you want is a good-looking docs site next to generated SDKs, Fern's free tier is a real, complete answer for that shape of team. If it is one person running docs entirely from Git who wants a custom domain and real sync without a seat limit forcing an upgrade, ReadMe's free tier does that too.

Key difference: Fern's free plan is built for a small team. ReadMe's free plan is built for one person running everything from Git.

Where each plan stops being public

Both companies put their governance behind a sales conversation, which is normal. Where they differ is what else sits on that side of the line.

On Fern, Enterprise is where SSO, SCIM and advanced RBAC live, and it is also where custom CSS, JavaScript and React components, custom layouts, multiple repositories and documentation instances, advanced analytics and data exports, self-hosting, and the uptime SLA live. Page count is capped there too: Free tops out at 1,000 pages, 2,500 for Postman customers, and going past that is the same sales conversation as everything else on this list. There is no published price between free and custom.

On ReadMe, $250/mo is a published number, and it covers the review workflow, Branches, the AI Linter, Multiplayer editing, custom MDX-ish components, Docs Audit in limited runs, and unlimited published versions. Audit Logs, SSO/OAuth, roles and access control, Private AI Context and Global Lint Rules are Enterprise, and multiple projects are too. Page count isn't on that list at all: readme.com/pricing doesn't publish a page limit on any plan, Starter included.

Key difference: on ReadMe there is a middle you can buy with a credit card. On Fern the step from free is a conversation.

SDKs, which is the thing we do not do

Fern's center of gravity is generating client libraries from one spec so a change to the spec ships everywhere at once. That is a hard problem, it is what they built the company on, and ReadMe does not sell it. Our API Reference generates code samples in the page; it does not publish and version real packages to npm, PyPI and Maven on your behalf.

If shipping SDKs in many languages is the problem keeping you up, that is Fern's problem to solve and not ours. Say so out loud in your evaluation rather than discovering it in month two.

The tradeoff we chose instead is what happens after the call. A Try It! request in ReadMe is logged into the Developer Dashboard alongside the production traffic your API sends through the Metrics SDK. My Developers filters by API key, email or company, so when a customer writes in you are reading their last twenty requests rather than asking for a curl command. Docs page views split Agent vs Human page by page in the same place.

On Fern, that half of the picture is not the product, and the docs analytics they do offer are on Enterprise.

Key difference: Fern makes the client libraries correct. ReadMe makes what the client did visible.

Teams coming from a Git-first, spec-driven workflow, exactly the audience Fern is built for, tend to find this costs them nothing on the way in:

We do all of the work in Git and then we import or upload the Swagger files to ReadMe, and it publishes beautifully.

— Beth Favini, Senior Director of UX Technical Writing and Learning, Akamai

Agent readiness, which Fern was first to measure

Credit where it's due: in April 2026, Fern built Agent Score, a public benchmark that grades any documentation site on a 0–100 scale across 23 checks, ahead of any answer we had. The spec underneath it isn't Fern's, though. AFDocs was written by independent researcher Dachary Carey and open-sourced under a CC BY 4.0 license. Fern is its best-known adopter, not its author.

Both products ship the basics: an MCP server, auto-generated LLMs.txt, an AI answer surface grounded in your content (Ask Fern and Ask AI), and an AI authoring assistant that opens a pull request rather than publishing outright (Fern Writer and GitHub AI Writer). AI proposes, a person merges. That's where the whole category has landed, and it's the right place to land.

Our own answer to Agent Score, Discoverability, shipped in August, built into the product instead of a separate leaderboard. It grades your project against that same AFDocs spec and puts the fix for each failing check right next to it, in Project Settings → AI → Discoverability: LLMs.txt, agent link headers, Content Signals, the MCP Server. Fern's benchmark tells you what's wrong. Ours tells you and hands you the switch — and you don't have to take our word for the score either. On Fern's own Agent Score tool, ReadMe's documentation scored 92/100 (Grade A) against Fern's own 85/100 (Grade B), each checked live in early September 2026.

Key difference: Fern built the public ruler first. ReadMe's version of it lives in the product and hands you the switch to fix what's failing.

Who owns the roadmap

Postman acquired Fern in January 2026. Postman's own announcement says the 25-person team joined intact and that "the product, brand, and roadmap will stay the same, and existing customers won't see any changes." Fern's footer now reads "a Postman company."

Report that rather than read into it. Acquisitions in this category have gone several ways. Anthropic acquired Stainless in May 2026 and TechCrunch reported the hosted product, including the SDK generator, is winding down, with customers keeping rights to SDKs already generated and no date announced. Postman is a large API company and Fern is squarely in its business, which is a better setup than most of the deals on that list.

The question to ask Fern directly is a specific one, not a philosophical one: what happens to Fern's docs product if it starts competing with Postman's own documentation surface. Ask them. Ask us the equivalent question too.

ReadMe has been building API documentation since 2014, independent, with no acquisition and no wind-down. Asana, OneTrust, NVIDIA and Akamai run on it, and so do brand-new YC startups.

Which one should you choose?

Fern is likely the right fit if generated SDKs are the reason you are shopping at all, if your docs are owned end to end by engineers who live in pull requests, if you are ten people or fewer with under a thousand pages and the free tier covers you (25 people and 2,500 pages if you're an existing Postman customer who applies for it), or if you already run Postman and want a single vendor relationship.

ReadMe is likely the right fit if API adoption is the number your team is measured on and you want Try It! requests and production API calls in one dashboard, if writers, PMs and support all need to ship changes without opening a pull request, if you want branch review and linting on by default rather than assembled, or if you want a published mid-tier price instead of a sales cycle to get past free.

Plenty of teams end up running both, with Fern generating the SDKs and ReadMe as the hub. That is a reasonable answer and not a cop-out.

Switching costs, in both directions

Markdown and MDX content moves without much drama, and your OpenAPI spec is portable by definition. That is the strongest argument for keeping the spec as your source of truth no matter who hosts your docs.

What does not move is anything built against the other platform's component model. Custom React components and CSS written for Fern's Enterprise customization need rebuilding in ReadMe's MDX-ish components, and the reverse is equally true. Redirects, information architecture and versioning are where migrations actually spend their time, which our enterprise migration guide covers in detail.

And because Fern's free plan is free forever, not a trial, the two don't have to be a choice at all. Keep Fern for SDK generation, at no added cost, and move your hub to ReadMe: nothing about that combination breaks, since the spec is the same spec. Your API Reference can link straight to Fern's generated SDK docs for each language, so a developer never has to pick a side.

FAQs

Does ReadMe generate SDKs like Fern does?

No. ReadMe generates code samples inside the API Reference and gives developers a Try It! console against your live API. Publishing and versioning real client libraries across languages is Fern's core product, not ours. The tradeoff: ReadMe logs what happens after those calls run, in My Developers next to your production traffic, which Fern's docs side doesn't do at all. If SDKs across languages are your main requirement, weight it heavily.

Did the Postman acquisition change Fern's pricing or product?

Postman's announcement in January 2026 said the product, brand and roadmap stay the same and existing customers would see no changes. Fern's plan structure has changed since then, though we have no source connecting the two. Ask Fern directly what their roadmap looks like inside Postman before you commit a year of docs to it.

Who scores higher on agent readiness?

On Fern's own Agent Score benchmark, built on the independent Agent-Friendly Docs spec, ReadMe's documentation scored 92/100 (Grade A) versus Fern's own 85/100 (Grade B), checked live in early September 2026. Fern built the benchmark first, in April 2026; ReadMe's Discoverability grades against that same spec inside the product, with the fix for each failing check a click away rather than a separate report card.

What does ReadMe track that Fern doesn't?

Every Try It! request lands in the Developer Dashboard next to the production traffic your API sends through the Metrics SDK, filterable by API key, email or company in My Developers. Docs page views split Agent vs Human in the same place. Fern's docs-side analytics are Enterprise-only and don't cover API-side behavior at all: SDK generation is their product, not usage visibility.

Which is cheaper?

Both start free, for different people. Fern's Free plan fits an actual team (10 people, 1,000 pages); ReadMe's Starter plan fits a single maintainer with a custom domain and Bi-directional sync included, including 2.5x more room on Fern's side if you're a current Postman customer who applies for it. Past that, ReadMe Pro is a published $250/mo; Fern's next step is Enterprise with no published price. The comparison shifts again once you need SSO, real roles, deep customization or analytics, which are Enterprise on Fern and partly Pro on ReadMe. Both pricing pages checked live September 9, 2026.

Try it against your own spec

Point both at your real OpenAPI file and publish twenty real pages in each. An hour of that tells you more than any comparison table, ours included.

Get started free, or book a demo and we will run it against your spec and your traffic. Wondering what the API-side data actually looks like once it is wired up? That is the Developer Dashboard, and it is the half of this comparison a table cannot show you.