Deedglass

[Deedglass (Deed Glass)]

Deedglass (Deed Glass)

Check what your AI agents actually changed.

An agent said it updated 1 row. Postgres changed 301.

Safety for AI agents that work on databases and health records. Rules decide each AI agent tool call;
Deedglass checks what really changed and seals a record. Open source, self-hosted, every feature free.

[CI] [Release] [npm] [Licence: Apache-2.0, with ee/ under FSL-1.1-ALv2] [Go reference] [Attack suite]

Start in one command

npx -y deedglass

An app opens in your browser. It runs on your own computer, signed in, with no account, no sign-up and no Docker or database to set up, and nothing is sent to us. Choose who will use it (a clinic, hospital IT, or people building with AI), then connect Claude Desktop, Cursor, VS Code, a record system or a database. You need Node 18 or newer. Read Start here for a short tour, or try it without installing anything at deedglass.com/play.

For developers, three commands:

npx -y deedglass start      # an agent reports 1 row, Postgres changed 301, and it's caughtnpx -y deedglass protect    # guard Claude Code, Cursor and other coding agentsnpx -y deedglass help       # the eight everyday commands; "help all" lists every command

Without Docker, start plays the same scene inside the binary, every line labelled live or replay, in under 30 s. More: Quickstart · Docs · Policy Generator · Healthcare · Benchmarks · Security · deedglass.com

Found it useful? A star helps other people find Deedglass. To hear about new releases, use Watch › Custom › Releases.

What it does

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.

