hatamoto

Hatamoto: a fast, secure, self-hosted CMS in Go, with signed WebAssembly plugins and auto-updates

Runs with mockssource: GitHubGoApache-2.0commit 7b741ab6020f

Go, Apache-2.0 licensed. The project labels itself: cms, go, golang, headless cms, mcp, postgres, self hosted and seo.

hatamoto runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.4 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The Go project builds into a 73MB hatamoto binary, all unit tests pass, and the binary prints version and help text correctly.

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

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.14 (measured)
recorded runs
1
last tested
stars
316
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.

What went wrong, in the agent's own words

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

  • PostgreSQL not available in container (no docker, no psql)
Install time
under a minute
Cold machine to finish
44 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
go build succeeded, hatamoto version printed dev commit, go test ./... (excluding integration tests requiring Postgres) with HATAMOTO_PERF_STRICT=0 passed all 90+ packages on the final run
Model tokens used
82,730
Exact commit tested
7b741ab6020f
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

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

Now I have complete data. Let me produce my final report.
Here's the complete summary:
**Build**: `go build -o bin/hatamoto ./cmd/hatamoto` → succeeded, 73MB binary at `backend/bin/hatam…
**Binary verification**: `hatamoto version` → `hatamoto dev (commit 7b741ab6020fde4d71b03e93719bea9…
**Go vet**: passed (clean)
**Unit tests**: With `HATAMOTO_PERF_STRICT=0` (the project's accepted env var for noisy/shared host…
- All packages pass: `./internal/...`, `./web/...`, `./app/...`, `./migrations/...`, `./tools/...`,…
- SDK module: `hatamoto.dev/sdk`, `hatamoto.dev/sdk/guest`, `hatamoto.dev/sdk/registry` all pass
- 2 known flaky tests (`TestRenderPageP50` in `pluginhost`, one analytics race) that are timing-sen…
**What didn't work**: Postgres is not available in this container, so:
- Integration tests (tagged `integration`) are skipped — they require `DATABASE_URL` pointing to a …
- `hatamoto serve` cannot start without a database

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

  • Installed in 0.4 minutes, faster than the median of the 29 comparable projects Argusic has measured.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 30 cms projects Argusic has installed and timed, hatamoto was the 2nd fastest to reach a running state, and 25 of 30 reached one at all.

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/3Runs with mocks92.000.14

Topics (from GitHub)

cmsgogolangheadless-cmsmcppostgresself-hostedseowasmwebassemblywordpress-alternative

Embed the badge

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

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

Questions

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