Softwr

Documentation · head to head

BookStack vs Hoppscotch

BookStack logo

BookStack

Documentation

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

From
Free
Rated
-
Full reviewWebsite
Hoppscotch logo

Hoppscotch

APIs

Open-source API development ecosystem with web-based REST client

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.; Hoppscotch open-source project with no published commercial support plans or pricing
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, Hoppscotch covers REST Client.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which BookStack and Hoppscotch actually diverge.

Attributes where BookStack and Hoppscotch differ
AttributeBookStackHoppscotch
Pricing modelOpen source, no licence feefreemium
PlatformsWeb, Self-hosted, DockerWeb, Desktop, Self-hosted
CategoryDocumentationAPIs
FoundedUnknown2019

Identical on both: starting price (Free), 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 Hoppscotch

  • REST Client
  • WebSocket
  • gRPC Client
  • GitHub
  • Documentation tools
  • CI/CD
  • Web support
  • Desktop support

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

Hoppscotch

  • API Developmentnot BookStack
  • API Gatewaynot BookStack
  • API Testingnot BookStack
  • API Documentationnot BookStack
  • Microservicesnot 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.

Hoppscotch

  • Open-source project with no published commercial support plans or pricing
  • No official enterprise tier or SLA information disclosed

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

Hoppscotch

Free
  • Open SourceFree
    • Full REST client
    • WebSocket support
    • Community
  • Teams$8/monthly
    • Team collaboration
    • Cloud sync
    • Priority 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 Hoppscotch if

  • You need rest client.
  • You want to start without paying.
  • You work on Web, Desktop, Self-hosted.
  • You also want websocket.
Hoppscotch review

Questions people ask

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

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.

Hoppscotch: Is Hoppscotch free to use for API development?

Yes, Hoppscotch is a completely free, open-source API development ecosystem. There are no subscription fees, license costs, or registration requirements to access the core platform.

Source
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.

Hoppscotch: Can I deploy Hoppscotch on my own infrastructure?

As an open-source project, Hoppscotch can be self-hosted and deployed on your own infrastructure. The source code is available for customization and deployment in private environments.

Source
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.

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 Hoppscotch

Keep looking

Other head to heads