Deedglass and Claw Patrol
Claw Patrol gates each agent action at the wire before it reaches the system.1 Deedglass also checks what Postgres committed afterwards, seals a record anyone can check, and can undo the rows.
The short answer
- Both put rules between an agent and the systems it touches, and both can pause an action until a person approves it.1
- Claw Patrol reads Postgres, ClickHouse, Kubernetes and HTTP traffic at the wire and decides before the action runs.1
- Deedglass decides before the call too, then reads Postgres's own change log to check what was committed, and records the result as a signed record.
When to choose Claw Patrol
- Your agents talk to ClickHouse, Kubernetes or plain HTTP services as well as Postgres, and you want one firewall in front of all of them.1
- You want rules in HCL with CEL conditions over the parsed traffic, kept in one config file.1
- You want to route whole hosts or single process trees through a gateway over WireGuard or Tailscale.1
- You want an MIT-licensed tool.1
When Deedglass fits
- The question after the call matters to you: did Postgres commit what the agent said it would? Triggers and cascades can turn one statement into hundreds of changed rows, and the check reports that as Doesn't match.
- You need a record of each action that someone outside your team can check offline, without trusting you or the agent.
- You want to undo the rows an agent changed, not only stop the next call.
Side by side
| Question | Claw Patrol | Deedglass |
|---|---|---|
| Decides before the call | Yes: gates each action against rules over the parsed traffic1 | Yes: rules decide each tool call before it runs |
| Asks a person before risky actions | Yes: can pause an action until a person approves it1 | Yes: approval in Slack, email or the Console |
| Checks what Postgres committed | Not described in its README (checked 13 October 2026)1 | Yes: reads Postgres's change log and compares it with the claim |
| Signed record of each action, checkable offline | Not described in its README (checked 13 October 2026)1 | Yes: every action is sealed into a hash-linked chain |
| Undoes rows | Not described in its README (checked 13 October 2026)1 | Yes, with checks before each undo |
| Runs as | A single binary; clients join over WireGuard or Tailscale1 | A single binary next to your agent (the cloud beta is on a waitlist) |
| Licence | MIT1 | Apache-2.0 core |
| Price (checked 13 October 2026) | Not stated in its README1 | Free self-host · Pro $49 a month |
Use them together
They can sit in a row. If Claw Patrol already gates your agent's Postgres traffic, Deedglass's change-log reader still sees every commit on the database. Changes that didn't come through Deedglass's own rules show up as unattributed, so you can see them without moving your gate.
What Deedglass doesn't do
- It doesn't parse ClickHouse, Kubernetes or arbitrary HTTP traffic at the wire; its checks after the call cover Postgres.
- It doesn't stop a trigger or a cascade from running. It shows what Postgres committed, so a person can act on it.
- It doesn't replace database permissions. Give the agent the narrowest role first.
Sources
- 1denoland/clawpatrol, README · github.com · checked 13 October 2026
Last checked 13 October 2026. We re-check these pages every month. If something is out of date, write to hello@deedglass.com.
Try it on your own setup
npx deedglass scanGrades only your own setup. Nothing is uploaded.