butterbase runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 36 minutes, hitting 4 errors on the way, and recorded the session.

How did Argusic test butterbase?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit b8623ece2ad7. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test butterbase?

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

How long does butterbase take to install?

36 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 butterbase need a GPU?

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

What goes wrong when installing butterbase?

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

Where is the evidence for butterbase?

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.

butterbase

Open-source backend-as-a-service. Postgres, auth, storage, functions, AI gateway, MCP.

Runs with mockssource: GitHubTypeScriptApache-2.0commit b8623ece2ad7

TypeScript, Apache-2.0 licensed. The project labels itself: baas, backend as a service, mcp, open source, postgres, supabase alternative and typescript.

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

pnpm install completed (881 packages), packages/shared, packages/sdk, packages/cli, and services/mcp-server build and test cleanly with Node v22. Control-api builds and its 2643 unit tests pass; 280 fail due to missing Docker infrastructure (Postgres, Redis). CLI binary runs and reports version 0.8.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 56 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 56 / 100
cost of the verifying run: $0.08 (measured)
recorded runs: 2
last tested: 2026-10-03
stars: 3,687
forks: 171
open issues: 12
watchers: 113
size: 11 MB
created: 2026-05-20
last push: 2026-10-01

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-03. 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 butterbase, 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.

npm install fails with 'Cannot set properties of null (setting peer)' - npm 9.2.0 too old for this workspace3 minutes
pnpm blocks build scripts for argon2, bcrypt, esbuild, sharp, workerd2 minutes
crypto.randomUUID undefined in Node v18, breaking quota-enforcer test2 minutes
280 control-api tests fail due to missing Postgres/Redis (no Docker available)

Install time: 36 minutes
Cold machine to finish: 38 minutes
Errors hit and fixed: 4 hit, 4 fixed with no human help
How the result was proved: npm test via vitest: shared 33/33 passed, sdk 193/193 passed, cli 108/108 passed, mcp-server 60/62 passed (2 skipped), control-api 2643/3490 passed (280 failed, mostly ECONNREFUSED Postgres/Redis)
Model tokens used: 274,145
Exact commit tested: b8623ece2ad7
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.

**Build:** `@butterbase/shared`, `@butterbase/sdk`, `@butterbase/cli` all compile cleanly with `tsc…
**Tests (with Node v22.23.3):**
- `packages/shared`: 33/33 passed
- `packages/sdk`: 193/193 passed
- `packages/cli`: 108/108 passed
- `services/mcp-server`: 60/62 passed (2 skipped)
- `services/control-api`: 2643 passed, 280 failed (all failures are `ECONNREFUSED` Postgres/Redis —…
**Issues encountered and fixes applied:**
1. npm 9.2.0 fails with `Cannot set properties of null (setting 'peer')` → used pnpm 12.8.1 instead
2. pnpm blocks native build scripts → added `onlyBuiltDependencies` to `pnpm-workspace.yaml`
3. Node v18 lacks `crypto.randomUUID()` → used Node v22 from npx cache
4. Control-api tests need Postgres/Redis → Docker not available in this container

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 36 minutes.
Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed Apache-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

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

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	Runs with mocks	92.00	0.08	2026-10-03 11:11 UTC
Argusic Runner	1/3	Did not run	20.00	0.17	2026-10-03 10:29 UTC

Topics (from GitHub)

baas backend-as-a-service mcp open-source postgres supabase-alternative typescript

Embed the badge

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

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

Questions

Does butterbase run?: butterbase runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 36 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test butterbase?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit b8623ece2ad7. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test butterbase?: The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does butterbase take to install?: 36 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 butterbase need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing butterbase?: 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for butterbase?: 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.