u/Hefty_Professor_4170

Yesterday I spent some time calculating how many tokens I actually use, just to understand what Fable might cost me without a subscription.

Turns out my current usage would be something like $2,000–$3,000 a week in tokens. And that’s with me trying not to use Claude on weekends.

While checking the numbers, I also noticed that I had two days in June where I processed around 830 million tokens in a single day.

Which got me thinking: in the era of AI coding agents, when you can generate a million lines of code a day, who even needs software developers?

I'm building a small tool that answers "which deploy slowed my Postgres?" and the best way to make it actually useful is to look at real production databases. So I'm offering free slow-query reviews to the first 5 people here.

What you get (free, ~20 min):

• I pull your top slow queries from pg_stat_statements — sorted by total time, i.e. the ones actually costing you, not just the scary-looking ones
• We work out why each is slow: missing index, N+1, RLS evaluating a function per-row, stale planner stats after a migration
• If you have deploy history, I'll try to pin which release/migration made something slow
• A short writeup of concrete fixes you can ship, yours to keep

What I want back: 15–20 min on a call + honest feedback on the tool. It's free for you either way — I'm trying to learn what real Supabase performance pain looks like.

On trust: the agent is read-only (runs as pg_monitor), reads only aggregate stats from pg_stat_statements — never your table rows — and it's MIT-licensed, so you can read exactly what it does. I never see application data.

Comment or DM to grab a slot.

(Disclosure: the tool is pgblame, not launched yet. This is genuinely about learning + giving free value, not a sales pitch.)

Hey r/Supabase — solo dev here. The thing that always bugged me about shipping
on Postgres: CI guards your *code* — tests, linters, deploy gates, all green —
and then goes totally silent on your *database*. You ship, and nobody's
watching whether that deploy just slowed a query.

So I built **pgblame** to close that blind spot. A tiny Docker agent snapshots
`pg_stat_statements` every 60s, takes a webhook from your Vercel/Railway/
GitHub-Actions deploys, and lines them up — "this query went 40ms → 800ms right
after *this* deploy." Same idea as Lantern, but not Rails-only, \~1/8 the price
of pganalyze ($19/mo, real free tier, no card).

Trust (it's a DB tool, so this matters): the agent runs in **your** environment
as a **read-only** non-superuser (`pg_monitor`), only reads aggregate stats
from `pg_stat_statements` — never your rows — and it's **MIT-licensed**, so you
can read the exact SQL it runs.

Looking for **2 people on Supabase + Vercel/Railway who ship a few times a**
**week** to set it up while I watch over a 20-min call — I want to find where
onboarding is confusing before posting it more widely. **Free Pro forever**,
zero obligation. Comment or DM.

Hey r/Supabase — solo dev here. The thing that always bugged me about shipping
on Postgres: CI guards your code — tests, linters, deploy gates, all green —
and then goes totally silent on your database. You ship, and nobody's
watching whether that deploy just slowed a query.

So I built pgblame to close that blind spot. A tiny Docker agent snapshots
pg_stat_statements every 60s, takes a webhook from your Vercel/Railway/
GitHub-Actions deploys, and lines them up — "this query went 40ms → 800ms right
after this deploy." Same idea as Lantern, but not Rails-only, ~1/8 the price
of pganalyze ($19/mo, real free tier, no card).

Trust (it's a DB tool, so this matters): the agent runs in your environment
as a read-only non-superuser (pg_monitor), only reads aggregate stats
from pg_stat_statements — never your rows — and it's MIT-licensed, so you
can read the exact SQL it runs.

Looking for 2 people on Supabase + Vercel/Railway who ship a few times a
week to set it up while I watch over a 20-min call — I want to find where
onboarding is confusing before posting it more widely. Free Pro forever,
zero obligation. Comment or DM.