Softwr

Documentation · head to head

Nuclino vs VitePress

Nuclino logo

Nuclino

Documentation

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

From
Free
Rated
-
VitePress logo

VitePress

Documentation

Vite powered static site generator for documentation, with instant dev server start and Vue components in Markdown

From
Free
Rated
-

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.; VitePress customising beyond the default theme options requires writing Vue components, so a team with no Vue experience hits a wall at the first design request and cannot resolve it with configuration.
  • They diverge on capability: Nuclino covers Item graph, VitePress covers Vite dev server.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Nuclino and VitePress actually diverge.

Attributes where Nuclino and VitePress differ
AttributeNuclinoVitePress
Pricing modelPer user per monthOpen source, no licence fee
PlatformsWeb, macOS, Windows, iOS, AndroidWeb, macOS, Windows, Linux

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 VitePress

  • Vite dev server
  • Vue in Markdown
  • Local search
  • Default theme
  • Static output
  • Frontmatter driven layout
  • Markdown extensions

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 VitePress
  • Teams that need to see how internal documents relate to each other rather than filing them in foldersnot VitePress
  • Organisations that must keep internal knowledge hosted inside the European Unionnot VitePress
  • Replacing scattered shared documents where search, not layout, is the actual problemnot VitePress

VitePress

  • A documentation set large enough that bundler based generators have made local preview too slow to bother withnot Nuclino
  • A Vue or Vite project that wants its docs on the same toolchain the library itself usesnot Nuclino
  • API reference pages that need live interactive component demos inside the prosenot Nuclino
  • A team that wants client side search without paying for or configuring a hosted search indexnot 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.

VitePress

  • Customising beyond the default theme options requires writing Vue components, so a team with no Vue experience hits a wall at the first design request and cannot resolve it with configuration.
  • There is no built in documentation versioning, so shipping docs for multiple released versions of a product means running separate builds or deploying separate sites and wiring the switcher yourself.
  • Like every git based generator it offers no editing interface, so writers and support staff who spot an error cannot fix it without a developer workflow.
  • The default local search builds its index in the browser at load time, so very large sites see a memory and startup cost on the reader side that Algolia would not impose.
  • The plugin ecosystem is small compared with Docusaurus, so features such as blogging, tag pages or client side redirects are often hand built rather than installed.

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

VitePress

Free
  • Open sourceFree
    • MIT licence
    • All features included
    • Self hosted on any static host

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.

Choose VitePress if

  • You need vite dev server.
  • You want to start without paying.
  • You work on Web, macOS, Windows, Linux.
  • You also want vue in markdown.

Questions people ask

Is Nuclino or VitePress better?
Neither clearly leads. Nuclino starts at Free and VitePress at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nuclino or VitePress?
Nuclino starts at Free and VitePress at Free.
Does Nuclino or VitePress run on more platforms?
Nuclino runs on Web, macOS, Windows, iOS, Android. VitePress runs on Web, macOS, Windows, Linux.
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 VitePress is typically brought in for.
What can Nuclino do that VitePress cannot?
Nuclino covers Item graph, Multiple collection views, Real time editing, Instant search. VitePress covers Vite dev server, Vue in Markdown, Local search, Default theme.

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.

VitePress: Do I have to know Vue?

Not to write Markdown pages. Yes, as soon as you want to change the theme or add an interactive component.

Nuclino: Where is the data stored?

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

VitePress: Does it handle versioned documentation?

Not natively. You build and deploy each version separately and link between them.

Nuclino: Does it handle translated content?

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

VitePress: Is search free?

Yes, the built in local search is free and needs no service. Algolia DocSearch is supported if you prefer hosted search.

VitePress: How does it compare on build speed?

Development start time stays roughly flat as pages are added because Vite does not bundle in development. Production builds still scale with page count.

VitePress: Can non developers contribute?

Only through the git hosting web editor, which still means a commit and a pull request.

Share

Related pages

Other head to heads