grafbase
[Acquired by The Guild] The Grafbase GraphQL Federation Gateway
Runssource: GitHubhomepageRustMPL-2.0commit b8223903090f
Rust, MPL-2.0 licensed. The project labels itself: ai, api, enterprise graphql, federation, graphql, graphql federation, mcp and model context protocol.
grafbase runs. An Argusic agent installed it in 12 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Grafbase gateway (v0.53.5) and CLI (v0.105.2) compiled from source; gateway serves GraphQL endpoint on localhost and passes 1364 of 1384 integration tests, with all 19 failures from missing external Docker containers, mTLS cert snapshots, and insta loop assertion limits.
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.
- CLI build script panic: missing assets/cli-app.tar.gz0.3 minutes
- Rust toolchain not installed0.2 minutes
- Integration tests failed: 19 failures in graphql_over_http, subscriptions, mtls
- Install time
- 12 minutes
- Cold machine to finish
- 64 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cargo test -p integration-tests --test integration_tests gateway:: --no-fail-fast: 1364 passed, 19 failed (pre-existing environmental failures). Gateway binary served HTTP 200 on /graphql and returned {"status":"healthy"} on /health. CLI binary --version returned 'Grafbase CLI 0.105.2'.
- Model tokens used
- 198,559
- Exact commit tested
- b8223903090f
- 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.
compilation terminated. error: could not compile `engine` (lib test) due to 1 previous error Let me now compile my complete findings. Here's a summary of what happened: **Install**: Rust toolchain 1.90.0 installed from scratch. Both `grafbase-gateway` and `grafbase` (… **Launch**: The gateway was launched with a minimal schema and config, serving HTTP 200 on `/graphq… **Tests**: 1364 integration tests passed, 19 failed (all environmental — Docker containers not runn… tokens used 198,559 Let me now compile my complete findings. Here's a summary of what happened: **Install**: Rust toolchain 1.90.0 installed from scratch. Both `grafbase-gateway` and `grafbase` (… **Launch**: The gateway was launched with a minimal schema and config, serving HTTP 200 on `/graphq… **Tests**: 1364 integration tests passed, 19 failed (all environmental — Docker containers not runn…
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 MPL-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
Of the 237 ai projects Argusic has installed and timed, grafbase was the 180th fastest to reach a running state, and 168 of 237 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 | 2/3 | Ran out of time | 0.00 | 0.36 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.22 |
Topics (from GitHub)
aiapienterprise-graphqlfederationgraphqlgraphql-federationmcpmodel-context-protocolrustwebassembly
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/grafbase)Questions
- Does grafbase run?
- Yes. grafbase runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test grafbase?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b8223903090f. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test grafbase?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does grafbase take to install?
- 12 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 grafbase need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing grafbase?
- 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 grafbase compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, grafbase was the 180th fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for grafbase?
- 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.