Softwr

Documentation · head to head

BookStack vs MadCap Flare

BookStack logo

BookStack

Documentation

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

From
Free
Rated
-
Full reviewWebsite
MadCap Flare logo

MadCap Flare

Documentation

Single-source technical authoring tool sold as a per-author annual subscription

From
On request
Rated
-
Full reviewWebsite

The short version

  • Only BookStack has a free tier, so it costs nothing to try first.
  • 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.; MadCap Flare flare is now subscription-only at $3,150 per author per year; a buyer who previously owned a perpetual licence faces an ongoing cost that did not exist under the old purchase model
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, MadCap Flare covers Single-source publishing.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which BookStack and MadCap Flare actually diverge.

Attributes where BookStack and MadCap Flare differ
AttributeBookStackMadCap Flare
Starting priceFreeOn request
Pricing modelOpen source, no licence feePer author per year, annual subscription only
Free tierYesNo
PlatformsWeb, Self-hosted, DockerWindows, Web

Identical on both: user rating (Not yet rated), category (Documentation).

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 MadCap Flare

  • Single-source publishing
  • Conditional text and variables
  • Flare Online cloud authoring
  • Topic-based structure
  • MadCap Central integration

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

MadCap Flare

  • A technical writing team moving off an unsupported or discontinued help authoring tool that needs single-source, multi-format publishingnot BookStack
  • An enterprise documentation team needing conditional content to manage several product editions from one sourcenot BookStack
  • A team wanting a familiar desktop authoring workflow rather than a browser-only or fully structured CCMS environmentnot BookStack
  • A documentation team that needs reviewer seats for subject matter experts without giving them full author licences, available on the Online plansnot 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.

MadCap Flare

  • Flare is now subscription-only at $3,150 per author per year; a buyer who previously owned a perpetual licence faces an ongoing cost that did not exist under the old purchase model
  • A 12-month commitment is required on Flare Online, so a team cannot trial the cloud tier month to month before committing budget
  • Pricing above the Desktop base tier is entirely quote-based for Online plans, so team and business-tier costs are not comparable across vendors without a sales call
  • The authoring model, while less rigid than a full CCMS, still requires writers to learn topic-based structuring, conditional tags and variables, which is a real ramp for staff used to Word or a wiki
  • Storage is capped per tier with paid add-ons in 10 GB increments, so a documentation set with heavy image or video assets can incur additional cost beyond the headline price
  • Windows-only desktop authoring limits teams that standardise on macOS or Linux to the browser-based Flare Online tier, which may not have full feature parity with desktop

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

MadCap Flare

On request
  • Flare Desktop$3150/year
    • On-premises topic-based authoring
    • Unlimited tech support
    • Free introductory training
  • Flare Online (Individual/Team/Business)$undefined/year
    • Cloud authoring plus desktop for each author
    • Reviewer seats and storage scale by tier
    • 12-month commitment required

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 MadCap Flare if

  • You need single-source publishing.
  • You work on Windows, Web.
  • You also want conditional text and variables.
MadCap Flare review

Questions people ask

Is BookStack or MadCap Flare better?
Neither clearly leads. BookStack starts at Free and MadCap Flare at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or MadCap Flare?
BookStack has a free tier; the other does not. Paid plans start at Free for BookStack and On request for MadCap Flare.
Does BookStack or MadCap Flare run on more platforms?
BookStack runs on Web, Self-hosted, Docker. MadCap Flare runs on Windows, Web.
Can I use BookStack for free?
Yes. BookStack has a free tier, so you can try it without paying. MadCap Flare starts at On request.
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 MadCap Flare is typically brought in for.
What can BookStack do that MadCap Flare cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. MadCap Flare covers Single-source publishing, Conditional text and variables, Flare Online cloud authoring, Topic-based structure.

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.

MadCap Flare: Is there still a perpetual licence option?

No, MadCap Flare is sold on an annual subscription basis; the previous perpetual licence model is not offered on current pricing.

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.

MadCap Flare: What is the entry price?

Flare Desktop is $3,150 per author per year; Flare Online plans are quote-only.

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.

MadCap Flare: Is there a minimum commitment?

Flare Online requires a 12-month commitment; Flare Desktop is billed annually.

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 MadCap Flare

Keep looking

Other head to heads