Yes. backend runs. Argusic installed and launched it on a clean machine in 19 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test backend?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9e3cb4a66007. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test backend?

The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does backend take to install?

19 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 backend need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing backend?

3 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.

Where is the evidence for backend?

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.

backend

Prod Forge is an open-source reference that shows how to build and operate a production-ready system: AI-assisted development, quality gates, CI/CD, infrastructure, observability, migrations, and rollback.

Runssource: GitHubTypeScriptMITcommit 9e3cb4a66007

TypeScript, MIT licensed. The project labels itself: api, architecture, architecture api, aws, backend, ci cd, clean architecture and deployment.

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

The NestJS Todo API builds, launches, and serves all API endpoints (auth, todos, version, health, metrics, swagger) backed by PostgreSQL and Redis, with all 483 unit tests passing.
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 93.3 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 93.3 / 100
cost of the verifying run: $0.18 (measured)
recorded runs: 1
last tested: 2026-11-05
stars: 523
forks: 0
open issues: 0
watchers: 0
created: -
last push: -

Subject data from GitHub, linked at the top of this page. 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 backend, 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.

No Docker, PostgreSQL, or Redis available in container6 minutes
E2E tests (testcontainers) cannot run without Docker daemon3 minutes
Node.js v18.19.1 too old (requires 24+); Prisma 7.10.1 blocked install1 minute

Install time: 19 minutes
Cold machine to finish: 22 minutes
Errors hit and fixed: 3 hit, 2 fixed with no human help
How the result was proved: npm test exited 0, 483 passed; app started on :3000, curl /health returned 200 with database+shutdown up, /api/version returned 200 with version 1.0.0, /api/v1/auth/login returned 200 with JWT token, /api/v1/todos GET returned 200 with 7 seeded todos, /api/v1/todos POST returned 201, /health/deps returned 200 with database+redis up, /metrics returned 200, /docs returned 200
Model tokens used: 368,775
Exact commit tested: 9e3cb4a66007
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.

echo "1. Node v18 -> Node v24 (downloaded prebuilt binary)"
echo "2. No Docker -> manual PostgreSQL + Redis from binaries"' in /work/repo
 succeeded in 0ms:
Install complete. Final state summary...
Errors encountered and fixed:
1. Node v18 -> Node v24 (downloaded prebuilt binary)
2. No Docker -> manual PostgreSQL + Redis from binaries
Now let me compile the final report.
Here is my final report:
tokens used
368,775
Here is my 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

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 MIT, as reported by its host.

What did not, or is not known

Took 19 minutes to install, slower than the median of the 61 comparable projects Argusic has measured.
Hit 3 errors during setup, 1 of which were not solved.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 62 api projects Argusic has installed and timed, backend was the 56th fastest to reach a running state, and 36 of 62 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	1/3	Runs	93.33	0.18	2026-11-05 08:48 UTC

Topics (from GitHub)

api architecture architecture-api aws backend ci-cd clean-architecture deployment docker grafana nestjs nodejs observability postgresql prisma production-ready prometheus redis rest-api typescript

Embed the badge

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

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

Questions

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