devspace
DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.
Runssource: GitHubhomepageGoApache-2.0commit 8ff6260787ed
Go, Apache-2.0 licensed. The project labels itself: cli, cloud native, container, containerization, dev, developer tool, developer tools and development.
devspace runs. An Argusic agent installed it in 15 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
DevSpace CLI builds from source and all unit tests pass; the binary prints help output correctly and is ready for use with a Kubernetes cluster.
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.3 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.
- go: command not found in container2 minutes
- e2e tests fail because no Kubernetes cluster is available
- Install time
- 15 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 2 hit, 1 fixed with no human help
- How the result was proved
- go test ./... (excluding e2e) exited 0, all packages passed. /work/repo/devspace --help printed usage.
- Model tokens used
- 38,638
- Exact commit tested
- 8ff6260787ed
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec /bin/sh -lc date in /work/repo succeeded in 0ms: Thu Sep 24 22:33:55 UTC 2026 exec /bin/sh -lc 'echo "Start time estimation: started around 22:18. End time: 22:33. Elapsed ~15 minute… succeeded in 0ms: Start time estimation: started around 22:18. End time: 22:33. Elapsed ~15 minutes. Now I'll compile the final result. tokens used 38,638 Now I'll compile the final result.
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
- Reached a running state on a clean machine, with the session recorded.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 15 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.
- Hit 2 errors during setup, 1 of which were not solved.
Of the 124 cli projects Argusic has installed and timed, devspace was the 104th fastest to reach a running state, and 111 of 124 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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
Topics (from GitHub)
clicloud-nativecontainercontainerizationdevdeveloper-tooldeveloper-toolsdevelopmentdevelopment-toolsdevopsdevops-toolsdevspacedevtooldockergolanghelmkanikokubernetesmicroserviceminikube
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/devspace)Questions
- Does devspace run?
- Yes. devspace runs. 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 devspace?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8ff6260787ed. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test devspace?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does devspace 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 devspace need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing devspace?
- 2 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does devspace compare with the alternatives?
- Of the 124 cli projects Argusic has installed and timed, devspace was the 104th fastest to reach a running state, and 111 of 124 reached one at all.
- Where is the evidence for devspace?
- All 3 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.