Documentation · head to head
BookStack vs PostHog

BookStack
Documentation
Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure
- From
- Free
- Rated
- -

PostHog
Technology
The single platform to analyze, test, observe, and deploy new features
- 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.; PostHog the free tier covers 1M events, 5K web session recordings and 2.5K mobile recordings per month before usage-based billing starts
- They diverge on capability: BookStack covers Shelves, books, chapters, pages, PostHog covers Product analytics.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which BookStack and PostHog 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 PostHog
- Product analytics
- Session recording
- Feature flags
- A/B testing
- Heatmaps
- SQL access
- Data warehouse
- Apps platform
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 PostHog
- Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot PostHog
- Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot PostHog
- Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot PostHog
PostHog
- Product analyticsnot BookStack
- Feature experimentationnot BookStack
- User behavior trackingnot BookStack
- A/B testingnot BookStack
- Debug production issuesnot 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.
PostHog
- The free tier covers 1M events, 5K web session recordings and 2.5K mobile recordings per month before usage-based billing starts
- Accounts without a card on file are limited to 1 project; adding one raises it to 6
- Data retention is 1 year until a card is added, which extends it to 7 years
- Support is community-only until the account is on a paid plan
- Error tracking is capped at 100K exceptions and surveys at 1500 responses per month on the free 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
PostHog
Free- FreeFree
- 1M events/month
- 5K sessions/month
- Unlimited users
- Paid$undefined/month
- $0.00031/event
- $0.005/session
- Advanced permissions
- Enterprise$undefined/month
- SAML SSO
- Advanced security
- Dedicated 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.
Choose PostHog if
- You need product analytics.
- You want to start without paying.
- You work on Web, Ios, Android, Api.
- You also want session recording.
Questions people ask
- Is BookStack or PostHog better?
- Neither clearly leads. BookStack starts at Free and PostHog at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BookStack or PostHog?
- BookStack starts at Free and PostHog at Free.
- Does BookStack or PostHog run on more platforms?
- BookStack runs on Web, Self-hosted, Docker. PostHog runs on Web, Ios, Android, 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 PostHog is typically brought in for.
- What can BookStack do that PostHog cannot?
- BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. PostHog covers Product analytics, Session recording, Feature flags, A/B testing.
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.
PostHog: What does PostHog's free tier include per month?
PostHog free tier includes: 1M analytics events, 5K session replays, 1M feature flag requests, 100K error tracking exceptions, 1,500 survey responses, 1M data warehouse rows, 10K data pipeline events, 100K AI observability events, 500 PostHog AI credits, 10K workflow messages, and 10GB log ingestion. Source: https://posthog.com/pricing
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.
PostHog: How much data retention does PostHog provide on paid plans?
PostHog free tier provides 1-year data retention. Pay-as-you-go plans offer 7-year data retention across all projects, enabling longer historical analysis. Source: https://posthog.com/pricing
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.
PostHog: What percentage of PostHog users stay on the free tier?
PostHog states that 97% of companies use PostHog for free, indicating extensive free tier adoption. However, specific per-unit pricing rates for overages on paid plans are not published. Source: https://posthog.com/pricing
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.
PostHog: When does PostHog provide priority support on paid plans?
PostHog provides email or Slack support for accounts exceeding $2,000/month on pay-as-you-go plans. Specific response times and support SLAs are not detailed on their pricing page. Source: https://posthog.com/pricing
SourceRelated 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 Mixpanel
- BookStack vs Amplitude
- BookStack vs LaunchDarkly
- BookStack vs Heap
- BookStack vs ClickUp
- BookStack vs Asana
- BookStack vs Figma
- BookStack vs Linear
- BookStack vs GitHub
- BookStack vs LogRocket
- BookStack vs Plane
- BookStack vs Storybook
- BookStack vs Microsoft Edge
- BookStack vs Netlify
- BookStack vs Productboard
- BookStack vs Sentry
- BookStack vs Trino
- BookStack vs Aha!
- PostHog vs Nuclino
- PostHog vs Slab
- PostHog vs MkDocs
- PostHog vs GitBook
- PostHog vs Outline
- PostHog vs Docsify
- PostHog vs HelpDocs
- PostHog vs Read the Docs
- PostHog vs Doxygen
- PostHog vs Guidde
- PostHog vs Sphinx
- PostHog vs Archbee
- PostHog vs Adobe FrameMaker
- PostHog vs Antora
- PostHog vs Bump.sh
- PostHog vs Mixpanel
- PostHog vs Amplitude
- PostHog vs LaunchDarkly
- PostHog vs Heap
- PostHog vs ClickUp
- PostHog vs Asana
- PostHog vs Figma
- PostHog vs Linear
- PostHog vs GitHub
- PostHog vs LogRocket
- PostHog vs Plane
- PostHog vs Storybook
- PostHog vs Microsoft Edge
- PostHog vs Netlify
- PostHog vs Productboard
- PostHog vs Sentry
- PostHog vs Trino
- PostHog vs Aha!
