BackYA 
GR
Replying to @liberzon
pgblame — CI guards your code and ignores your database. pgblame watches
Postgres query performance across deploys, so you see which deploy slowed a
query. $19/mo, real free tier. Looking for 2 design-partner beta users.
Backstory: I've had plenty of Postgres pain over the years, but the thing
that always nagged me wasn't one incident — it's that CI guards your code and
goes silent on your database. Deploys ship; nobody's watching whether they
slowed a query.
So I built the tool I wanted: pgblame. A tiny read-only Docker agent
snapshots pg_stat_statements every 60s, ingests your Vercel/Railway/GitHub-
Actions deploy webhooks, and shows "this query went 40ms → 800ms right after
this deploy." Same shape as Lantern but not Rails-only; ~1/8 the price of
pganalyze ($19/mo, real free tier). The agent runs in your env, read-only,
never sees your data, MIT-licensed.
It's live at pgblame.com but I haven't launched publicly yet — I want
2 founders running Postgres in prod (Supabase/Neon/RDS + Vercel/Railway,
shipping often) as design partners: 20-min call, you set it up while I watch,
brutally honest feedback, free Pro forever. Who's in?
pgblame.com
pgblame — which deploy slowed your Postgres?
A Docker sidecar that snapshots pg_stat_statements and ties query regressions to your Vercel/Railway deploys. $19/mo, free tier.
Love this — "CI guards your code and ignores your database" is such a sharp way to frame the gap. Tying query regressions directly to deploys is the kind of thing that should've existed years ago. $19/mo with a free tier is a great price point too — makes it an easy "just try it" decision. Following along, curious to see how the Supabase/Neon/RDS support holds up in the wild.