AppVeyor vs BookStack

What AppVeyor is

AppVeyor is a hosted continuous-integration service with YAML or UI build configuration, build matrices, hosted workers and bring-your-own-cloud workers. Its public free tier is scoped to open-source projects; private-project allowances, concurrent jobs and self-hosted job capacity vary by paid plan.

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 AppVeyor is built to do

YAML or UI configuration

Defines the pipeline in appveyor.yml or through project settings, with documented precedence rules.

Build matrix

Expands selected environment dimensions into separate build jobs.

Build workers

Runs jobs on hosted environments or qualifying self-hosted and BYOC capacity.

Secure variables

Encrypts secret values for YAML and restricts their default use in pull-request builds.

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.

Choose AppVeyor if

• Open-source projects that fit the public-project free tier and one hosted concurrent job
• Teams expressing multi-environment builds through a repository YAML file
• Organizations combining hosted CI control with their own worker infrastructure

Skip AppVeyor if

• A private project must remain on a free hosted plan
• Required concurrent or self-hosted capacity exceeds the acceptable subscription cost
• Your scripts cannot be hardened to fail reliably and keep secrets out of logs

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

AppVeyor: pros & cons

• Repository configuration: Builds can be defined in appveyor.yml and carried with the source repository.
• Build matrices: Creates jobs across selected operating systems, platforms, configurations and environment variables.
• Hosted and self-hosted execution: Pricing documents Windows, Linux and macOS options plus BYOC workers.
• Secret variables: Account-specific encryption supports protected values in visible YAML files.
• Narrow free scope: The listed free plan is for unlimited public open-source projects, not private repositories.
• Concurrency queue: Jobs beyond the plan's concurrent-job allowance wait for capacity.
• Plan limits: Private projects, concurrent hosted jobs and simultaneous self-hosted jobs differ by tier.
• Script error handling: AppVeyor warns that PowerShell non-terminating errors can leave a build reported as successful unless configured to stop.

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.