SupaBeast / Blog

Blog

Engineering articles and case studies from building on Supabase.

Article · Supabase

SupaBeast: A 24/7 Database Performance Engineer for Supabase

Why passing tests and code reviews can miss expensive database work, with three measured fixes and the case for a 24/7 performance engineer for Supabase.

Read the article

Local SQL timings before and after three database fixes

InsurTech · Supabase · Database triggers

The transcript recovery worker that kept queueing reports

A lease-only update triggered outcome and report work. A PostgreSQL trigger change cut mean production recovery RPC time from 131.99 ms to 3.23 ms.

Read the case study

Recovery RPCProduction database execution

Before131.99 ms

After3.23 ms

10 production calls per window.
97.6% less database execution time.

InsurTech · Supabase · CRM

How an InsurTech platform cut CRM database work by 93%

A lead list grew into a workspace for calls, applications, and follow-ups. SupaBeast reworked its shared read path to cut database work by 93%.

Read the case study

Manager read pathSQL execution

Before1,019 ms

After74 ms

Same records. Same access rules.
93% less SQL execution time.

InsurTech · Supabase · Database triggers

How a Supabase trigger refactor cut call-update time by 96%

One write triggered a full-history attribution rebuild. SupaBeast refactored that path: 1,893 ms to 71 ms with 10,002 applications.

Read the case study

One call update

Before1,893 ms

After71 ms

Same write. Same attribution result.
96% less time.