Softwr

Documentation · head to head

BookStack vs Radix UI

BookStack logo

BookStack

Documentation

Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure

From
Free
Rated
-
Full reviewWebsite
Radix UI logo

Radix UI

Web Development

Unstyled, accessible React component primitives

From
Free
Rated
-
Full reviewWebsite

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.; Radix UI you write all the styling, so time to a finished interface is much longer than with a styled library
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, Radix UI covers Unstyled primitives.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which BookStack and Radix UI actually diverge.

Attributes where BookStack and Radix UI differ
AttributeBookStackRadix UI
PlatformsWeb, Self-hosted, DockerWeb
CategoryDocumentationWeb Development

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated).

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 Radix UI

  • Unstyled primitives
  • Accessibility built in
  • Composable API
  • Controlled or uncontrolled

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 Radix UI
  • Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot Radix UI
  • Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot Radix UI
  • Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot Radix UI

Radix UI

  • Design systems that need correct accessibility without inherited visual opinionsnot BookStack
  • Replacing hand-built dropdowns and dialogs that have accessibility bugsnot BookStack
  • Teams with a designer whose output should not be constrained by a library’s themenot 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.

Radix UI

  • You write all the styling, so time to a finished interface is much longer than with a styled library
  • Composable part-based APIs are more verbose than a single component with props
  • Covers primitives rather than complex widgets, so data grids and date pickers come from elsewhere

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

Radix UI

Free
  • Radix UIFree
    • Full functionality
    • Commercial use permitted
    • Community support

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.
BookStack review

Choose Radix UI if

  • You need unstyled primitives.
  • You want to start without paying.
  • You also want accessibility built in.
Radix UI review

Questions people ask

Is BookStack or Radix UI better?
Neither clearly leads. BookStack starts at Free and Radix UI at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or Radix UI?
BookStack starts at Free and Radix UI at Free.
Does BookStack or Radix UI run on more platforms?
BookStack runs on Web, Self-hosted, Docker. Radix UI runs on Web.
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 Radix UI is typically brought in for.
What can BookStack do that Radix UI cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Radix UI covers Unstyled primitives, Accessibility built in, Composable API, Controlled or uncontrolled.

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.

Radix UI: Is Radix UI free?

Yes, open source under the MIT licence.

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.

Radix UI: Why use unstyled components?

Because accessibility is the hard part and visual design is the part teams want to own. Radix gives the first and stays out of the second.

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.

Radix UI: What is the relationship with shadcn/ui?

shadcn/ui is built on Radix primitives, adding Tailwind styling and copy-paste distribution on top.

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.

Share

Related pages

More on BookStack

More on Radix UI

Keep looking

Other head to heads