keystatic
First class CMS experience, TypeScript API, Markdown & YAML/JSON based, no DB
Runssource: GitHubhomepageTypeScriptMITcommit c51af99a27ad
TypeScript, MIT licensed. The project labels itself: cms, content management system, javascript, json, markdoc, markdown, static content and typescript.
keystatic runs. An Argusic agent installed it in 40 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 1288 tests pass (1251 passed, 37 skipped, 0 failures) across both the @keystatic/core and @keystar/ui packages using Node 24.12.0 and pnpm 11.20.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 100 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.
- Postinstall script fails on Node 18 - .mts file extension not recognized15 minutes
- rolldown linux-x64-gnu native binding missing (optional dependency not installed)5 minutes
- pnpm not found - needed to install dependencies2 minutes
- Install time
- 40 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npx vitest run --reporter=junit returned tests=1288 failures=0 errors=0 across 146 test files. keystatic project: 57 files, 702 passed, 8 skipped. keystar/ui project: 89 files, 549 passed, 29 skipped.
- Model tokens used
- 98,151
- Exact commit tested
- c51af99a27ad
- 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.
98,151 All 1288 tests passed with 0 failures. Let me summarize the results. **Errors encountered:** 1. **pnpm not found** — Node 18.19.1 came with npm but not pnpm. Installed pnpm 11.20.0 via `npm in… 2. **`.mts` files unsupported on Node 18** — The postinstall script runs `node design-system/pkg/bu… 3. **rolldown native binding missing** — `@rolldown/[email protected]` is an optional dep… **Verification:** - `npx vitest run --reporter=junit` produced a JUnit report with `tests="1288" failures="0" errors=… - The `keystatic` project: 57 test files, 702 passed, 8 skipped. - The `keystar/ui` project: 89 test files, 549 passed, 29 skipped. - Combined: 146 test files, 1251 passed, 37 skipped, 0 failures, 0 errors. **Time spent:** roughly 40 minutes from start to finish.
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 3 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 2 times, so the result is not a one-off.
What did not, or is not known
- Took 40 minutes to install, slower than the median of the 28 comparable projects Argusic has measured.
Of the 29 cms projects Argusic has installed and timed, keystatic was the 28th fastest to reach a running state, and 25 of 29 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
Topics (from GitHub)
cmscontent-management-systemjavascriptjsonmarkdocmarkdownstatic-contenttypescriptyaml
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/keystatic)Questions
- Does keystatic run?
- Yes. keystatic runs. Argusic installed and launched it on a clean machine in 40 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test keystatic?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c51af99a27ad. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test keystatic?
- The run that produced this verdict cost $0.25: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does keystatic take to install?
- 40 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 keystatic need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing keystatic?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does keystatic compare with the alternatives?
- Of the 29 cms projects Argusic has installed and timed, keystatic was the 28th fastest to reach a running state, and 25 of 29 reached one at all.
- Where is the evidence for keystatic?
- 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.