Super

Commented on UsageRail · Nov 6, 2026

I'm the maker. The design choice that shaped everything else was keeping UsageRail out of the request path: the SDK checks keys and limits in your own process, and request and response bodies never leave your server. Framework guides cover Express, Hono, Fastify, Next.js, Cloudflare Workers, FastAPI, Flask and Django. If your stack isn't on that list, or something's missing for how you bill, I'd like to hear about it.

Commented on BackupDrill · Oct 1, 2026

Hi DevHunt, I'm Super and I build BackupDrill. What got me started: most teams on Supabase have backups, and very few have ever tried restoring one. The first time I restore-tested a real project's dump into plain Postgres, one table was missing. pg_restore printed an error and carried on, and the error was buried in the role and schema warnings you learn to ignore with Supabase dumps. So BackupDrill does two things. It backs up the database, plus Storage files once you add their S3 keys, into a bucket you own (S3, R2, B2 or Wasabi). Then it restores the backup into a throwaway Postgres and checks that every table came back. Paid plans run that drill weekly and email you the report. The Free plan covers one project with weekly backups and a drill on the first one. The backup engine is an MIT CLI (github.com/backupdrill/cli) if you'd rather run it yourself. Happy to answer questions.