Self-Hosting Platform Comparison

Last Updated: 07.08.2026

Several projects try to make self-hosting easier, but they are not all direct replacements for each other. This comparison should help you find the solution that best fits your use case. We aim to be fair and neutral.

This comparison is based on our current understanding of the projects listed below. Projects change over time, so corrections, updates, and feedback are welcome through the feedback page.

Included projects:

All included projects:

  • are fully open source
  • can be self-hosted without a vendor account
  • do not impose commercial-use limits on self-hosting
  • provide a web interface for administration
  • focus on apps with web interfaces or standard client apps
  • support ARM64, including Raspberry Pi 4 or newer
  • can run apps on ARM when the app packaging supports it

Note: StartOS platform software is open source. Standard StartOS installer images include proprietary firmware / drivers for broader hardware compatibility. Slim FOSS-only images are also available for supported hardware.

Project Positioning

AspectQuollixFreedomBoxYunoHostRuntipiStartOS
LicenseApache 2.0AGPL-3.0AGPL-3.0GPL-3.0MIT
License complexityLow, permissiveHigher, copyleftHigher, copyleftHigher, copyleftLow, permissive
Primary product focusLow-complexity extensible Docker self-hostingPrivacy-focused personal serverDebian-based self-hosting administrationOne-click Docker homeserver appsSovereign personal server OS

Architecture and Installation

AspectQuollixFreedomBoxYunoHostRuntipiStartOS
Installation modelDocker Compose setupDebian Pure Blend; package or image installInstall script on Debian or pre-built imageInstall scriptServer OS image or Start9 hardware
Host modelDocker hostDebian systemDedicated Debian serverDocker hostDedicated server OS
Host managed byAdminPlatformPlatformAdminPlatform

Apps and Extensibility

AspectQuollixFreedomBoxYunoHostRuntipiStartOS
App package formatdocker-compose.yml with conventionsDebian packages and FreedomBox componentsYunoHost app package with manifest, scripts, resources, and config templatesconfig.json plus docker-compose.yml with Runtipi metadataS9PK service package
Custom app integration pathGUI / API upload of Compose YAMLDebian package / Plinth module integrationCustom _ynh app packageCustom app definition or custom app storeSideload .s9pk package
Custom app integration effortLow, Compose uploadHigher, Debian / Plinth integrationHigher, package scriptsMedium, Compose plus metadataMedium to higher, S9PK SDK
App isolation strengthStrongLimitedPartialPartialStrong
App isolation mechanismDocker network / volume isolationDebian / system-level isolationUnix users / ACLs / systemdDocker Compose isolationLXC service isolation
Public third-party publishingPlanned self-service App StoreThrough Debian / FreedomBox contribution processThrough YunoHost app catalog contribution processThrough custom Git-based app storesThrough Start9, community, or custom registries
App update modelAutomated app updates with pre-update backupsAutomatic via Debian packagesWebadmin or CLI app upgradesOne-click app updatesUser-approved service updates
App URL modelDedicated subdomainsApp-dependentSubdomains or subpathsIP / port locally; domains or paths when exposedSame host with service ports, private domains optional
App catalog size8 official apps40+ documented apps600+ apps260+ appsRegistry-dependent

Backups

AspectQuollixFreedomBoxYunoHostRuntipiStartOS
Backup / restore mechanismUniversal volume-based backup / restore; automatic for every appApp-specificApp-specific package scriptsPer-app local archive backup / restoreService-package-defined backup / restore
Remote backup targetSSH serverSSH serverThrough backup appsNoSMB network folder
End-to-end encrypted backupsYesConfigurableThrough backup appsNoYes
Backup typeIncrementalIncrementalThrough backup appsNoDifferential
Backup retention policyPer appNot documentedNoGlobal or per-app maximumNo
Full-server restoreBackup recoveryPartialComplete archive restoreManual archive restoreBackup recovery

Identity and Access

