cloudburn

Open-source policy engine that blocks bad AWS spending patterns before they ship and remediates what's already burning.

Runssource: GitHubhomepageTypeScriptApache-2.0commit a4fcdc0504ec

TypeScript, Apache-2.0 licensed. The project labels itself: amazon web services, aws, cloud, command line tool, cost management, cost optimization, devops and devops tools.

cloudburn runs. An Argusic agent installed it in 0.3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Full monorepo builds, lints, typechecks, and all 1,883 tests pass across all 5 packages (cloudburn CLI, @cloudburn/action, @cloudburn/mcp, @cloudburn/sdk, @cloudburn/rules). The CLI binary runs and correctly scans Terraform IaC for cost violations.

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.04 (measured)
recorded runs
2
last tested
stars
1,802
forks
369
open issues
57
watchers
43
size
7 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.

Install time
under a minute
Cold machine to finish
4 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
pnpm exec turbo run test test:e2e across all 5 packages: rules (522 passed), sdk (1151 passed), cli (102 passed, 1 skipped), action (23 unit + 12 e2e passed), mcp (6 unit + 19 e2e passed). docs:test (14 passed), release:test (18 passed), docs:check passed, boundaries passed, lint passed, typecheck passed. CLI version (0.18.6) reported. CLI scan against a Terraform fixture returned a correct finding for CLDBRN-AWS-EBS-1.
Model tokens used
93,462
Exact commit tested
a4fcdc0504ec
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.

@cloudburn/sdk:test:       Tests  1151 passed (1151)
@cloudburn/sdk:test:    Start at  13:17:04
@cloudburn/sdk:test:    Duration  120.92s (tests 86%, import 12%, transform 2%)
@cloudburn/sdk:test:
 Tasks:    1 successful, 1 total
Cached:    1 cached, 1 total
  Time:    26ms >>> FULL TURBO
Here is the complete result:
2026-11-13T13:19:55.596674Z ERROR codex_core::session: failed to record rollout items: thread 01a1d…
tokens used
93,462
Here is the complete 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.
  • Installed in 0.3 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • 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 it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 0.3 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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 Runner2/3Runs100.000.04
Argusic Runner1/3Runs100.000.04

Topics (from GitHub)

amazon-web-servicesawscloudcommand-line-toolcost-managementcost-optimizationdevopsdevops-toolsfinopshomebrewnpm-package

Embed the badge

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

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

Questions

Does cloudburn run?
Yes. cloudburn runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test cloudburn?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit a4fcdc0504ec. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test cloudburn?
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 cloudburn take to install?
0.3 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 cloudburn need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing cloudburn?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for cloudburn?
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.

Discussion