spicedb
Open Source, Google Zanzibar-inspired database for scalably storing and querying fine-grained authorization data
Runssource: GitHubhomepageGoApache-2.0commit 9145a33f9a09
Go, Apache-2.0 licensed. The project labels itself: abac, acl, authorization, ciam, cloud native, database, distributed systems and entitlements.
spicedb runs. An Argusic agent installed it in 26 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
SpiceDB built with toolchain go1.27.3, serves an in-memory datastore on :8443, answers healthz 200, accepts schema and relationship writes, and correctly evaluates permission checks (anne has view, zoe does not), with the unit test suites passing except Docker-dependent datastore/e2e tests that cannot run here.
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 90.8 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.
- Full mage test:unit run hung ~16 min in cache-missed internal/services/v1 run under 4-core/768MB container (stream-timeout goroutine)16 minutes
- No Go toolchain in container5 minutes
- README `serve` example flags (--grpc-no-tls/--http-no-tls) and plain-HTTP start not valid for HTTP without TLS certs3 minutes
- Datastore tests fail: rootless Docker not found (sdbtestcontainer, pkg/cmd GC/repair/migrate) and e2e needs cockroach binary2 minutes
- Install time
- 26 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 4 hit, 3 fixed with no human help
- How the result was proved
- curl http://127.0.0.1:8443/healthz returned 200; permission check returned PERMISSIONSHIP_HAS_PERMISSION/NO_PERMISSION; go build ./... exit 0; go test ./cmd/... ./internal/... and ./pkg/... = 105 packages ok
- Model tokens used
- 224,067
- Exact commit tested
- 9145a33f9a09
- 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.
- `curl` to `http://127.0.0.1:8443/healthz` returned `200`. - `POST /v1/schema/write` returned HTTP `200` with a `writtenAt` token. - `POST /v1/relationships/write` returned HTTP `200` with a `writtenAt` token. - `POST /v1/permissions/check` returned `PERMISSIONSHIP_HAS_PERMISSION` for `anne` on `folder:budge… **Tests** - `go test ./cmd/... ./internal/...`: 54 packages `ok`. - `go test ./pkg/...`: 51 packages `ok`. - `go test ./internal/services/v1` rerun separately: `ok` in 19.9s (the full `mage test:unit` run h… - `go run mage.go -l` works; the documented `mage test:unit` flow exists but aggregates the whole m… **Unfixable gaps (no Docker, no root)** - `pkg/testutil/sdbtestcontainer` and `pkg/cmd` datastore tests fail with `get provider: rootless D… - `e2e/newenemy` needs a `cockroach` binary.
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 26 minutes.
- Ran without a GPU, so it does not need one to start.
- 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
- Hit 4 errors during setup, 1 of which were not solved.
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)
abacaclauthorizationciamcloud-nativedatabasedistributed-systemsentitlementsfgafine-grained-access-controlfine-grained-authorizationkubernetespermissionsrbacrebacsecuritysecurity-toolszanzibar
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/spicedb)Questions
- Does spicedb run?
- Yes. spicedb runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test spicedb?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9145a33f9a09. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test spicedb?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does spicedb take to install?
- 26 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 spicedb need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing spicedb?
- 4 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.
- Where is the evidence for spicedb?
- 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.