BookStack vs FileMaker

What BookStack is

BookStack is an MIT-licensed, self-hosted documentation application built around shelves, books, optional chapters and pages. It provides role and content-level permissions, multiple enterprise authentication options and a permission-aware REST API, but the operator remains responsible for the PHP and database stack, upgrades, filesystem permissions, security configuration and complete database-plus-file backups.

What FileMaker is

Claris FileMaker is a licensed low-code platform for creating custom data applications and delivering them through desktop, iPhone, iPad and web clients. Teams choose Claris-managed FileMaker Cloud, self-managed FileMaker Server or qualifying third-party hosting; user ranges, hosted-app count, storage, API transfer, plug-ins and operational responsibility vary by option and tier.

What BookStack is built to do

Book hierarchy

Organizes page content within optional chapters, books and reusable bookshelves.

Roles and permissions

Combines system roles with content-level overrides and inherited controls.

Federated authentication

Documents OIDC, SAML 2.0 and LDAP configuration for self-hosted instances.

REST API

Provides token-authenticated JSON endpoints governed by the API user's permissions.

What FileMaker is built to do

Custom app builder

Builds data-centric workflows with layouts, scripts, calculations and access controls.

Cloud or Server hosting

Deploys through Claris-managed infrastructure or customer-controlled FileMaker Server.

Mobile and web access

Uses FileMaker Go on iPhone and iPad and WebDirect for supported browsers.

REST data interfaces

Exposes hosted data and administrative operations through supported APIs and OData.

Choose BookStack if

• Internal handbooks, runbooks and technical knowledge bases with a clear hierarchy
• Organizations needing self-hosting, role controls and supported identity integrations
• Teams that can automate upgrades, database and file backups, and restore drills

Skip BookStack if

• You need a vendor-operated SaaS with no infrastructure responsibility
• Your information model cannot fit shelves, books, chapters and pages
• You cannot preserve the database, uploads, configuration and original APP_KEY together

Choose FileMaker if

• Business workflows needing a tailored data application rather than an off-the-shelf SaaS process
• Teams choosing explicitly between managed Cloud simplicity and Server infrastructure control
• Deployments whose users, apps, storage and API transfer fit the selected license

Skip FileMaker if

• Required plug-ins must run in FileMaker Cloud
• Expected app, storage or API-transfer usage exceeds the acceptable tier or purchase agreement
• You need an open-source application stack without named-user licensing

BookStack: pros & cons

• Predictable structure: Shelves, books, chapters and pages give teams a constrained documentation hierarchy.
• Granular access: Roles can be combined and overridden at shelf, book, chapter or page level.
• Authentication choices: Official administration docs cover OpenID Connect, SAML 2.0 and LDAP.
• Automation surface: The REST API covers content and administrative resources while enforcing the API user's roles and permissions.
• Self-hosting burden: PHP, MySQL or MariaDB, web-server configuration, updates and monitoring are operator responsibilities.
• Manual recovery design: There is no built-in full backup and restore; both database records and instance files must be protected.
• Key dependency: Restores need the original APP_KEY for encrypted features such as multi-factor credentials.
• Hierarchy trade-off: The book metaphor is approachable but may constrain teams needing free-form graphs or complex publishing workflows.

FileMaker: pros & cons

• Integrated app builder: Combines data, layouts, scripts, permissions and application logic.
• Multiple clients: FileMaker Pro, FileMaker Go and WebDirect cover desktop, supported Apple mobile devices and browsers.
• Hosting choice: Offers Claris-managed Cloud, customer-managed Server and third-party hosting paths.
• Data interfaces: FileMaker Data API, OData and Admin API cover supported data and administration use cases.
• Layered licensing: User count, hosting option and selected tier shape cost and entitlements.
• Cloud quotas: Current tiers document hosted-app, storage, active-flow, web-view and outbound API-transfer limits.
• Cloud plug-in boundary: Claris states that FileMaker Cloud does not support plug-ins, while Server and third-party hosting can.
• Self-hosting work: FileMaker Server makes the customer responsible for hardware, operating system, updates, performance and infrastructure practices.