Softwr

Documentation · head to head

BookStack vs Refact

BookStack logo

BookStack

Documentation

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

From
Free
Rated
-
Full reviewWebsite
Refact logo

Refact

Developer Tools

Autonomous AI coding agent for development tasks

From
Free
Rated
-
Full reviewWebsite

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.; Refact requires configuration for optimal performance
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, Refact covers Autonomous agent workflows.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which BookStack and Refact actually diverge.

Attributes where BookStack and Refact differ
AttributeBookStackRefact
Pricing modelOpen source, no licence feeFreemium with paid tiers
PlatformsWeb, Self-hosted, DockerVS Code, Web
CategoryDocumentationDeveloper Tools
FoundedUnknown2023

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 Refact

  • Autonomous agent workflows
  • IDE chat
  • Real-time code completions
  • GitHub integration
  • Database integration
  • On-premise deployment
  • Multi-LLM support
  • 25+ language 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 Refact
  • Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot Refact
  • Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot Refact
  • Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot Refact

Refact

  • Autonomous code generation for development tasksnot BookStack
  • End-to-end bug fixes and refactoringnot BookStack
  • Multi-language software development accelerationnot BookStack
  • Enterprise development with data privacy requirementsnot 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.

Refact

  • Requires configuration for optimal performance
  • On-premise deployment adds operational complexity
  • Free tier limited by daily agent request quota
  • Coin system adds complexity to cost calculation

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

Refact

Free
  • FreeFree
    • Limited daily agent usage
    • Unlimited completions
    • 2,000 coins for agent and chat
  • Pro$10/month
    • 40 daily agent requests
    • 64k context window
    • 10,000 coins monthly
  • Enterprise$undefined/custom
    • On-premise deployment
    • Custom coin allocation
    • Fine-tuning 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.
BookStack review

Choose Refact if

  • You need autonomous agent workflows.
  • You want to start without paying.
  • You work on VS Code, Web.
  • You also want ide chat.
Refact review

Questions people ask

Is BookStack or Refact better?
Neither clearly leads. BookStack starts at Free and Refact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or Refact?
BookStack starts at Free and Refact at Free.
Does BookStack or Refact run on more platforms?
BookStack runs on Web, Self-hosted, Docker. Refact runs on VS Code, Web.
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 Refact is typically brought in for.
What can BookStack do that Refact cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Refact covers Autonomous agent workflows, IDE chat, Real-time code completions, GitHub integration.

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.

Refact: How many programming languages does Refact support?

Refact supports 25+ programming languages including Python, JavaScript, Go, Rust, Java, C++, and many others.

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.

Refact: Can I deploy Refact on-premises?

Yes. Refact offers on-premise deployment options for organizations requiring complete data control and privacy.

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.

Refact: What LLMs does Refact support?

Refact works with multiple LLMs including Claude, GPT-4, and open-source models, giving you flexibility in model selection.

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

More on BookStack

More on Refact

Keep looking

Other head to heads