Your connection budget is three equations, and most "too many connections" surprises come from one of them being a multiplication you did as an addition. I rebuilt a Nano-sized Supabase limit set on my laptop, pushed past every limit, and wrote down what failed, in what order, and with which error text. Some checks ran on a hosted Free project at tiny scale, and a few that only a paid plan exposes ran on a throwaway Pro project I created and deleted the same day. Scripts, numbers and a calculator are in the repo. Everything is from my runs on 2026-11-03 and 2026-11-04; prices and versions change, so numbers carry dates.
The most serious finding is not about capacity: on the transaction pooler, a setting left behind by one client leaked rows (through an RLS policy) and an admin role's privileges to the next client (section 10).
How this was made: I wrote this with Claude's help: it drafted, and I ran every step, edited the text, and checked the results.…