Documentation · head to head
BookStack vs Nuclino

BookStack
Documentation
Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure
- 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: BookStack there is no vendor-hosted option at all, so you own the server, TLS certificates, database backups and upgrades, or you pay a third-party host that has no support relationship with the project and no ability to fix a bug.; 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: BookStack covers Shelves, books, chapters, pages, Nuclino covers Item graph.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which BookStack 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 BookStack
- Shelves, books, chapters, pages
- Dual editors
- Granular permissions
- Full text search
- Page revisions
- REST API
- External authentication
- Export
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.
BookStack
- Running an internal knowledge base on infrastructure inside a network that cannot reach external SaaSnot Nuclino
- Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot Nuclino
- Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot Nuclino
- Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot Nuclino
Nuclino
- A small company that wants internal process notes searchable without running a wiki platformnot BookStack
- Teams that need to see how internal documents relate to each other rather than filing them in foldersnot BookStack
- Organisations that must keep internal knowledge hosted inside the European Unionnot BookStack
- Replacing scattered shared documents where search, not layout, is the actual problemnot BookStack
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
BookStack
- There is no vendor-hosted option at all, so you own the server, TLS certificates, database backups and upgrades, or you pay a third-party host that has no support relationship with the project and no ability to fix a bug.
- The shelf, book, chapter, page hierarchy is fixed at four levels and cannot be reshaped, so migrating a deeply nested Confluence or MediaWiki space means flattening content by hand and losing the original structure.
- It requires PHP and MySQL or MariaDB, which is a stack many engineering teams no longer run, so adopting it usually means introducing a database and runtime nobody else in the organisation maintains.
- Development is concentrated on a single maintainer, which makes the bus factor a legitimate procurement question for anything the organisation intends to depend on for a decade.
- Content lives in the database rather than in files under version control, so there is no docs-as-code workflow, no review by pull request and no branch per release.
- Export is per page, chapter or book, so moving a large instance to another platform means writing a script against the REST API rather than copying a directory of Markdown.
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
BookStack
Free- BookStackFree
- MIT licence with no paid edition
- All features included, no seat limits
- Self-hosted on your own infrastructure
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 BookStack if
- You need shelves, books, chapters, pages.
- You want to start without paying.
- You work on Web, Self-hosted, Docker.
- You also want dual editors.
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 BookStack or Nuclino better?
- Neither clearly leads. BookStack 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, BookStack or Nuclino?
- BookStack starts at Free and Nuclino at Free.
- Does BookStack or Nuclino run on more platforms?
- BookStack runs on Web, Self-hosted, Docker. Nuclino runs on Web, macOS, Windows, iOS, Android.
- Can I use BookStack for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is BookStack best used for?
- BookStack is most often used for running an internal knowledge base on infrastructure inside a network that cannot reach external saas, documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki produces, replacing a confluence licence for a team that needs pages, permissions and search but none of the surrounding suite, publishing customer-facing manuals from the same instance as internal documentation using per-book permissions. Of those, running an internal knowledge base on infrastructure inside a network that cannot reach external saas and documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki produces are not what Nuclino is typically brought in for.
- What can BookStack do that Nuclino cannot?
- BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Nuclino covers Item graph, Multiple collection views, Real time editing, Instant search.
Answered from the vendors’ own pages
BookStack: Is there a paid or hosted version?
No. BookStack is MIT-licensed with no commercial edition and no official hosted service. Third-party hosts exist but are unaffiliated with the project.
Nuclino: Can Nuclino publish a public documentation site?
No. Individual items can be shared by link, but there is no branded, versioned public site.
BookStack: Can I nest pages more deeply?
No. Four levels is the design, not a limitation waiting to be fixed, and content that needs deeper nesting has to be restructured.
Nuclino: Where is the data stored?
In the European Union, by a company registered in Germany, which is usually the reason procurement shortlists it.
BookStack: Does it support single sign-on?
Yes, through LDAP, SAML2 or OpenID Connect, with group to role mapping, and none of it is gated behind a paid tier because there is no paid tier.
Nuclino: Does it handle translated content?
No. There is no locale model, so translations would be separate items kept in sync by hand.
BookStack: How hard is it to migrate content in?
Straightforward for flat content through the REST API, awkward for deeply nested wikis, because the structure has to be collapsed to fit.
Related pages
Other head to heads
- BookStack vs Slab
- BookStack vs MkDocs
- BookStack vs GitBook
- BookStack vs Outline
- BookStack vs Docsify
- BookStack vs HelpDocs
- BookStack vs Read the Docs
- BookStack vs Doxygen
- BookStack vs Guidde
- BookStack vs Sphinx
- BookStack vs Archbee
- BookStack vs Adobe FrameMaker
- BookStack vs Antora
- BookStack vs Bump.sh
- BookStack vs Paligo
- BookStack vs Adobe RoboHelp
- BookStack vs MadCap Flare
- BookStack vs ReadMe
- BookStack vs Scalar
- BookStack vs Starlight
- BookStack vs VitePress
- Nuclino vs Slab
- Nuclino vs MkDocs
- Nuclino vs GitBook
- Nuclino vs Outline
- Nuclino vs Docsify
- Nuclino vs HelpDocs
- Nuclino vs Read the Docs
- Nuclino vs Doxygen
- Nuclino vs Guidde
- Nuclino vs Sphinx
- Nuclino vs Archbee
- Nuclino vs Adobe FrameMaker
- Nuclino vs Antora
- Nuclino vs Bump.sh
- Nuclino vs Paligo
- Nuclino vs Adobe RoboHelp
- Nuclino vs MadCap Flare
- Nuclino vs ReadMe
- Nuclino vs Scalar
- Nuclino vs Starlight
- Nuclino vs VitePress
