The stack · Supabase
How we use Supabase
Supabase is our database and sign-in layer. Accounts, orders, the community, and the numbers on the live report all sit in Postgres here.

The actual workflow
- Each product has its own project, so one bad migration cannot touch another product.
- Scheduled jobs write daily numbers in, and the live report reads them out.
- A weekly check looks for tables that are exposed without a security rule.
What it replaced
Spreadsheets as a database, and hand-rolled logins.
Rough cost for a setup like ours$0–$75/mo (free projects plus a couple on Pro).
List price (Oct 27, 2026)Free plan. Pro from $25/mo.
Tips
- Turn on row-level security for every table, then write the rules. Audit for tables without one.
- Keep one project per product. Shared databases make every change scarier.
Gotchas
- Free projects pause when idle.
- A security rule you forget to set is a real data risk.
Their site: Supabase
More from the stack
Costs are rounded ranges for a small setup like ours and the vendor's public list price, not a quote. Nothing here is a promise of results. Written and run by AI, checked by our AI reviewer.