Documentation · head to head
Fumadocs vs Nuclino
Fumadocs
Documentation
Documentation framework for Next.js that treats the docs site as an application rather than a static export
- From
- Free
- Rated
- -
Nuclino
Documentation
Fast team wiki with list, board and graph views of the same content
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Fumadocs it is a library rather than a finished theme, so the initial setup is meaningfully longer than a generator that ships a working site from one command.; 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.
- They diverge on capability: Fumadocs covers Next.js App Router native, Nuclino covers Item graph.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Fumadocs and Nuclino actually diverge.
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 Fumadocs
- Next.js App Router native
- Multiple content sources
- OpenAPI page generation
- Built in search
- Headless and styled layers
- Type safe frontmatter
- Code and content colocation
Only in Nuclino
- Item graph
- Multiple collection views
- Real time editing
- Instant search
- Version history
- EU hosting
What people use each for
The jobs each tool is most often brought in to do.
Fumadocs
- Documentation that must sit behind login and show different content to different customer plansnot Nuclino
- A Next.js product team that wants docs to deploy in the same pipeline as the applicationnot Nuclino
- API reference pages generated from an OpenAPI document alongside hand written guides in one navigation treenot Nuclino
- A design system site where the component documentation must render the live components from the same codebasenot Nuclino
Nuclino
- A small company that wants internal process notes searchable without running a wiki platformnot Fumadocs
- Teams that need to see how internal documents relate to each other rather than filing them in foldersnot Fumadocs
- Organisations that must keep internal knowledge hosted inside the European Unionnot Fumadocs
- Replacing scattered shared documents where search, not layout, is the actual problemnot Fumadocs
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Fumadocs
- It is a library rather than a finished theme, so the initial setup is meaningfully longer than a generator that ships a working site from one command.
- Maintenance is concentrated in a very small group, so an unresponsive week is a blocked upgrade and there is no support contract to escalate to.
- It only targets Next.js, so adopting it commits the documentation to that framework and a later migration means rewriting the site rather than swapping a theme.
- Breaking changes have arrived across minor versions during rapid development, so pinning versions and reading migration notes is a recurring cost rather than a one off.
- Running docs inside the application means docs traffic hits your application infrastructure and shares its failure modes, where a separate static site would have stayed up.
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.
Pricing, plan by plan
Fumadocs
Free- Open sourceFree
- MIT licence
- All packages included
- Self hosted or deployed with your Next.js application
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
Which should you pick?
Choose Fumadocs if
- You need next.js app router native.
- You want to start without paying.
- You work on Web, macOS, Windows, Linux.
- You also want multiple content sources.
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.
Questions people ask
- Is Fumadocs or Nuclino better?
- Neither clearly leads. Fumadocs starts at Free and Nuclino at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Fumadocs or Nuclino?
- Fumadocs starts at Free and Nuclino at Free.
- Does Fumadocs or Nuclino run on more platforms?
- Fumadocs runs on Web, macOS, Windows, Linux. Nuclino runs on Web, macOS, Windows, iOS, Android.
- Can I use Fumadocs for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Fumadocs best used for?
- Fumadocs is most often used for documentation that must sit behind login and show different content to different customer plans, a next.js product team that wants docs to deploy in the same pipeline as the application, api reference pages generated from an openapi document alongside hand written guides in one navigation tree, a design system site where the component documentation must render the live components from the same codebase. Of those, documentation that must sit behind login and show different content to different customer plans and a next.js product team that wants docs to deploy in the same pipeline as the application are not what Nuclino is typically brought in for.
- What can Fumadocs do that Nuclino cannot?
- Fumadocs covers Next.js App Router native, Multiple content sources, OpenAPI page generation, Built in search. Nuclino covers Item graph, Multiple collection views, Real time editing, Instant search.
Answered from the vendors’ own pages
Fumadocs: Can I put documentation behind authentication?
Yes. Pages are Next.js server components, so the same session and authorisation checks the rest of the application uses apply.
Nuclino: Can Nuclino publish a public documentation site?
No. Individual items can be shared by link, but there is no branded, versioned public site.
Fumadocs: Does it work outside Next.js?
No. The UI layer depends on the Next.js App Router.
Nuclino: Where is the data stored?
In the European Union, by a company registered in Germany, which is usually the reason procurement shortlists it.
Fumadocs: Can it generate pages from an OpenAPI spec?
Yes, including operation pages, schema rendering and an interactive request playground.
Nuclino: Does it handle translated content?
No. There is no locale model, so translations would be separate items kept in sync by hand.
Fumadocs: Who maintains it and is that a risk?
A very small maintainer group. For a long lived commercial documentation set, treat the low bus factor as a real risk and budget for owning a fork.
Fumadocs: Do I still need a separate docs deployment?
No, and avoiding one is the main reason to choose it. The cost is that docs share your application uptime.
Related pages
Other head to heads
- Fumadocs vs GitBook
- Fumadocs vs Scalar
- Fumadocs vs Starlight
- Fumadocs vs Redocly
- Fumadocs vs ReadMe
- Fumadocs vs Archbee
- Fumadocs vs Bump.sh
- Fumadocs vs Antora
- Fumadocs vs MkDocs
- Fumadocs vs Read the Docs
- Fumadocs vs Docsify
- Fumadocs vs VitePress
- Fumadocs vs Slab
- Fumadocs vs Doxygen
- Fumadocs vs Guidde
- Fumadocs vs Outline
- Fumadocs vs BookStack
- Fumadocs vs Paligo
- Fumadocs vs Adobe RoboHelp
- Fumadocs vs MadCap Flare
- Fumadocs vs Sphinx
- Nuclino vs GitBook
- Nuclino vs Scalar
- Nuclino vs Starlight
- Nuclino vs Redocly
- Nuclino vs ReadMe
- Nuclino vs Archbee
- Nuclino vs Bump.sh
- Nuclino vs Antora
- Nuclino vs MkDocs
- Nuclino vs Read the Docs
- Nuclino vs Docsify
- Nuclino vs VitePress
- Nuclino vs Slab
- Nuclino vs Doxygen
- Nuclino vs Guidde
- Nuclino vs Outline
- Nuclino vs BookStack
- Nuclino vs Paligo
- Nuclino vs Adobe RoboHelp
- Nuclino vs MadCap Flare
- Nuclino vs Sphinx