ponzu

Headless CMS with automatic JSON API. Featuring auto-HTTPS from Let's Encrypt, HTTP/2 Server Push, and flexible server framework written in Go.

Runssource: GitHubhomepageGoBSD-3-Clausecommit 5c57b559e76b

Go, BSD-3-Clause licensed. The project labels itself: api, cli, cms, golang, http2, json, productivity and server.

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

Ponzu v0.11.0 CLI (ponzu) and server binary build, install, and run in a fresh container using a self-contained Go 1.22.12 + GOPATH vendor layout. The CLI creates projects, generates content types, and builds serving binaries.

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
$2.14 (measured)
recorded runs
2
last tested
stars
5,761
forks
383
open issues
36
watchers
123
size
4 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 ponzu, 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.

  • GOPATH not set; vendor directory incomplete for master branch GOPATH-mode build5 minutes
  • Bleve/vellum/zap/RoaringBitmap transitive dependency chain missing from GOPATH4 minutes
  • Go 1.22+ required but not installed in container2 minutes
  • Generated Person/Blog content types lack Createable/Trustable/Updateable/Deleteable interface methods2 minutes
  • CLI unit tests fail due to GOPATH working-directory mismatch: TestParseType uses os.Getwd() for template path, TestNewName2Path requires test-fixtures directory1 minute
Install time
14 minutes
Cold machine to finish
54 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
go build -o /dev/null ./cmd/ponzu (exit 0); curl -s -o /dev/null -w '%{http_code}' localhost:18120/admin/init returned 200; curl -s -i --max-time 8 -X POST -d multipart localhost:18120/api/content/create?type=Blog returned 200 with JSON data; curl -s http://localhost:18120/api/contents?type=Blog returned 200 with 'data' array; curl -s 'http://localhost:18120/api/search?type=Blog&q=Hello' returned 200 with matching results; curl -sk https://127.0.0.1:10443/admin returned 302 HTTP/2; docs flag serves docs/ at :1235 (200)
Model tokens used
10,781,702
Exact commit tested
5c57b559e76b
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 attempt that decided the verdict above. 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.

echo "build-status=$?"
# Test a fresh "new" flow from the original copy root
echo "=== original-repo-state ==="
cd /work/repo
git diff --stat HEAD | tail -1
git status --porcelain=v1 | grep -v "''^??" | head -3
echo "clean"' in /work/repo
 exited 143 in 0ms:
Now I have all the data. Let me present the final report.
tokens used
10,781,702
Now I have all the data. Let me present the 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.
  • Recovered from all 5 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 BSD-3-Clause, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 14 minutes to install, slower than the median of the 61 comparable projects Argusic has measured.

Of the 62 api projects Argusic has installed and timed, ponzu was the 51st fastest to reach a running state, and 37 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.002.14
Argusic Runner1/3Runs100.000.09

Topics (from GitHub)

apiclicmsgolanghttp2jsonproductivityservertls

Embed the badge

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

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

Questions

Does ponzu run?
Yes. ponzu runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test ponzu?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5c57b559e76b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ponzu?
The run that produced this verdict cost $2.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ponzu take to install?
14 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 ponzu need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ponzu?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does ponzu compare with the alternatives?
Of the 62 api projects Argusic has installed and timed, ponzu was the 51st fastest to reach a running state, and 37 of 62 reached one at all.
Where is the evidence for ponzu?
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