velero
Backup and migrate Kubernetes applications and their persistent volumes
Runs with mockssource: GitHubhomepageGoApache-2.0commit 8e9f66addf63
Go, Apache-2.0 licensed. The project labels itself: backup, disaster recovery, hacktoberfest, kubernetes and velero.
velero runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Velero binary builds and reports its version (client-only). 96 of 97 test packages pass; the controller test suite is skipped because the kubebuilder envtest binaries (kube-apiserver, etcd, kubectl) are not available at /usr/local/kubebuilder/bin/.
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.
- Controller test suite requires kubebuilder envtest binaries (etcd, kube-apiserver, kubectl) at /usr/local/kubebuilder/bin/5 minutes
- Go 1.26 compiler not installed on the system3 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- make local produced binary at _output/bin/linux/amd64/velero (150 MB); velero version --client-only returned 'Version: main, Git commit: 8e9f66addf6355d7f504f18d27b2841a3b2b8120'; test suite ran 96 packages passing, 1 package failing (pkg/controller due to kubebuilder binaries not available)
- Model tokens used
- 114,022
- Exact commit tested
- 8e9f66addf63
- 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.
/bin/sh -lc "# Collect precise timing
echo \"Started at:\" ; stat -c '%Y' /work/repo/Makefile 2>/dev/null | xargs -I {} date -d @{} 2>/de…
echo \"Now:\" ; date +%s" in /work/repo
succeeded in 0ms:
Started at:
Wed Nov 4 14:38:27 UTC 2026
Now:
1793804057
I have all the information needed for the final report.
tokens used
114,022
I have all the information needed for the final report.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
- Recovered from all 2 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.
- Took 15 minutes to install, slower than the median of the 47 comparable projects Argusic has measured.
Of the 48 backup projects Argusic has installed and timed, velero was the 41st fastest to reach a running state, and 32 of 48 reached one at all.
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.26 | |
| Argusic Runner | 1/3 | Runs with mocks | 82.00 | 0.13 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/velero)Questions
- Does velero run?
- velero runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test velero?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8e9f66addf63. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test velero?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does velero 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 velero need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing velero?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does velero compare with the alternatives?
- Of the 48 backup projects Argusic has installed and timed, velero was the 41st fastest to reach a running state, and 32 of 48 reached one at all.
- Where is the evidence for velero?
- 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.