Architecture decisions, engineering write-ups, and PostgreSQL performance insights.
An AI agent needs real database access to be useful and real guardrails to be safe. The PostgreSQL wire protocol is the one layer where you can enforce both, for any database, with zero code changes.
Most of PgBeam's 140,000-line codebase was written by AI agents. The setup that makes this work is simpler than you'd expect: a monorepo, a rules file, and a persistent knowledge base.
PgBeam's entire API surface is generated from a single OpenAPI spec: Go server types, route registration, TypeScript SDK, and interactive documentation. Here's how the pipeline works.
How PgBeam's query caching works: L1 process-local cache, optional L2 shared cache, stale-while-revalidate semantics, and cache key computation.
Vercel Functions can deploy to 20 regions. Most teams deploy to one, because their database is in us-east-1. The problem was never compute distribution. It was always the data layer.
The solutions for PostgreSQL latency across regions are either incomplete or locked to a specific platform. Here's why I built something different.