Softwr

Documentation · head to head

BookStack vs Rollup

BookStack logo

BookStack

Documentation

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

From
Free
Rated
-
Full reviewWebsite
Rollup logo

Rollup

Web Development

JavaScript module bundler built for libraries

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.; Rollup slower than the Go and Rust bundlers that followed it, since it is written in JavaScript
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, Rollup covers Tree shaking.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which BookStack and Rollup actually diverge.

Attributes where BookStack and Rollup differ
AttributeBookStackRollup
PlatformsWeb, Self-hosted, DockerLinux, macOS, Windows
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 Rollup

  • Tree shaking
  • Clean output
  • Multiple output formats
  • Plugin API

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

Rollup

  • Publishing a JavaScript library in several module formatsnot BookStack
  • Builds where output size and cleanliness matter more than build speednot BookStack
  • Producing ES module output for consumers who will bundle it themselvesnot 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.

Rollup

  • Slower than the Go and Rust bundlers that followed it, since it is written in JavaScript
  • Application concerns like dev servers and hot reloading are not its job, so app builds need Vite on top
  • Configuration for non-trivial applications gets verbose compared with tools that assume more

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

Rollup

Free
  • RollupFree
    • 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 Rollup if

  • You need tree shaking.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want clean output.
Rollup review

Questions people ask

Is BookStack or Rollup better?
Neither clearly leads. BookStack starts at Free and Rollup at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or Rollup?
BookStack starts at Free and Rollup at Free.
Does BookStack or Rollup run on more platforms?
BookStack runs on Web, Self-hosted, Docker. Rollup runs on Linux, macOS, Windows.
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 Rollup is typically brought in for.
What can BookStack do that Rollup cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Rollup covers Tree shaking, Clean output, Multiple output formats, Plugin API.

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.

Rollup: Is Rollup 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.

Rollup: Rollup or webpack?

Rollup is the usual choice for libraries thanks to cleaner output and better tree shaking. webpack remains stronger for complex applications with heavy asset handling.

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.

Rollup: Do I need Rollup if I use Vite?

Not directly. Vite uses Rollup for production builds, so you already benefit from it.

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 Rollup

Keep looking

Other head to heads