// the take
pgbot is a single static Go binary that connects read-only to Postgres's own statistics views and prints a findings-first health report, with local baselines so repeat runs show what changed. It's aimed at anyone who wants a fast diagnostic without standing up a monitoring stack — someone triaging a database they don't own, a CI pipeline gating migration PRs, or an AI agent that needs structured Postgres findings over MCP.
The read-only guarantee is enforced at the role level (pg_monitor, no write grants) with session-level defense in depth (statement_timeout, lock_timeout, BEGIN READ ONLY) rather than just a flag you have to trust. Findings are computed deterministically in Go from SQL and kept separate from the optional AI layer, which only explains and prioritizes — it can't invent a finding that isn't there, which is the right trust boundary for this kind of tool. The --json output is a versioned, documented schema treated as a real interface (separate from the human-readable text, which is explicitly allowed to change), so scripts and the MCP server have something stable to build on. Provider-specific footguns (Neon's pooler suffix and scale-to-zero cold window, Supabase's :6543 transaction pooler, RDS's CloudWatch-only host metrics) are called out directly instead of glossed over.
It's explicitly beta, and the README admits the JSON contract has already moved to 1.5.0 — anyone building automation on --json needs to track schema changes on an interface that hasn't stabilized yet. Several commands (logs, waits) and all of Aurora multi-instance support are marked experimental, so the feature surface is wider than what's actually hardened. The query-level findings (top queries, tuning) depend on pg_stat_statements, an extension a lot of managed providers don't enable by default, so the single most useful diagnostic signal is opt-in and easy to be missing without realizing it. It's a point-in-time tool by design — no persistent history beyond a local baseline store, no alerting, no multi-host rollup — so anyone who actually needs retention or paging has to run pganalyze/PMM/pgwatch alongside it rather than instead of it.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →