BookStack vs Uno Platform

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 Uno Platform is

Uno Platform is an Apache-2.0-licensed .NET UI framework for building applications from a shared C# and XAML or C# Markup codebase across Windows, Android, iOS, WebAssembly, macOS and Linux. Its open-source runtime is complemented by account-based Studio tooling such as Hot Reload and Hot Design. Actual target coverage depends on the development host, IDE, .NET workloads, platform SDKs and renderer, so single-codebase does not mean identical tooling or behavior everywhere.

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

Shared .NET UI

Uses C# with XAML or C# Markup to share application and interface code across targets.

WebAssembly target

Runs supported .NET UI applications in modern desktop and mobile browsers.

Skia desktop

Targets desktop environments on Windows, macOS and supported Linux configurations.

Studio tooling

Adds account-based Hot Reload and Hot Design workflows where the compatibility matrix permits.

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 Uno Platform if

• C# teams extending WinUI-style skills beyond Windows
• Products whose required hosts and targets appear in the supported environment matrix
• Applications that can test and tune each platform rather than assume pixel-identical behavior

Skip Uno Platform if

• A required target or debugging workflow is unsupported from the team's development hosts
• The product depends heavily on native controls or APIs not proven through Uno abstractions
• You cannot maintain platform SDKs, .NET workloads and target-specific QA

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.

Uno Platform: pros & cons

• Broad target matrix: One .NET solution can target Windows, Android, iOS, browsers, macOS and Linux.
• Familiar Microsoft UI model: C#, XAML and WinUI-aligned APIs reduce conceptual switching for .NET UI teams.
• Open-source core: The Uno repository is available under Apache License 2.0.
• Multiple IDE choices: Official setup paths cover Visual Studio, VS Code and JetBrains Rider.
• Host-dependent targets: iOS requires a current Mac/Xcode path, while WinAppSDK development is unavailable from macOS and Linux hosts.
• Compatibility matrix: IDE, host OS, target, .NET version and renderer combinations do not all offer the same build or debugging support.
• Upgrade work: Migration notes include removed target frameworks, tooling updates and platform-specific API changes.
• Studio boundaries: Hot Design requires sign-in, supported project versions and XAML; it excludes C# Markup and currently has target limitations.