CasaOS
Simple, easy-to-use home cloud system and dashboard
CasaOS is a community-based open-source home cloud operating system and dashboard built on Docker. It provides an elegant app store and dashboard for managing self-hosted applications.
Key features
- Elegant app store
- Drag-and-drop dashboard
- File management
- Docker app management
Pros & cons
Strengths
- Very beginner-friendly
- Polished interface
Trade-offs
- Best on dedicated hardware
- Less control than raw Docker
CasaOS replaces
Last reviewed Aug 26, 2026 · 745 words
If you have a spare mini PC, have never typed docker compose up, and want Jellyfin and Nextcloud running by tonight, CasaOS is the fastest honest path I know. It installs onto a plain Debian or Ubuntu in about 2 minutes with one command, gives you an app store where installs are a single click, and its dashboard looks like something a designer touched. The trade you make is control: CasaOS wants to own Docker, port 80 and the way apps are described, and the day you want something it did not anticipate, you will be working around it rather than with it. 37,138 stars and an Apache-2.0 licence say a lot of people are happy with that trade.
It is a layer, not an operating system
Despite the name, CasaOS does not replace your OS. The install script (curl -fsSL https://get.casaos.io | sudo bash) adds Docker if missing, a Go daemon, and a web gateway that claims port 80 on the host. Everything you install through it is an ordinary Docker container you can see with docker ps. That is the good news: nothing is hidden and nothing is proprietary. The awkward news is the port. If you already run a reverse proxy on 80 and 443, install CasaOS on a fresh machine or change its gateway port in the settings before the two collide. The 512 MB RAM floor is for CasaOS itself; each app adds its own. It runs on amd64 and arm64, so a Raspberry Pi 4 with 4 GB is a legitimate host for a handful of light apps, though a used mini PC is the better buy for anything involving media.
The app store is a curated compose library
Every store entry is a Docker Compose file with CasaOS metadata, so "install" means pull the image, create volumes under /DATA/AppData/{app}, and start. The official store is deliberately small and vetted; the community sources (BigBearCasaOS is the one most people add) cover hundreds more. You can also import any compose file through Custom Install, which is the escape hatch that keeps CasaOS from being a toy. What you cannot do easily is the fiddly stuff: shared Docker networks between apps, non-standard volume layouts, or environment changes the store's form did not expose.
Files, storage and the things it is not
CasaOS ships a file manager and basic disk management: mount a drive, merge several into one pool, share over SMB. That covers a home NAS at the "family photos on a USB disk" level. It is not a RAID manager, not ZFS, and not a backup tool; treat those as separate jobs. It is also not a monitoring tool. The dashboard shows CPU and RAM, and that is where it stops, so install Uptime Kuma from the store on day one.
Where people outgrow it
The pattern I see repeatedly: month 1 delight, month 6 friction. The friction is always the same three things. First, updating apps through the UI works until an image changes its config format, at which point you need the compose file anyway. Second, backups of /DATA/AppData are your problem and the UI does not remind you. Third, the moment you want a second machine or a proper reverse proxy with automatic certificates, CasaOS has no opinion and you are back to hand-written compose, which the homelab compose patterns post covers. Runtipi sits in the same beginner tier with a stricter, more reproducible app format; if you already know Docker, skip both and put Homepage in front of your own stack.
Uninstalling cleanly
There is a casaos-uninstall command that removes the daemon and gateway but leaves your containers and /DATA alone. That is the right behaviour: graduating out of CasaOS costs you nothing but the dashboard, because every app was a normal container all along.
What I'd do
For a first server, yes: fresh Debian, the install script, add the BigBear store source, and install apps from the store for a month. Keep /DATA/AppData in a nightly backup from the first day. When the store form stops exposing the setting you need, that is your cue to open the generated compose file, learn what it does, and start managing that app by hand. CasaOS is the best on-ramp in the dashboards category precisely because it does not lock the exit.
Compare CasaOS
7 head-to-head comparisons.
Similar dashboards & startpages apps
Portainer CE
Dashboards & StartpagesLightweight management UI for Docker and Kubernetes
Replaces Rancher, Docker Desktop
Glance
Dashboards & StartpagesSelf-hosted feeds and info dashboard
Replaces Heimdall
Web Check
Dashboards & StartpagesAll-in-one OSINT tool for analysing any website
Homepage
Dashboards & StartpagesFast, file-configured application dashboard
Replaces Heimdall
Dashy
Dashboards & StartpagesFeature-rich personal dashboard for self-hosters
Replaces Heimdall
Dockge
Dashboards & StartpagesFancy, reactive, self-hosted Docker Compose stack manager
Replaces Portainer