Aegis releases Postgres proxy to intercept dangerous SQL
Understand this story
Aegis has released a Layer-4 Postgres proxy written in Go, deployed between applications and the database, which parses and cuts off connections before destructive statements such as DROP TABLE and unfiltered DELETE reach the database, with no need for applications to change database code. The open-source proxy runs on in-memory state and does not hard-depend on Redis; Redis is used only by the enterprise edition for distributed or high-availability state. The open-source version targets local development and single-node sandbox environments, and four configurations including AEGIS_JWT_SECRET must be set at startup; it exits immediately if the JWT secret is missing. Aegis says those needing production-grade protection for AI agents can contact its enterprise team.
AI overview based on source reports · Updated 15 min ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Hacker News AIShow HN: Aegis – A Layer-4 Postgres proxy in Go to block destructive AI SQL
Aegis is a Go-based Layer-4 proxy that sits between an application and Postgres, parsing every query and terminating the connection when a destructive statement such as DROP TABLE or an unfiltered DELETE is detected, without requiring database code changes. It listens on port 5433 for the Postgres wire protocol and 5434 for an admin/metrics API, and ships with a Python SDK whose @safe_db_run decorator provisions an ephemeral Neon branch and points the connection at the proxy. The open-source tier includes static rate limiting and the blocking mechanism, while ML adaptive throttling, fleet telemetry, eBPF kernel-bypass and custom AST policies are listed for the SaaS and Enterprise tiers.
Activity for this story
Not enough continuous observations to show a trend yet.