Documentation · head to head
BookStack vs Helicone

BookStack
Documentation
Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure
- From
- Free
- Rated
- -
Helicone
AI
Open-source LLM observability and gateway platform for AI applications
- 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.; Helicone the free Hobby plan is capped at 10,000 requests per month, which teams with production traffic can exceed quickly.
- They diverge on capability: BookStack covers Shelves, books, chapters, pages, Helicone covers Request dashboard and tracking.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which BookStack and Helicone actually diverge.
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 Helicone
- Request dashboard and tracking
- Sessions and segments
- Helicone Query Language (HQL)
- Prompt datasets and improvement
- Playground
- Rate limits and alerts
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 Helicone
- Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot Helicone
- Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot Helicone
- Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot Helicone
Helicone
- Monitoring cost and latency of production LLM applicationsnot BookStack
- Debugging multi-step agent sessionsnot BookStack
- Managing and iterating on prompts across a teamnot BookStack
- Routing requests across multiple LLM providersnot 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.
Helicone
- The free Hobby plan is capped at 10,000 requests per month, which teams with production traffic can exceed quickly.
- Advanced compliance features like SOC 2 and HIPAA are only available starting at the $799/month Team plan.
- Usage beyond the free tier is billed on top of the base subscription, adding cost unpredictability at scale.
- On-premises deployment is restricted to the custom Enterprise 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
Helicone
Free- HobbyFree
- 10,000 free requests
- 1 GB storage
- 1 seat
- Pro$79/month
- 10K free requests included, usage-based beyond
- 7-day free trial
- Unlimited playgrounds and workspaces
- Team$799/month
- 5 organizations
- SOC 2 and HIPAA compliance
- Dedicated Slack channel access
- Enterprise$undefined/mo
- Custom MSAs and SAML SSO
- On-premises deployment
- Bulk cloud discounts
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 Helicone if
- You need request dashboard and tracking.
- You want to start without paying.
- You work on web, api.
- You also want sessions and segments.
Questions people ask
- Is BookStack or Helicone better?
- Neither clearly leads. BookStack starts at Free and Helicone at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BookStack or Helicone?
- BookStack starts at Free and Helicone at Free.
- Does BookStack or Helicone run on more platforms?
- BookStack runs on Web, Self-hosted, Docker. Helicone runs on web, api.
- 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 Helicone is typically brought in for.
- What can BookStack do that Helicone cannot?
- BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Helicone covers Request dashboard and tracking, Sessions and segments, Helicone Query Language (HQL), Prompt datasets and improvement.
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.
Helicone: What does Helicone cost?
Helicone offers a free Hobby plan, a Pro plan at $79/month, a Team plan at $799/month, and custom Enterprise pricing, with usage-based charges applying beyond included request limits.
SourceBookStack: 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.
Helicone: Is there a free plan, and what are its limits?
The free Hobby plan includes 10,000 requests per month, 1 GB of storage, 1 seat, and 1 organization, aimed at kickstarting AI projects.
SourceBookStack: 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.
Helicone: Are there discounts available?
Helicone offers 50% off the first year for qualifying startups, discounts for non-profits, a $100 annual credit for open-source projects, and free access for students.
SourceBookStack: 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.
Related pages
Other head to heads
- BookStack vs Nuclino
- BookStack vs Slab
- BookStack vs MkDocs
- BookStack vs GitBook
- BookStack vs Outline
- BookStack vs Docsify
- BookStack vs HelpDocs
- BookStack vs Read the Docs
- BookStack vs Doxygen
- BookStack vs Guidde
- BookStack vs Sphinx
- BookStack vs Archbee
- BookStack vs Adobe FrameMaker
- BookStack vs Antora
- BookStack vs Bump.sh
- BookStack vs PromptLayer
- BookStack vs Arize AI
- BookStack vs Galileo
- BookStack vs Together AI
- BookStack vs Stable Diffusion
- BookStack vs AutoGen
- BookStack vs LangGraph
- BookStack vs Aider
- BookStack vs Sourcegraph Cody
- BookStack vs Tabnine
- BookStack vs Amazon Q Developer
- BookStack vs Replicate
- BookStack vs Gumloop
- BookStack vs Inflection AI
- BookStack vs LatchBio
- BookStack vs LOVO
- BookStack vs Manus
- BookStack vs Modal
- Helicone vs Nuclino
- Helicone vs Slab
- Helicone vs MkDocs
- Helicone vs GitBook
- Helicone vs Outline
- Helicone vs Docsify
- Helicone vs HelpDocs
- Helicone vs Read the Docs
- Helicone vs Doxygen
- Helicone vs Guidde
- Helicone vs Sphinx
- Helicone vs Archbee
- Helicone vs Adobe FrameMaker
- Helicone vs Antora
- Helicone vs Bump.sh
- Helicone vs PromptLayer
- Helicone vs Arize AI
- Helicone vs Galileo
- Helicone vs Together AI
- Helicone vs Stable Diffusion
- Helicone vs AutoGen
- Helicone vs LangGraph
- Helicone vs Aider
- Helicone vs Sourcegraph Cody
- Helicone vs Tabnine
- Helicone vs Amazon Q Developer
- Helicone vs Replicate
- Helicone vs Gumloop
- Helicone vs Inflection AI
- Helicone vs LatchBio
- Helicone vs LOVO
- Helicone vs Manus
- Helicone vs Modal
