CasaOS
CasaOS - A simple, easy-to-use, elegant open-source Personal Cloud system.
Runs with mockssource: GitHubhomepageGoApache-2.0commit 0d3b2f444ec0
Go, Apache-2.0 licensed. The project labels itself: casaos, docker, golang, home automation, home cloud, home server, iot and raspberry.
CasaOS runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 8 errors on a clean machine with no GPU, and the whole session was recorded.
CasaOS Go backend compiles and serves API endpoints (200 on /ping, /doc/openapi.yaml, /v1/sys/version/current returning 0.4.15) on a dynamically-assigned local port; UI build cannot complete due to inaccessible private npm packages.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 87 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No Go compiler in container2 minutes
- No gateway service for management address2 minutes
- No yarn package manager1 minute
- UI submodule not checked out1 minute
- go build failed: missing codegen packages1 minute
- URL files had trailing newlines causing panic1 minute
- Install time
- 15 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 8 hit, 6 fixed with no human help
- How the result was proved
- go test ./... ran: 5 package ok, 1 FAIL (TestPorts, empty port list in container); server launched with mock gateway, responded 200 on /ping, /doc/casaos/openapi.yaml, and /v1/sys/version/current (returned '0.4.15')
- Model tokens used
- 113,111
- Exact commit tested
- 0d3b2f444ec0
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
| No yarn in container | Installed via `npm --prefix ~/.npm-global` | | Submodule `UI` not checked out | Cloned from GitHub directly | | `go build` failed: missing codegen | Ran `go generate ./...` | | URL files had trailing newlines → parse panic | Used `printf` instead of `echo` to strip newlines… | `TestPorts` fails (empty port list) | Expected — container has no ports in use | | UI private npm packages 404 | Cannot fix — packages are private to IceWhale | | Gateway service not running | Created mock Python HTTP server | exec /bin/sh -lc 'pkill -f mock_gateway 2>/dev/null; pkill -f "/tmp/casa" 2>/dev/null; sleep 1; echo "do… exited 143 in 0ms: tokens used 113,111
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 15 minutes.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Hit 8 errors during setup, 2 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 87.00 | 0.10 |
Topics (from GitHub)
casaosdockergolanghome-automationhome-cloudhome-serveriotraspberryself-hostedvuejs
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/casaos)Questions
- Does CasaOS run?
- CasaOS runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test CasaOS?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0d3b2f444ec0. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test CasaOS?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does CasaOS take to install?
- 15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does CasaOS need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing CasaOS?
- 8 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for CasaOS?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.