- Who it helps
- Developers evaluating controls around automated changes to databases and services.
- Availability
- The site describes a self-hosted Apache-2.0 core and free features during its current growth phase. The browser app is labelled version 0.15.0.
Separate permission from outcome
Its recorded database demonstration permits a one-row update, then detects that a trigger changed 301 rows. The displayed counts are replayed from the maker’s recorded run. Undo is a separate write requiring approval.
Verification depends on the connection
The product distinguishes an agent’s claim from a result read from a connected system. If it cannot read the result, it reports that it cannot check. The maker says its attack suite has not had an outside penetration test.
What you can do
- Read the connector limits before testing with disposable data. Open reference ↗
Where the evidence stops
Documentation and recorded example read; no database connected or demonstration executed. Rollback reliability, security and production suitability remain independently unverified.
Sources read. Primary documentation read November 2, 2026 UTC. No software installed, model inference run or full workflow executed.
Sources & further reading
Web · official
Deedglass compares an agent’s report with actual changes ↗
Identifies the subject, documented capability or specific verification limit.
Arjun Prabhakaran / Deedglass · page checked 2026-11-02
Coverage note: Independent attention and end-to-end execution remain unverified.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
- · Added to Current
Deedglass puts rules around agent tool calls, then checks connected systems for what actually changed and records the result.