▲ pgblame
Log inStart free
BACKED BY PG_STAT_STATEMENTS

Which deploy
slowed your
Postgres?

A Docker agent snapshots pg_stat_statements every minute and ties query regressions to your Vercel and Railway deploys. When something gets slow, you get the commit that did it.

▷ Start free5-min setup
since last deploy · 14 minutes agopgblame ▸ live
SELECT id FROM messages WHERE thread_id = $1 ORDER BY created_at DESC LIMIT 5012ms280ms↑23×
SELECT count(*) FROM users WHERE active = true3ms3ms—
INSERT INTO events (kind, payload) VALUES ($1, $2)2ms2ms—
└ vercel · main · 0bf42c9 · "index on messages(thread_id, created_at)"
$ pgblame agent ▸ sampling pg_stat_statements every 60s
Works with
Supabase
Neon
Vercel
Railway
GitHub Actions
03 · How it works

Three steps.
Five minutes.

No agents to deploy. No code changes. No language SDK. Just a Docker container next to your Postgres and a webhook from your CI.

  1. ◇ Step 01
    Run the agent
    $ docker run -d \
  -e PGBLAME_DATABASE_URL=… \
  -e PGBLAME_TOKEN=pgb_… \
  ghcr.io/liberzon/\
    pgblame-agent:latest
    25 MB image · static Go binary · read-only role
  2. ◇ Step 02
    Wire your deploy webhook

    Vercel and Railway are two clicks. GitHub Actions or any other CI is a one-line curl.

    Pre-built integrations · or POST to /v1/deploy
  3. ◇ Step 03
    Open the dashboard

    Every query that got slower (or faster) since the deploy, with the commit and author. Email and Slack alerts on regressions.

    30-day history on Pro · 7 days on free
04 · Honest comparison

Use the right
tool. Maybe not us.

Lantern is great if you're on Rails. pganalyze is great if you have a budget. We built pgblame for the gap between them — language-agnostic, deploy-aware, $19/mo.

ToolPriceDeploy correlationHistoryNon-Rails
pgHerofree—current state only✓
Lantern$9/mo✓30 days—
pganalyze$149+/mo✓long✓
Supabase Query Performancefree w/ Supabase—current state only✓
pgblame$19/mo (free tier)✓30 days✓
05 · Pricing

Free to start.
$19 to keep going.

The free tier is a real product, not a trial. Pro adds projects, history, and alerts when you need them.

◇ Free
$0
/forever
  • ✓1 project
  • ✓7-day query history
  • ✓Now + Since-last-deploy views
  • ✓No card required
Start free
◇ Prorecommended
$19
/per month
  • ✓5 projects
  • ✓30-day query history
  • ✓Email alerts on regressions
  • ✓Slack and Discord webhooks
  • ✓Priority support
Start free, upgrade later
06 · FAQ

Questions
we keep getting.

Do you ever see my data?
No. The agent runs in your environment and reads only aggregate stats from pg_stat_statements — never your application rows. The connection string and credentials never leave your machine. The agent is MIT-licensed at github.com/liberzon/pgblame-agent — you can read the literal SQL it runs.
Will the agent slow my database down?
Vanishingly. One SELECT every 60 seconds against pg_stat_statements (a system catalog view). The session has a 5-second statement timeout and runs as a non-superuser, read-only role. If the query takes more than 2 seconds three times in a row, the agent backs off automatically.
Does it work with Supabase / Neon / RDS / self-hosted?
Yes. The agent only needs a Postgres connection string and a role with pg_read_all_stats. Supabase exposes it directly; Neon, RDS, and self-hosted Postgres are all supported.
How is this different from pgHero / Lantern / pganalyze?
pgHero is current-state only — no history, no deploy correlation. Lantern does deploy correlation but is a Rails-only gem. pganalyze does the most but starts at $149/mo. pgblame is the same shape as Lantern, language-agnostic, at $19/mo.
Can I self-host the dashboard?
The agent is MIT-licensed and the schema is open. The hosted dashboard isn't officially supported as a self-host target at MVP — fork at your own risk. Most users find $19/mo cheaper than running it themselves.