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 10 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
CasaOS v0.4.15 backend builds successfully, launches as an HTTP server listening on a random port, responds with HTTP 200 on GET /, and 6 of 7 standalone unit test files pass.
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 89.5 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.
- Gateway and message-bus external services unreachable at startup3 minutes
- Go (Golang) compiler not installed in container2 minutes
- Codegen packages missing (codegen/casaos_api.go and codegen/message_bus/api.go)2 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- go build -o casa main.go succeeded (31MB binary), ./casa -v returned 'v0.4.15', server started and answered HTTP 200 on GET /, 7 unit test files exercised (health, db, samba, ip, file, network_detection, other tests), 6 pass, 1 skips flaky subtests, only service/file_test.go cannot compile standalone due to a main.go global dependency
- Model tokens used
- 135,337
- 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.
echo "---" # And verify the version again export GOPATH=/tmp/gopath GOROOT=/tmp/golang-install/usr/lib/go-1.21 PATH=$GOROOT/bin:$GOPATH/bin:$… cd /work/repo && ./casa -v' in /work/repo succeeded in 0ms: -rwxrwxr-x 1 runner runner 31618834 Nov 2 01:41 /work/repo/casa v0.4.15 exec /bin/sh -lc 'kill $(pgrep -f '"'mock_gateway\\|mock_messagebus\\|casa') 2>/dev/null; true" in /work… succeeded in 0ms: tokens used 135,337
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 10 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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.
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 | 2/3 | Runs with mocks | 92.00 | 0.28 | |
| 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 10 minutes, hitting 3 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. 2 attempts are 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.28: 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?
- 10 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?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for CasaOS?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.