Yes. gophenberg runs. Argusic installed and launched it on a clean machine in 16 minutes, hitting 6 errors on the way, and recorded the session.

How did Argusic test gophenberg?

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

What did it cost to test gophenberg?

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

How long does gophenberg take to install?

16 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 gophenberg need a GPU?

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

What goes wrong when installing gophenberg?

6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for gophenberg?

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.

gophenberg

A plugin-first CMS. Go backend, React admin, Gutenberg editor.

Runssource: GitHubGoApache-2.0commit a3dc0e85d482

Go, Apache-2.0 licensed. The project labels itself: cms, cms backend, cms framework, content management, content management framework and content management system.

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

Gophenberg 0.19.0 compiles, passes configuration check, serves HTTP 200 on the root page and the content API, and 28 of 32 Go test packages pass with a real PostgreSQL 16 instance stood up from extracted .deb packages, no Docker needed.
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.48 (measured)
recorded runs: 1
last tested: 2026-11-02
stars: 749
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 gophenberg, 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.

Docker not available for PostgreSQL3 minutes
pg_ctl failed: could not create lock file and could not bind IPv62 minutes
Go 1.27.3 compiler not found in PATH1 minute
pnpm not installed and npm install -g failed due to permissions1 minute
initdb failed: libpq.so.5 not found1 minute
psql not found (only server binaries extracted)1 minute

Install time: 16 minutes
Cold machine to finish: 17 minutes
Errors hit and fixed: 6 hit, 6 fixed with no human help
How the result was proved: go build ./cmd/gophenberg exited 0 producing a 37MB binary; ./gophenberg version printed 'gophenberg 0.19.0'; ./gophenberg check exited 0; ./gophenberg serve started on 127.0.0.1:8083 and curl http://127.0.0.1:8083/ returned HTTP 200 (7527 bytes of HTML), curl http://127.0.0.1:8083/api/content/v1 returned HTTP 200 with JSON content API; 28 of 32 test packages passed (4 failures were pre-existing collation/error-code/root-ownership/theme-probe issues)
Model tokens used: 165,423
Exact commit tested: a3dc0e85d482
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.

=== TEST RESULTS ===
28 packages passed, 4 failed (pre-existing):
  - internal/installer: needs root-owned /opt/gophenberg
  - internal/postgres: collation/error-code mismatches
  - internal/themehost: node theme probe timeout
  - internal/app: database-wait password scenario timing
```json
```
tokens used
165,423
```json
```

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 6 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 16 minutes to install, slower than the median of the 27 comparable projects Argusic has measured.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 28 cms projects Argusic has installed and timed, gophenberg was the 17th fastest to reach a running state, and 24 of 28 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	100.00	0.48	2026-11-02 09:40 UTC

Topics (from GitHub)

cms cms-backend cms-framework content-management content-management-framework content-management-system

Embed the badge

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

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

Questions

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