Softwr

Documentation · head to head

BookStack vs Obsidian

BookStack logo

BookStack

Documentation

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

From
Free
Rated
-
Obsidian logo

Obsidian

Research

A powerful knowledge base on top of a local folder of plain text Markdown files

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.; Obsidian sync is a paid add-on at $4 per month billed annually rather than part of the app
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, Obsidian covers Bidirectional linking.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which BookStack and Obsidian actually diverge.

Attributes where BookStack and Obsidian differ
AttributeBookStackObsidian
Pricing modelOpen source, no licence feeUnknown
PlatformsWeb, Self-hosted, DockerWeb, Windows, macOS, Linux, iOS, Android
CategoryDocumentationResearch
FoundedUnknown2020

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 Obsidian

  • Bidirectional linking
  • Graph view visualization
  • Markdown support
  • Local file storage
  • Plugin ecosystem
  • Custom CSS themes
  • Templates
  • Search and tags

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

Obsidian

  • Local-first markdown note taking with no account requirednot BookStack
  • Linking notes into a personal knowledge graphnot BookStack
  • Syncing a vault across devices with end-to-end encryption on the paid add-onnot BookStack
  • Publishing a public site from a vaultnot BookStack
  • Extending the editor with community pluginsnot 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.

Obsidian

  • Sync is a paid add-on at $4 per month billed annually rather than part of the app
  • Publishing to the web is a further $8 per month per site
  • Commercial use asks for a $50 per user per year licence, though the vendor states it is not required
  • Collaboration is limited compared with a hosted notes tool, since the vault is local files first

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

Obsidian

Free
  • Obsidian Sync$4/month
    • Sync notes across devices
  • Obsidian Publish$8/month
    • Turn notes into a website

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

  • You need bidirectional linking.
  • You want to start without paying.
  • You work on Web, Windows, macOS, Linux, iOS, Android.
  • You also want graph view visualization.

Questions people ask

Is BookStack or Obsidian better?
Neither clearly leads. BookStack starts at Free and Obsidian at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or Obsidian?
BookStack starts at Free and Obsidian at Free.
Does BookStack or Obsidian run on more platforms?
BookStack runs on Web, Self-hosted, Docker. Obsidian runs on Web, Windows, macOS, Linux, iOS, Android.
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 Obsidian is typically brought in for.
What can BookStack do that Obsidian cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Obsidian covers Bidirectional linking, Graph view visualization, Markdown support, Local file storage.

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.

Obsidian: Is Obsidian free?

Yes. The core Obsidian application is 100% free for personal and commercial use with no limitations. You can use unlimited vaults and every core feature without payment.

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.

Obsidian: What file format does Obsidian use?

Obsidian stores every note as a plain Markdown file. Because it uses standard Markdown instead of a proprietary format, your notes remain portable and can be edited with many other Markdown editors.

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.

Obsidian: Can I collaborate with others in Obsidian?

The core application does not include built-in team collaboration features. However, Obsidian offers optional add-ons and can be used with version control systems or cloud storage for collaboration.

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