BookStack Hosting

How BookStack works

BookStack models information after a physical library. Shelves group related books, books contain chapters or pages, and chapters provide an optional layer for keeping longer manuals understandable. Authors write the actual content on pages, so readers can move from a broad subject to a precise procedure without navigating a loose collection of files.

Search is available across the installation and within individual books or chapters. Teams can also use tags to describe content from different angles, while content-level permissions let administrators control access at shelf, book, chapter, or page level. That combination makes the structure useful for both public references and private departmental knowledge.

Key BookStack features

The editor is designed for people who need to document work rather than learn a complex publishing system. A page can hold instructions, explanations, screenshots, and linked material, while the hierarchy keeps related pages together. Sorting and moving content helps the library adapt as a process grows or ownership changes.

Permissions are role-based and can be overridden for specific content. This supports cases where most documentation is shared but finance, infrastructure, or management material needs a narrower audience. Export and import tools also provide a route for moving selected books, chapters, or pages between compatible installations.

BookStack vs Confluence

BookStack presents documentation through a fixed shelves-and-books model and keeps the interface centred on writing, reading, search, and permissions. Confluence is a connected workspace for team knowledge, documentation, and collaboration within the wider Atlassian ecosystem.

Confluence may be the stronger choice for organisations that want Atlassian-hosted cloud plans, close Jira integration, and a large Marketplace integration ecosystem. BookStack is more attractive when the priority is a self-hosted documentation library with a direct information hierarchy and fewer surrounding workspace concepts.

Who uses BookStack

IT teams use BookStack for runbooks, service notes, and recovery procedures. Operations groups can maintain standard processes and onboarding guides, while product teams can publish internal specifications or customer instructions. Small organisations also use it as a central handbook when shared folders have become difficult to search and govern.

The platform is especially suitable when readers need predictable navigation. It is less suited to organisations that want documentation to behave like a spreadsheet, database, or whiteboard, because its strength comes from the book-based structure rather than an open-ended workspace.

Self-hosting BookStack: requirements and cost

BookStack resource use is mainly shaped by active readers and editors, stored page content, attachments, and search activity. The catalogue stack includes MariaDB, which stores users, permissions, page records, and related application data alongside the persistent BookStack files. The recommended plan accounts for both the application and its MariaDB container.

On AvaHost, the software itself is free to run and the recommended minimum is Plan 2 at €5. One-click deployment provisions BookStack and a MariaDB container, while the database remains unmanaged by AvaHost. Automatic application updates and scheduled backups are included. Teams expecting heavy concurrent editing or a large attachment archive should review usage after launch and move to a larger plan when needed.