AspectQuollixFreedomBoxYunoHostRuntipiStartOS
Native shared identityYes, OIDC-firstYes, OIDC / LDAPYes, LDAP / SSOwatNoNo
LDAP directoryNoYesYesNoNo
OIDC providerYesYesNoNoNo
OIDC clientYesNoNoNoNo
Cross-instance identity / federationYesNoNoNoNo
Fine-grained access policiesYes, per-app access policies and groupsYes, group-based app accessYes, group and permission based app accessLimited, expose / unexpose apps onlyLimited, service exposure controls only
User onboarding flowInvite token; expiring one-time code; native email deliveryManual account creationManual account creationNo platform usersSingle-user platform; app-specific users

Administration and Operations

AspectQuollixFreedomBoxYunoHostRuntipiStartOS
Certificates without public inbound HTTPYes, DNS-01NoNoYes, Cloudflare DNS-01 via custom TraefikYes, via StartTunnel
HTTP-01 certificates with auto-renewalPlannedYesYesYesYes
App / admin shell accessBrowser terminalBrowser terminalNative CLIHost / CLISSH plus start-cli attach
Hardware resource monitoringPlannedPartialLimited, diagnosis onlyNoYes
App health monitoringPlannedPartialPartialPartialYes
Operational alert notificationsPlannedNoPartial, diagnosis email alertsNoSMTP notifications

Platform-Managed Services

AspectQuollixFreedomBoxYunoHostRuntipiStartOS
Platform-managed mail serverNoYesYesNoNo
Platform-managed VPNNo, host responsibilityOpenVPN / WireGuardNoNo, host or app responsibilityStartTunnel WireGuard, router VPN supported
Dynamic DNSNoYesYesNo, host or app responsibilityNo
Private / relay remote accessNoPageKiteNoManual Cloudflare Tunnel setupStartTunnel
Platform-managed file sharingNo, host responsibilitySambaApp-dependentPartial, shared media directoryApp-dependent

Quollix Differentiators

The most relevant Quollix differentiators in this comparison are:

  • Backup and restore are automatically integrated for all Compose apps, including custom uploaded apps, with per-app retention policies.
  • OIDC is the central identity layer. Quollix can act as both OIDC provider and OIDC client, which enables cross-instance identity and federation.
  • User onboarding is invite-based, with expiring one-time codes and native email delivery.
  • DNS-01 certificate generation is supported, so apps can get certificates without public inbound HTTP access.
  • The planned App Store is intended to support self-service app publishing, where users can register, upload apps, and make them discoverable for others.

Adjacent Projects

The following projects are related to self-hosting, but are not included because they optimize for different use cases:

  • Sandstorm is historically important, but focuses on sandboxed web apps and per-document sharing rather than general server/app administration. Also, the latest tagged release was in 2023.
  • Coolify, CapRover, and Easypanel are closer to self-hosted platform-as-a-service tools. They focus on flexible deployment and lower-level control rather than simple, opinionated end-user self-hosting.
  • SelfPrivacy has a default model for provisioning a rented / cloud NixOS server through supported provider accounts rather than installing a host-local platform on an existing server.
  • TrueNAS and OpenMediaVault are primarily NAS or server operating systems. They can run self-hosted applications, but storage and home-server infrastructure are their main focus.
  • CasaOS is not included because the latest stable platform release was in 2024 and current development appears to have shifted toward ZimaOS.

Excluded Projects

The following projects are not included because they are proprietary, source-available, or do not have a clearly open source project model.

  • Cloudron is source-available under the Cloudron Subscription license.
  • Cosmos is source-available and uses Apache 2.0 with the Commons Clause, which is not open source according to the Commons Clause FAQ.
  • Heroku, Vercel, and Netlify are proprietary hosted platforms.
  • Umbrel is source-available under the PolyForm Noncommercial license.
  • Unraid is proprietary NAS / home-server software.
  • ZimaOS is evolved from CasaOS, but no open source license was found.
Last modified August 7, 2026: add comparison article (02c2067)