[Terminal recording of a real make demo-hero run. Order 42 ships: Proven, Matches, 1 row. A legacy trigger is turned on and the same UPDATE runs: Proven, Doesn't match, Postgres changed 301 rows in public.orders, the agent reported 1, with the row diff. Then every record verifies offline.]

_{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

curl -fsSL https://deedglass.com/install.sh | sh   # macOS and Linux: checks the sha256, copies deedglass into ~/.local/binnpx -y deedglass help                              # or run it with no install (Node 18 or newer)npm install -g deedglass                           # or install it from npm

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.

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/WITNESS_DEBEZIUM.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 deedglass.com/healthcare and the FHIR benchmark. To see it on synthetic data first, with no Docker and no server, run npx deedglass health pilot (the 15-minute hospital pilot).
• Security teams. Lockdown makes every agent write wait for a person, needs two people for high-risk writes and for turning lockdown off, and keeps each agent to one connector (docs/LOCKDOWN.md). Records are signed and anyone can check them offline with deedglass verify.

Project status

• Pre-1.0. Every release is in CHANGELOG.md and on the releases page. The deed format is a versioned public spec (spec/), so old records keep verifying.
• One maintainer. Deedglass is built by Arjun Prabhakaran in India (GOVERNANCE.md). Replies are best effort (SUPPORT.md).
• Free and self-hosted. Every feature is free while we grow, including ee/, and it runs on your machines with your own Postgres. Nothing checks a licence and nothing is sent to deedglass.com (Security).
• Not yet: no SOC 2 report, no outside penetration test and no SSO. Known limits are in docs/LIMITATIONS.md and KNOWN_ISSUES.md.

How it works

flowchart LR  A["AI agent<br/>Claude · OpenAI · Cursor · any MCP client"] -->|tool call + agent key| R  subgraph D["Deedglass · one binary + Postgres"]    R["1 · Rules<br/>allow · deny · ask a person"] --> X["2 · Run<br/>with credentials from the vault"]    X --> C["3 · Check<br/>what really changed"] --> S["4 · Seal<br/>a signed record"]  end  X --> T["Tools<br/>Postgres · FHIR · GitHub · Slack · Stripe · MCP servers"]  T -->|change log or read-back| C  S --> U["Undo<br/>Postgres rows, after a person countersigns"]  H[People] -->|approve · stop| R

Every tool call passes through Deedglass with the agent's key. Your rules (policies) decide allow, deny or require_approval; Deedglass runs the call with credentials the agent never holds; the check compares what happened with what was asked; and the outcome is sealed as a record in the org's chain.

How sure each check is

Each record claims one level and one result: Matches, Doesn't match or Can't check. When Deedglass can't tell whether a tool ran, the result is Can't check, never Matches. The API keeps the short names (L0/L1/L2, VERIFIED/MISMATCH/UNVERIFIABLE); the glossary maps them.

The 301-row scene

What an agent reports is not always what the system stored, and a log the agent writes itself can't show the difference. An agent was asked to mark order 42 as shipped. It ran one UPDATE and its tool reported 1 row. A legacy trigger shipped 300 more orders in the same transaction. This is the real output of the Quickstart's last step on 2026-10-14 (shortened where you see …):

$ npx -y deedglass init --trigger…✕ UPDATE order 42         Proven · Doesn't match · Postgres changed 301 rows in public.orders. The agent reported 1.  expected   UPDATE 1 row in public.orders where id = 42 · sets status  observed   UPDATE 301 rows in public.orders · 300 outside id = 42…✓ Trigger off             orders_ship_open_batch dropped✓ Undo preview            Undo available · 301 rows in public.orders · 301 updates    policy   undo-needs-approval · a person countersigns first

The agent's log says 1 row. Deedglass read Postgres's own change log for that transaction, found 301, sealed the difference as a record, and planned an undo from those rows that runs only after a person countersigns.

Quickstart

Docker running with about 2 GiB of free disk, Node 18 or newer, and macOS or Linux, then (from the tested Quickstart). On Windows, npx deedglass runs the native Windows binary, no WSL needed; deedglass init uses Docker on macOS and Linux, so on Windows start with npx deedglass app, which needs no Docker:

mkdir acme-agents && cd acme-agentsnpx -y deedglass init --yesnpx -y deedglass doctornpx -y deedglass init --trigger

deedglass init starts two Postgres 18.6 containers in Docker (Deedglass's own database and a demo database), runs deedglass serve on 127.0.0.1:8080, creates an org, an agent and the postgres-check policy (reads and writes run, every write is checked at Proven, DROP and TRUNCATE never run; use postgres-safe in production, where writes wait for a person), and ends with a blocked DROP TABLE and an UPDATE checked at Proven. deedglass doctor runs seventeen read-only checks, each with its fix. deedglass init --trigger turns on the demo database's legacy trigger, sends the same one-row UPDATE, and ends on the 301-row mismatch and the undo preview shown above. Its last line is the undo run command; the undo waits for a person, and undo run prints the approve link.

Port 8080 or 55432 taken? npx -y deedglass init --yes --listen 127.0.0.1:8090 --pg-port 55440 (--listen is where deedglass serve listens; --pg-port is Deedglass's own Postgres, and the demo database takes the port 10 above it). Every later command run in that directory finds the ports in .deedglass/stack.json. npx -y deedglass init --purge removes the containers, the volumes and the files in .deedglass/ when you're done.

Protect every agent in one command: npx deedglass protect adds the shell guard to Claude Code, Cursor, Codex CLI, Gemini CLI and GitHub Copilot CLI, so a command such as railway volume delete, supabase db reset --linked or terraform destroy waits for your yes (Codex and Gemini CLI deny it instead). It backs up each file first and --undo puts them back: a second check, not a sandbox (docs/protect.md).

Then put your own Postgres behind it (Supabase, Neon or any Postgres 16 to 18): npx -y deedglass connect "$DATABASE_URL" runs read-only checks and prints a plan; --apply sets it up (guide).

Four ways in

When a scan finds a trigger or a cascade on a table your agent can write, it says so and points to the 301 scene. Observe mode is below.

Observe mode: nothing to rewire

deedglass observe run --connector pg-demo -- ./agent.sh   # open a watched session, run the agent, close itdeedglass observe show obs_01k… --undo-sql                # the undo as SQL you review and run (free)deedglass observe run --connector dev --undo-sql ~/deedglass-undo -- claude   # watch a Claude Code session, shell included

Turn it on with witness.observe.enabled: true in the connector's config. Observe mode reads only Postgres's change log, through the role and replication slot that deedglass connector postgres init creates, so it works beside any gate you already use, or none. It shows every row committed on the watched tables while the session was open and seals the session as a record. It can't tell which program wrote a row, so a session gets no Matches or Doesn't match verdict; row images are kept 30 days; a TRUNCATE can't be undone from the record. Undo SQL is free, and so is a one-step undo through Deedglass: every feature is free while we grow. Details: docs/OBSERVE.md.

Add it to your agent client

[Add to Cursor] Install in VS Code · LM Studio · Goose · Claude Desktop · Every client

claude mcp add --scope user deedglass -- npx -y deedglass mcp serve

No link holds a key. Run npx deedglass init first; each client asks Deedglass for the key it wrote.

Claude Code plugin (the MCP server, the /deedglass:scan, /deedglass:wrap and /deedglass:watch commands, and skills for reading a scan and for giving an agent Postgres access safely), from this repo's own marketplace:

/plugin marketplace add deedglass/deedglass/plugin install deedglass@deedglass

Every format, with its source: docs/INSTALL_CLIENTS.md.

SDKs and clients

• TypeScript: @deedglass/sdk, with adapters for the AI SDK, the OpenAI Agents SDK, LangChain and the Claude Agent SDK.
• Python: deedglass, with LangChain and Claude Agent SDK adapters. It isn't on PyPI yet; install it from this repo or from a release's wheel (docs/SDK_PYTHON.md).
• Go: github.com/deedglass/deedglass/pkg/deedglass.
• MCP: deedglass mcp wrap governs any stdio MCP server; deedglass mcp serve governs remote ones for Claude Desktop, Claude Code, Cursor, VS Code and Windsurf.

Connectors

Postgres (Proven), REST, GitHub, Slack, Stripe (test mode only), Gmail drafts, Notion and remote MCP servers. Credentials live in an encrypted vault; every outbound call goes through one egress door. See docs/CONNECTORS.md.

Benchmarks

Each benchmark publishes what Deedglass misses next to what it catches.

Every scenario, with the misses named: corpus/BENCHMARK.md, corpus/fhir/BENCHMARK.md and deedglass.com/benchmark.

Speed:

How they were measured, and the misses: docs/BENCHMARKS.md.

What it doesn't do

• Proven checks cover Postgres only, and need wal_level=logical and REPLICA IDENTITY FULL on watched tables.
• A hijacked agent with a valid key and an in-policy action is allowed. Policies, budgets and approvals narrow this; they don't close it.
• Deedglass trusts the Postgres server, its superusers, the host it runs on and its seal key. It can't protect you from a compromised host.
• Records hold digests, not payloads. One set of seal keys signs every org on an instance.
• It doesn't replace a least-privilege database role. Use both: the role limits what the agent can do; Deedglass checks what it did with that.

The whole list, with workarounds: docs/LIMITATIONS.md and KNOWN_ISSUES.md.

Alternatives

You may not need Deedglass, or you may want it next to one of these. Each has a longer page, with sources and the date each was checked, at deedglass.com/compare.

Security

The attack suite runs 82 cases against a real server and real Postgres on every release candidate: 82 matched, 0 differ (attack/results/latest.json, docs/ATTACK_SUITE.md). Another 23 library- and CLI-level cases (groups Y and T: crypto agility, the A2A proxy, the Debezium witness, the shell guard, timestamps) run with go test ./attack on every pull request. Report a vulnerability privately: SECURITY.md.

Every feature is free while we grow, so nothing checks a licence and nothing is sent to deedglass.com: the scan reads files on your machine and, with --postgres-dsn-env, connects only to the database you name. The deedglass licence commands, kept for a later paid option, are the only ones that call Dodo Payments or deedglass.com, and only when you run them; DEEDGLASS_NO_NETWORK=1 stops those calls. deedglass version --check and the --latest option of deedglass policy install and policy packs contact GitHub when you use them. Head timestamps are off by default; with TSAs or a transparency service listed in deedglass.yaml, deedglass deeds timestamp and each export contact only those. How the licence path works if a later build asks for a key: docs/LICENSING.md.

Docs and links

• Docs: docs.deedglass.com · Quickstart · how it works · docs/
• Agent clients: Claude Code · Cursor, VS Code and Windsurf · Claude Desktop · your own Postgres
• Frameworks: Vercel AI SDK · Claude Agent SDK · OpenAI Agents SDK · LangChain · Mastra · Pydantic AI · Google ADK · CrewAI · LlamaIndex
• Healthcare: deedglass.com/healthcare · FHIR connector · PHI mode · Medplum example · FHIR benchmark · Hospital pilot · IT review pack
• GitHub Action: Deedglass Scan on the GitHub Marketplace
• Security: SECURITY.md · lockdown · attack suite · limitations · verifying records
• Contributing: CONTRIBUTING.md · good first issues · Discussions

Contributing

Read CONTRIBUTING.md: make dev, make ci, the tests a change needs, and DCO sign-off (git commit -s). Questions go to Discussions (SUPPORT.md); how decisions are made is in GOVERNANCE.md.

If Deedglass showed you something your logs didn't, a GitHub star helps other people find it.

License

The core, the SDKs and the CLI are Apache-2.0. The features in ee/ are FSL-1.1-ALv2 (free to use while we grow), and each release of them becomes Apache-2.0 two years after it ships. The release binary, the @deedglass/cli-* npm packages and the container image include ee/, so their licence is Apache-2.0 AND FSL-1.1-ALv2.

FSL-1.1-ALv2 lets you read, run and change ee/ for anything except offering a competing product (ee/LICENSE); everything Deedglass does for safety is free and outside ee/ (docs/LICENSING.md). The rest is LICENSE; third-party notices are in NOTICE. Forks are welcome under a new name: TRADEMARKS.md.

The record spec (spec/: the deed format and the export bundle) and the intent-vs-effect corpus (corpus/) are published under CC-BY-4.0, so anyone can implement, copy or adapt them with credit.

In plain words (a summary, not legal advice; the licence files govern):