payload
Payload is the open-source, fullstack Next.js framework, giving you instant backend superpowers. Get a full TypeScript backend and admin panel instantly. Use Payload as a headless CMS or for building powerful applications.
Runssource: GitHubhomepageTypeScriptMITcommit 72ee1751b153
TypeScript, MIT licensed. The project labels itself: cms, content management, content management system, express, graphql, headless, headless cms and jamstack.
payload runs. An Argusic agent installed it in 57 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install succeeds, pnpm run build:core succeeds (45 tasks), unit tests pass 2251/2256 with SQLite integration test passing 12/13 using Node 24.15.0
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 80 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- rollup-plugin-dts resolved to TypeScript 7.0.2 instead of TS6 compatibility layer3 minutes
- Node 18.19.1 did not meet project requirement of >=24.15.03 minutes
- import.meta.dirname not supported in Node 182 minutes
- better-sqlite3 native module failed to load with Node 242 minutes
- pnpm not available globally - EACCES on /usr/local/lib/node_modules1 minute
- rollup bundle:types ran out of memory on Node 18 (FATAL ERROR: Ineffective mark-compacts)1 minute
- Install time
- 57 minutes
- Cold machine to finish
- 58 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- node --max-old-space-size=8192 ./node_modules/vitest/vitest.mjs run --project unit returned Test Files 1 failed | 212 passed | 1 skipped (214), Tests 1 failed | 2251 passed | 4 skipped (2256); PAYLOAD_DATABASE=sqlite node --max-old-space-size=8192 ./node_modules/vitest/vitest.mjs run test/config/int.spec.ts returned Test Files 1 passed (1), Tests 12 passed | 1 skipped (13); Build files verified at packages/{payload,next,db-sqlite}/dist/index.js
- Model tokens used
- 301,440
- Exact commit tested
- 72ee1751b153
- 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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
301,440 Now I have all the data to compile the final result. Here's my report: **Build**: `pnpm install` + `pnpm run build:core` succeeds. Core packages (`payload`, `@payloadcms/… **Fixes applied**: 1. Installed pnpm via `npm config set prefix ~/.npm-global && npm install -g [email protected]` 2. Added `rollup-plugin-dts>typescript` override to fix TypeScript 7 vs 6 resolution for `bundle:ty… 3. Set `NODE_OPTIONS="--max-old-space-size=8192"` for rollup bundle step 4. Patched `bundleWithPayload.js` to use `new URL(".", import.meta.url).pathname` instead of `impor… 5. Installed Node 24.15.0 via `n` package manager 6. Rebuilt `better-sqlite3` native addon with `node-gyp rebuild` 7. Ran vitest directly instead of via `pnpm vitest` to avoid CLI confusion **Verified with**: Unit tests: 212/214 files passed, 2251/2256 tests passed. Integration test (SQLi…
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 57 minutes.
- Recovered from all 7 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 MIT, as reported by its host.
- Measured 5 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.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 3/3 | Runs | 100.00 | 0.30 | |
| Argusic Runner | 2/3 | Runs | 100.00 | 0.11 | |
| Argusic Runner | 1/3 | Did not run | 50.00 | 0.24 | |
| Argusic Runner | 2/3 | Runs | 100.00 | 0.33 | |
| Argusic Runner | 1/3 | Did not run | 50.00 | 0.20 |
Topics (from GitHub)
cmscontent-managementcontent-management-systemexpressgraphqlheadlessheadless-cmsjamstackjavascriptmit-licensemongodbnextjsnodejsopen-sourcepayloadpayloadcmspostgresreacttypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/payload)Questions
- Does payload run?
- Yes. payload runs. Argusic installed and launched it on a clean machine in 57 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test payload?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 72ee1751b153. 5 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test payload?
- The run that produced this verdict cost $0.30: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does payload take to install?
- 57 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 payload need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing payload?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for payload?
- All 5 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.