Softwr

Documentation · head to head

Nuclino vs ReadMe

Nuclino logo

Nuclino

Documentation

Fast team wiki with list, board and graph views of the same content

From
Free
Rated
-
Full reviewWebsite
ReadMe logo

ReadMe

Documentation

Hosted developer hub priced per API project, with docs personalised from live request logs

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Nuclino there is no publishing layer, so a public help centre or versioned product documentation cannot live here and has to be maintained in a second tool.; ReadMe pricing is per project, so an organisation with several distinct APIs multiplies the monthly bill rather than adding seats, and the sensible workaround, merging unrelated APIs into one documentation project, distorts the information architecture to fit the invoice.
  • They diverge on capability: Nuclino covers Item graph, ReadMe covers OpenAPI reference.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Nuclino and ReadMe actually diverge.

Attributes where Nuclino and ReadMe differ
AttributeNuclinoReadMe
Pricing modelPer user per monthPer project per month
PlatformsWeb, macOS, Windows, iOS, AndroidWeb

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Documentation).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Nuclino

  • Item graph
  • Multiple collection views
  • Real time editing
  • Instant search
  • Version history
  • EU hosting

Only in ReadMe

  • OpenAPI reference
  • Try It playground
  • API metrics
  • Personalised docs
  • Versioning
  • Guides and recipes
  • Git sync via rdme
  • Changelog and support widget

What people use each for

The jobs each tool is most often brought in to do.

Nuclino

  • A small company that wants internal process notes searchable without running a wiki platformnot ReadMe
  • Teams that need to see how internal documents relate to each other rather than filing them in foldersnot ReadMe
  • Organisations that must keep internal knowledge hosted inside the European Unionnot ReadMe
  • Replacing scattered shared documents where search, not layout, is the actual problemnot ReadMe

ReadMe

  • Publishing a public API reference where a developer can send a live request with their own key from the documentation pagenot Nuclino
  • Cutting support load by showing an integrating developer their own recent failing requests next to the endpoint descriptionnot Nuclino
  • Keeping documentation versions aligned with API versions so customers on an older release read the matching referencenot Nuclino
  • Shipping documentation from the same pull request as the code change using the rdme command line tool in CInot Nuclino

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Nuclino

  • There is no publishing layer, so a public help centre or versioned product documentation cannot live here and has to be maintained in a second tool.
  • The free plan is capped at roughly fifty items, which a real team passes within weeks, making it a trial rather than a usable tier.
  • Per user pricing means occasional readers who open a document twice a month cost the same as the writers who maintain it.
  • The editor is intentionally limited, with no databases, relations or page-level templates, so structured content such as a request register needs a different product.
  • Export options are limited to Markdown and PDF per item, so moving a large workspace elsewhere is a bulk conversion job rather than a supported migration.

ReadMe

  • Pricing is per project, so an organisation with several distinct APIs multiplies the monthly bill rather than adding seats, and the sensible workaround, merging unrelated APIs into one documentation project, distorts the information architecture to fit the invoice.
  • The metrics and personalisation features require your API to stream request logs to ReadMe, which means production request metadata leaves your infrastructure and needs a scrubbing layer plus a security review before anything is switched on.
  • Single sign-on and private documentation sit on the higher tier, so a company that only needs to gate partner documentation behind SAML pays a large step up for one control.
  • The platform is built for describing REST APIs, and long-form product manuals, internal knowledge bases or non-OpenAPI protocols fit it badly, so most customers end up running a second documentation tool alongside it.
  • Theming is bounded by ReadMe templates and limited custom CSS, so a documentation site that must match a strongly designed marketing site will not get there without compromise.
  • Content uses ReadMe-specific Markdown extensions and platform features, so migrating away is an export plus a rewrite rather than moving a folder of Markdown files.

Pricing, plan by plan

Nuclino

Free
  • FreeFree
    • Around 50 items in total
    • Limited storage
    • Core editing and search
  • Starter$6/month
    • Per user per month
    • Unlimited items and version history
    • Larger file uploads
  • Business$12/month
    • Per user per month
    • Single sign-on and admin controls
    • Private workspaces and audit features

ReadMe

Free
  • FreeFree
    • One project on a ReadMe subdomain
    • OpenAPI reference and guides
    • Basic editing and publishing
  • Startup$99/month
    • One project
    • Custom domain
    • API metrics from request logs
  • Business$399/month
    • One project
    • SAML single sign-on
    • Private and partner-only documentation
  • Enterprise$undefined/year
    • Multiple projects under one contract
    • Negotiated support and uptime terms
    • Security review and custom deployment questions

Which should you pick?

Choose Nuclino if

  • You need item graph.
  • You want to start without paying.
  • You work on Web, macOS, Windows, iOS, Android.
  • You also want multiple collection views.
Nuclino review

Choose ReadMe if

  • You need openapi reference.
  • You want to start without paying.
  • You also want try it playground.
ReadMe review

Questions people ask

Is Nuclino or ReadMe better?
Neither clearly leads. Nuclino starts at Free and ReadMe at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nuclino or ReadMe?
Nuclino starts at Free and ReadMe at Free.
Does Nuclino or ReadMe run on more platforms?
Nuclino runs on Web, macOS, Windows, iOS, Android. ReadMe runs on Web.
Can I use Nuclino for free?
Both have a free tier, so you can try either at no cost before committing.
What is Nuclino best used for?
Nuclino is most often used for a small company that wants internal process notes searchable without running a wiki platform, teams that need to see how internal documents relate to each other rather than filing them in folders, organisations that must keep internal knowledge hosted inside the european union, replacing scattered shared documents where search, not layout, is the actual problem. Of those, a small company that wants internal process notes searchable without running a wiki platform and teams that need to see how internal documents relate to each other rather than filing them in folders are not what ReadMe is typically brought in for.
What can Nuclino do that ReadMe cannot?
Nuclino covers Item graph, Multiple collection views, Real time editing, Instant search. ReadMe covers OpenAPI reference, Try It playground, API metrics, Personalised docs.

Answered from the vendors’ own pages

Nuclino: Can Nuclino publish a public documentation site?

No. Individual items can be shared by link, but there is no branded, versioned public site.

ReadMe: Is ReadMe priced per user?

No. It is priced per project, meaning per documented API. Team size does not change the bill, and a second API generally does.

Nuclino: Where is the data stored?

In the European Union, by a company registered in Germany, which is usually the reason procurement shortlists it.

ReadMe: Do I have to send my API logs to ReadMe?

Only for metrics and personalised documentation. The reference, guides and playground work without it, but the features that most distinguish the product are the ones that need the log stream.

Nuclino: Does it handle translated content?

No. There is no locale model, so translations would be separate items kept in sync by hand.

ReadMe: Can I keep documentation in Git?

Yes. The rdme command line tool synchronises Markdown and OpenAPI files from a repository, so documentation can ship in the same pull request as the code.

ReadMe: Can I self-host it?

No. ReadMe is a hosted product only, so buyers with a hard on-premises requirement need a different platform.

Share

Related pages

More on Nuclino

More on ReadMe

Keep looking

Other head to heads