Softwr

Documentation · head to head

BookStack vs Bump.sh

BookStack logo

BookStack

Documentation

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

From
Free
Rated
-
Full reviewWebsite
Bump.sh logo

Bump.sh

Documentation

Hosted API documentation that diffs each new spec against the last and publishes a human readable changelog

From
On request
Rated
-
Full reviewWebsite

The short version

  • Only BookStack has a free tier, so it costs nothing to try first.
  • 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.; Bump.sh the service is hosted only, so organisations that cannot send their API specification to a third party are excluded regardless of how well the diff works.
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, Bump.sh covers Structural spec diff.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which BookStack and Bump.sh actually diverge.

Attributes where BookStack and Bump.sh differ
AttributeBookStackBump.sh
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsWeb, Self-hosted, DockerWeb

Identical on both: 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 Bump.sh

  • Structural spec diff
  • Published changelog
  • AsyncAPI support
  • CI integration
  • Multi API hubs
  • Custom domain and branding
  • Access control

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

Bump.sh

  • A public API with paying consumers where an accidental breaking change carries contractual consequencesnot BookStack
  • An event driven platform that needs AsyncAPI documentation rather than REST only toolingnot BookStack
  • A pull request gate that must fail when a spec change breaks an existing clientnot BookStack
  • A partner portal grouping several internal APIs behind access control on a custom domainnot 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.

Bump.sh

  • The service is hosted only, so organisations that cannot send their API specification to a third party are excluded regardless of how well the diff works.
  • Long form guides and tutorials are secondary to the reference, so most teams still run and pay for a second documentation site.
  • Diff quality depends on spec quality, and a specification generated loosely from code annotations produces noisy change reports that teams learn to ignore.
  • It is a small European vendor in a category where larger competitors bundle documentation with gateways and portals, so procurement at a large enterprise can take longer than the evaluation did.
  • Because pricing is not something a buyer can confirm without contact, budgeting for it early in a comparison is guesswork.

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

Bump.sh

On request
  • Bump.sh$undefined/year
    • Hosted API documentation portal
    • Automatic breaking change detection
    • Consumer facing changelog

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 Bump.sh if

  • You need structural spec diff.
  • You also want published changelog.
Bump.sh review

Questions people ask

Is BookStack or Bump.sh better?
Neither clearly leads. BookStack starts at Free and Bump.sh at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or Bump.sh?
BookStack has a free tier; the other does not. Paid plans start at Free for BookStack and On request for Bump.sh.
Does BookStack or Bump.sh run on more platforms?
BookStack runs on Web, Self-hosted, Docker. Bump.sh runs on Web.
Can I use BookStack for free?
Yes. BookStack has a free tier, so you can try it without paying. Bump.sh starts at On request.
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 Bump.sh is typically brought in for.
What can BookStack do that Bump.sh cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Bump.sh covers Structural spec diff, Published changelog, AsyncAPI support, CI integration.

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.

Bump.sh: What does it do that a normal API docs renderer does not?

It compares each published spec with the previous one and tells you, and your consumers, exactly what changed and whether it breaks clients.

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.

Bump.sh: Does it support event driven APIs?

Yes. AsyncAPI is a first class input alongside OpenAPI, which is unusual in this category.

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.

Bump.sh: Can I self host it?

No. It is a hosted service only.

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.

Bump.sh: Can it block a merge?

Yes. The command line tool and GitHub action return a failure on a detected breaking change.

Bump.sh: Is it a full documentation site?

It is primarily reference and changelog. Plan on a separate generator for guides and conceptual content.

Share

Related pages

More on BookStack

More on Bump.sh

Keep looking

Other head to heads