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 13 minutes and hit 1 error on a clean machine with no GPU, and the whole session was recorded.
DevSpace CLI builds, runs (version, help, and all subcommands respond), and 98% of unit tests pass; only the sync package's TestInitialSync fails due to container-level inotify instance limits.
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 86 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.
- TestInitialSync in pkg/devspace/sync fails: "too many open files" from inotify traversal hitting container inotify limit (max_user_instances=128)2 minutes
- Install time
- 13 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 1 hit, 0 fixed with no human help
- Model tokens used
- 75,080
- Exact commit tested
- 8ff6260787ed
- Container image
- sha256:4c3d41857be3
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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/tmp/TestInitialSync2706713302: 001 002 003 cleanup skipped (safe) Small temp artifacts remain. Not a problem for the test report. Now let me compile the final results. The project built successfully from source, the CLI binary ru… 2026-09-03T13:23:26.667916Z ERROR codex_core::session: failed to record rollout items: thread 01a06… tokens used 75,080 Small temp artifacts remain. Not a problem for the test report. Now let me compile the final results. The project built successfully from source, the CLI binary ru…
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 2 times, so the result is not a one-off.
What did not, or is not known
- Took 13 minutes to install, slower than the median of the 24 comparable projects Argusic has measured.
- Hit 1 error during setup, 1 of which were not solved.
Of the 25 cli projects Argusic has installed and timed, devspace was the 21st fastest to reach a running state, and 23 of 25 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.08 | |
| Argusic Runner | 1/3 | Runs | 80.00 | 0.05 |
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 13 minutes, hitting 1 error 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. 2 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.05: 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?
- 13 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?
- 1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
- How does devspace compare with the alternatives?
- Of the 25 cli projects Argusic has installed and timed, devspace was the 21st fastest to reach a running state, and 23 of 25 reached one at all.
- Where is the evidence for devspace?
- 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.