The use case: how Supabase deploys Sentry
Supabase's frontend team uses Sentry to filter noise, rank and fix user-impacting bugs, trace requests from Studio to backend APIs, and alert on instability. The backend team uses it to correlate errors, logs, metrics and traces, with a custom tail-based trace sampling pipeline and escalation alerting.
More reported results
Figures published in Sentry’s case study. They are not independently measured by usedby.
Five high-impact bugs were discovered and fixed, retiring ~115,000 events and unblocking ~6,300 users.
A 24-hour snapshot after rollout: 7.18M transactions/day, 630K pageloads, 6.2M navigations, and per-endpoint latency data for every path Studio takes through the backend.
In the customer’s words
A teammate merged a PR, noticed Sentry issues, and fixed with a follow-up PR. Never got alerted by a customer about this. This is the gold standard.Other AI tools used by Supabase
Other public relationships recorded on usedby.
Explore Supabase’s AI stackSentry users in DevTools & Infrastructure
Companies in the same sector, with public evidence.
AtlassianConfirmed
BitnamiConfirmed
Bolt.newConfirmed
FactoryConfirmed
Faros AIConfirmed
SmugMugConfirmedGo straight to the source
Based on Sentry’s published case study. We check the public evidence; the results are reported by the vendor.
sentry.io- Last checked
- Nov 12, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 60xChecked
The figure is on the page; its label is our wording.
- Supabase uses SentryChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Three weeks later: weekly crashes dropped from 2,000+ to 32.






