Set up
Your app's calls to Supabase are tagged by name, so a failing database shows up as Supabase failing, not as a mystery 500.
Store the key with where your app runs. Or run npx pagerless connect and it finds your services and places the key for you.
Fixes on Supabase
| Fix | On Supabase |
|---|---|
| Undo the update | Not available |
| Restart | Restarts the project |
| Add capacity | Adds compute (a billed add-on, so it always asks) |
| Deploy events | From the SDK's deploy marker |
| Access it needs | a Supabase access token |
Pagerless never undoes anything on a database host: going back in time on live data is not a safe one-tap action.
Questions
Can Pagerless roll back Supabase automatically?
Not on Supabase. It alerts you and, where available, restarts or adds capacity.
Does Pagerless need admin access to Supabase?
It needs a Supabase access token. It is stored encrypted and used only for the fixes listed above. You can skip it: alerts work without it.