Does ReadMe hold up in 2026 against three years of Reddit criticism?

We went back through the Reddit threads where people explain in detail why they passed on ReadMe or left it. Six objections come up repeatedly. Five are no longer true. The sixth we would choose again, and the last section says who should buy something else anyway.

If you evaluated ReadMe before mid-2025, the tool you tried is not the tool you would be buying now. Branches, reviewable previews, Bi-directional Sync, a CLI, and a rebuilt editor all shipped after most of the public criticism of us was written.

"There is no staging"

From a comment in r/technicalwriting, from someone whose team was leaving: no staging, and no review branches visible in the app.

That was a fair description of legacy ReadMe. It is not a description of Branches, which shipped in August 2025 and lets admins save changes across pages without them going live. Every branch gets a Shareable Branch URL a reviewer can open without an account for seven days, and AI Branch Reviews added a Review tab with a line-by-line diff covering reordering as well as content.

Reviews are the part that answers this properly, and on Enterprise they can be required. A Group Admin can set it so nothing merges until a teammate approves, choose who can approve, and separately restrict who can merge. So an editor submits a branch and an admin publishes it. Admins keep a Skip Requirements and Merge override, which is worth being deliberate about handing out.

We should be clear about the tradeoff we did make, because people mean two things by staging. If you meant a gate before publish, that is what this is, and it is enforceable. If you meant a place you can always point at, we rejected that: one staging site means one preview at a time and a queue behind it, where branches give you as many in-flight previews as you have work in progress. If your process depends on a named URL rather than on a gate, raise it on a call.

That comment was posted after Branches existed. But ReadMe Refactored rolled out project by project, so they may have been accurately describing a hub that did not have any of it yet. That is on us.

"It doesn't work well with our pipelines"

Same commenter. The answer is that we rebuilt the content layer on Git.

Bi-directional sync means changes in the ReadMe editor sync to your repository and changes in your repository sync back. Branches created in GitHub show up in ReadMe and the reverse. Navigation lives in _order.yaml files in the repo, so structure is reviewable in a pull request like anything else. GitHub Enterprise, including on-prem, was part of the June 2025 launch.

The newReadMe CLI landed May 7, 2026. lint catches broken links, duplicate slugs, invalid frontmatter and broken MDX components, with auto-fix. oas:sync keeps reference pages current with your spec, setup:github wires up a GitHub Action, and dev, in beta, runs a local server with hot reload.

Which answers the version of this objection we hear most: engineers did not want to leave their editor, and now they do not have to.

"Only 2 levels" of hierarchy

From the GitBook conversion thread in 2023, where a commenter said the two-level cap was getting worse as their product suite grew.

The sidebar went from three levels to five on June 26, 2026.

API Reference is a different answer, and the distinction matters more than the number. Reference structure is generated from your OpenAPI document: a category per document, pages from your tags, a page per operation. Three levels, because three levels is what a spec describes. OpenAPI has no way to express a tag inside a tag, so there is no fourth level for us to generate. Markdown subpages nest underneath a reference page fine, which is where a longer explanation of one operation belongs. What you cannot do is ask us to invent a hierarchy your spec does not contain.

The more useful admission is why anyone would still believe the limit is two. That change was in our changelog and nowhere else.

So the 2023 complaint is still the best available public answer to a question we fixed. That is a documentation failure, and we sell documentation.

"HTML blocks and inline CSS styling"

The same 2023 thread opened on formatting: images could not be placed inside a paragraph or aligned without dropping into raw HTML.

That editor is gone. The engine moved from Slate to Tiptap in the May 2026 release, which is also where Inline AI and Full Preview Mode arrived. Pages support MDX, so you can write JSX directly on a page and style an <img /> however you want. Tabs, Accordion, Columns and Cards come from the command menu, and Custom Components let you build one in Settings and reuse it.

The exact gripe in that thread, an icon aligned to a line of body text, is a component you write once and reuse. Better than raw HTML on every page, not the same as a button.

"A whole lot of extra clicking"

From r/node, in a 2023 roundup of every API docs platform the author could install. Their criticism was that splitting each endpoint onto its own page looks cleaner and costs you the ability to hit Cmd-F across the whole reference.

This is the one we would choose again, so it helps to say what the choice is for.

A page per endpoint is an addressable unit. It is what lets Try It! sit next to one operation with its own auth and parameters, what makes an endpoint linkable so support can send someone to the exact failing call, and what lets the Developer Dashboard tie a logged request to the page someone was reading. A single-page reference gives you one Cmd-F. It gives up all three.

So we made finding things better than Cmd-F rather than worse. Since June 26, 2026, search matches inside your API Reference: parameter names, request and response schema property names, and their descriptions, not only endpoint titles. Cmd-F on one long page only finds what is currently rendered, so a collapsed schema property is invisible to it. The thing people were asking for was a worse version of what they actually wanted. Jump To sits at the top of the API Reference sidebar at Cmd+/ and filters straight to an operation.

