deedglass/deedglass

An agent said it updated 1 row. Postgres changed 301.
Deedglass sits between AI agents and the systems they change. Rules decide each tool call, a check
compares what the system really changed with what the agent reported (Claimed, Checked or Proven;
Matches, Doesn't match or Can't check), and each result is sealed as a signed record anyone can
check offline. It can undo the rows an action changed.
Try it in your browser · Quickstart ·
Docs · Healthcare ·
Benchmarks · Security · deedglass.com
A real run of make demo-hero (commit 97a524c, 2026-10-14), each line shown at the time it printed.
Source: docs/assets/demo-hero.cast.json , recorded by scripts/demo/capture.mjs and drawn by scripts/demo/cast2svg.mjs ( make demo-svg ).
## Install
sh
curl -fsSL https://deedglass.com/install.sh | sh # macOS and Linux: checks the sha256, copies deedglass into ~/.local/bin
npx -y deedglass help # or run it with no install (Node 18 or newer)
npm install -g deedglass # or install it from npm
| Other ways | Command |
| Binaries | archives for macOS, Linux and Windows on the latest release, with checksums.txt |
| Go | go install github.com/deedglass/deedglass/cmd/deedglass@latest (the CLI, without the Console) |
| Docker | build the image from a checkout: make web-build docker (tags deedglass:dev; Node 24 builds the Console) |
The install script downloads the release archive for your platform, checks its sha256 against the
release's checksums.txt (and the signature, when cosign is installed), and copies deedglass into
~/.local/bin; read it first: scripts/install.sh. It downloads from a copy
of the release on deedglass.com and falls back to GitHub: about 7 s on one network in India, where the
GitHub-only install took 81-119 s. A public container image is coming; until it's
published, build the image locally as above. Checksums, signatures and SBOMs:
docs/INSTALL.md.
## Try it in 60 seconds
sh
npx -y deedglass play --fast # the 1-vs-301 scene in your terminal: no Docker, nothing leaves your machine
npx -y deedglass scan # grade what the agents in your MCP configs could change, A to F (read-only)
npx -y deedglass init --yes && npx -y deedglass init --trigger # the same scene, live, on Postgres in Docker
The first two need only Node: together they took 18 s from an empty npm cache on one machine
(2026-10-25). The third starts the real stack in Docker; with the Postgres image already pulled it
is ready in about 7 s, and the first run also downloads Postgres 18.6. The
Quickstart below walks through it.
## Who it's for
Developers with agents on databases. Claude Code, Cursor or your own agent writes to Postgres.
Your rules decide each call first, Postgres's change log shows what really committed, and the
rows one action changed can be undone after a person countersigns. MySQL and other databases can
be checked from a Debezium change feed (docs/WITNESSDEBEZIUM.md).
Health-tech teams and hospitals on FHIR. The FHIR connector (beta) puts a FHIR R4 server
behind Deedglass with SMART Backend Services, reads each write back at the version the server
reported, and checks Proven on HAPI FHIR JPA 8.x and Medplum 5.x running on Postgres. See