Softwr

Documentation · head to head

BookStack vs Gravitee

BookStack logo

BookStack

Documentation

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

From
Free
Rated
-
Gravitee logo

Gravitee

APIs

Open source API management platform for event-native APIs

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.; Gravitee the entry paid API management tier is $2,500 a month and includes a single production gateway
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, Gravitee covers API Gateway.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which BookStack and Gravitee actually diverge.

Attributes where BookStack and Gravitee differ
AttributeBookStackGravitee
Pricing modelOpen source, no licence feefreemium
PlatformsWeb, Self-hosted, DockerCloud, On-premise, Kubernetes
CategoryDocumentationAPIs
FoundedUnknown2015

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 Gravitee

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

Gravitee

  • API gateway and lifecycle managementnot BookStack
  • Exposing Kafka event streams as managed APIsnot BookStack
  • Protocol mediation between event brokers and clientsnot BookStack
  • Self-hosting an open source API gatewaynot BookStack
  • Access control and authentication in front of internal APIsnot 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.

Gravitee

  • The entry paid API management tier is $2,500 a month and includes a single production gateway
  • Event management is priced separately, starting at $1,250 a month for the Comet tier
  • Tiers are gated on gateway and broker counts, so scaling horizontally means moving tier rather than paying incrementally
  • Data logging masking and other enterprise features are withheld from the lowest paid tier
  • 24/7 support requires the top Universe tier

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

Gravitee

Free
  • CommunityFree
    • API Gateway
    • Basic analytics
    • Community support
  • Enterprise$1500/monthly
    • Advanced features
    • SLA support
    • SSO integration
  • Custom$undefined/monthly
    • Custom deployment
    • Dedicated support
    • Premium SLA

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 Gravitee if

  • You need api gateway.
  • You want to start without paying.
  • You work on Cloud, On-premise, Kubernetes.
  • You also want developer portal.

Questions people ask

Is BookStack or Gravitee better?
Neither clearly leads. BookStack starts at Free and Gravitee at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or Gravitee?
BookStack starts at Free and Gravitee at Free.
Does BookStack or Gravitee run on more platforms?
BookStack runs on Web, Self-hosted, Docker. Gravitee runs on Cloud, On-premise, Kubernetes.
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 Gravitee is typically brought in for.
What can BookStack do that Gravitee cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Gravitee covers API Gateway, Developer Portal, Analytics Dashboard, Kubernetes.

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.

Gravitee: What is Gravitee's pricing model?

Gravitee uses a tiered subscription model with monthly flat pricing. The Planet tier for API Management starts at $2,500/month with one production gateway, while the Comet tier for Event Management starts at $1,250/month.

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.

Gravitee: Are there hidden fees with Gravitee?

No. Gravitee explicitly states there are no hidden fees, and all tiers include unlimited users and unlimited APIs under management.

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.

Gravitee: What does higher tier pricing include in Gravitee?

Higher tiers add more production gateways, enterprise plugins, and enhanced support levels ranging from Gold to Platinum/Diamond support.

Source
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

Other head to heads