devopness

Devopness: AI DevOps on your cloud. Deploy apps, infra and CI/CD. Any cloud and any stack, one MCP. Deterministic API, opinionated and fully configurable. No cloud credentials in AI chats.

Runssource: GitHubhomepageTypeScriptApache-2.0commit aec616919c31

TypeScript, Apache-2.0 licensed. The project labels itself: aws, azure, ci cd, cloud infrastructure, deployment, deployment automation, devops and devops tools.

devopness runs. An Argusic agent installed it in 11 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All three SDK packages install, build, and pass their test suites: Python SDK 86/86 tests, JavaScript SDK 29/29 tests plus clean TypeScript compilation, UI React 403/403 tests.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
581
forks
182
open issues
13
watchers
3
size
26 MB
created
last push

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.

Time lost to each failure while testing devopness, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node.js v18.19.1 is too old (SDK requires ^20.19.0 || ^22.13.0 || >=24)5 minutes
  • Python pip install blocked by PEP 668 OS package protection3 minutes
  • Java not found, cannot run openapi-generator-cli for JS SDK build
Install time
11 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
Python: 'python3 -m unittest discover -s tests -v' → 86 passed, 0 failed. JS SDK: 'npm test' → 7 files, 29 passed. 'vp check' → 0 errors. 'tsc' → silent. UI React: 'npm test' → 57 files, 403 passed.
Model tokens used
193,185
Exact commit tested
aec616919c31
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

tokens used
193,185
All packages work — here's the summary:
**Python SDK** — 86 tests pass. Client import and instantiation verified.
**JavaScript SDK** — 29 tests pass. Lint clean (0 errors). TypeScript compiles. Full build needs Ja…
**UI React** — 403 tests pass.
**Errors encountered:**
| Error | Fix | Duration |
|-------|-----|----------|
| Node.js v18 too old (needs >=20) | Downloaded & used Node v22.14.0 binary | ~5 min |
| Python pip blocked (PEP 668) | Created venv, installed poetry there | ~3 min |
| Java not found (JS SDK build only) | Not fixable — no root, no Java in container; generated model…

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.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Took 11 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 12 aws projects Argusic has installed and timed, devopness was the 10th fastest to reach a running state, and 10 of 12 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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

awsazureci-cdcloud-infrastructuredeploymentdeployment-automationdevopsdevops-toolsdigitaloceangoogle-cloudheroku-alternativehetznermcpmodel-context-protocolmulti-cloud-environmentsself-hostingserver-managementterraform-alternativevercel-alternativezero-downtime-deploy

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/devopness.svg)](https://argusic.com/subject/devopness)

Questions

Does devopness run?
Yes. devopness runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test devopness?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit aec616919c31. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test devopness?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does devopness take to install?
11 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 devopness need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing devopness?
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.
How does devopness compare with the alternatives?
Of the 12 aws projects Argusic has installed and timed, devopness was the 10th fastest to reach a running state, and 10 of 12 reached one at all.
Where is the evidence for devopness?
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.

Discussion