I built a tool to track per-tenant usage & billing on Supabase — would love your feedback
Building multi-tenant SaaS on Supabase, I kept hitting the same wall: Supabase shows usage per project, never per tenant. I couldn't tell which customer was driving my DB/egress/request load — which makes cost control and usage-based billing pure guesswork.
So I built usagebill to scratch my own itch, and I'd genuinely love feedback from people who've faced this.
What it does: one line wraps supabase-js (a fetch wrapper, not a gateway), tags each request/query with a tenant_id, ships the events to columnar storage instead of your Postgres, and turns per-tenant usage into a billing ledger you can export to Stripe.
Honest scope, because I know this crowd: it measures usage proxies — requests, query duration, egress bytes, rows — not raw CPU (on shared-schema/RLS that isn't separable anyway). Zero-PII by default, and the SDK is fire-and-forget so it never blocks your app.
It's live and self-serve if you want to poke at it. Mostly I want the brutal version — where would this fall down for your setup? What's missing before you'd trust it with billing?
(Disclosure: I'm the developer. Not trying to spam — genuinely validating whether this is worth pursuing.)