The other need underneath the complaint was getting the reference somewhere you can read or paste it, which the same thread said out loud a year later when someone wanted the spec in local context for an LLM and described rebuilding it page by page. That one is a button now. Copy Page sits on every page, and its menu will view the page as markdown, open it in ChatGPT or Claude, or connect the hub to Cursor or VS Code over MCP. No account required, because the developer evaluating your API does not have one yet.

Which is the part of this we actually care about. Your hub has two audiences now, and the one that does not click is the one that grew.

"$400/mo for CSS"

The r/node roundup put us at $400 a month with custom CSS as the reason to upgrade. That number is stale: the price came down and those plans no longer exist.

As of September 14, 2026, Pro is $250 a month billed annually and Custom CSS & HTML is included, not a line item. Starter is free and ships Bi-directional Sync, an interactive API Reference, a custom domain, LLMs.txt and MCP Server, so you can connect your repo and publish a working hub without talking to us.

Checked on each vendor's own pricing page September 11, 2026, for a team of five.

We are third of four. Redocly is there because it is what the writer in that thread actually chose, and leaving it out would have made a more flattering table and a less useful one.

One clarification, because the word invites the wrong guess. Ask AI Lite is included on Pro and runs the same default model every ReadMe hub gets, so it is not a weaker answer. What the $150 Ask AI add-on buys is choosing your own model and customizing the surface. If you do not need to pick the model, you are not missing answers at $250.

Two honest edges. Our flat rate covers five admins, so unlimited-seat pricing catches up with us somewhere around fifteen. And GitBook charges per site, which cuts the other way once you run several.

For the full side-by-side we keep one each for Mintlify and GitBook.

One decision explains five of these

Read the six objections next to each other and they look like six unrelated gaps. They were mostly one.

No staging, no reviewable branches, no fit with a pipeline, structure you could not rearrange, an editor you could not escape into your own tooling: those are all the same complaint about a content layer that lived in a database and could only be reached through a web app. So we rebuilt it on Git. Every save is a commit, branches are real branches, navigation is a file, and the CLI exists because once content lives in a repo a command line is the obvious way to reach it.

That matters if you looked at ReadMe once and moved on. These were not five feature requests we worked through one at a time. They all fell out of moving content into Git, which is why they landed together, and why an impression formed before that rebuild is wrong about all of them at once.

Who should buy something else

Worth being precise about the money first, because the numbers get repeated wrong. Starter is free. Pro is $250 a month, so $3,000 a year. Five figures is the Enterprise conversation, and it usually starts with multiple sites or governance rather than page count.

ReadMe is the wrong call if you want full control of the frontend and have an engineer who wants to own it, if you need several separate sites without an Enterprise budget, since Pro covers one project, or if your docs are small and slow-moving enough that nobody will resent maintaining a static site. In those cases the r/golang thread and the r/node roundup are giving you good advice, and Docusaurus, Material for MkDocs or Scalar will serve you. Docs behind a login is the one requirement on that list a static site generator will make hard.

ReadMe is probably the right call if your API is the product, if guides and a changelog and a support forum belong in the same place as your reference, if more than a couple of people touch the docs and someone has to approve what ships, if you need to see what developers actually called and what failed, or if you are being asked how your docs behave for agents and do not have an answer.

Come back and check

We would rather be evaluated on what we ship than on what we shipped in 2023. So the ask is small: take the one thing that stopped you and check it. Starter is free and syncs with your repo, which means you can test the specific objection yourself rather than take our word for any of this.

Still have a hub you gave up on, or an objection that is not in these six? Send it to support@readme.io and we will tell you straight whether it is fixed.

FAQ

Does ReadMe have a staging environment?

Not a single named staging site, but you get the gate it exists for. Edit across pages on a branch without publishing, share a Shareable Branch URL with reviewers, diff in the Review tab, then merge. On Enterprise, Reviews can be required, so nothing merges until a teammate approves and merge access can be restricted to admins.

How much does ReadMe cost, and is custom CSS extra?

Checked September 11, 2026: Starter is free, Pro is $250 a month billed annually with up to five admins and $20 each after, Enterprise is custom and annual. Custom CSS & HTML is on Pro, not a separate charge.

Is ReadMe more expensive than GitBook, Mintlify, or Redocly?

Cheaper than two, more than one. Checked on each vendor's own pricing page September 11, 2026, for five people: Redocly Enterprise $120 at $24 per seat with AI search gated to that tier, ReadMe Pro $250 flat with Ask AI Lite included, GitBook Ultimate about $297 with a 500-answer soft cap, Mintlify Pro $450 with its assistant included.

What do I get on the free plan?

Enough to publish a real hub: one project on your own domain, the reference generated from your spec, Git sync in both directions, usage metrics, LLMs.txt and MCP Server. What starts on Pro is Branches, Multiplayer editing, Ask AI Lite, unlimited published versions and Custom CSS & HTML.

Can agents and LLMs read a ReadMe hub?

Yes, and without an account. Copy Page will view any page as markdown, open it in ChatGPT or Claude, or connect the hub to Cursor or VS Code over MCP. Appending .md to a page URL also returns markdown, and every hub publishes LLMs.txt.