Use case

SaaS on Vercel and Supabase

The most common stack for new SaaS. Pagerless covers both halves: roll back the deploy on Vercel, restart or add compute on Supabase.

Set up

npx pagerless connect

It adds the Next.js instrumentation file and puts the key in Vercel. Then connect Vercel and Supabase in the app with access tokens so fixes can run.

Who's to blame, in plain words

Calls to Supabase are tagged by name in the SDK, so the diagnosis can say "Supabase is timing out" instead of "500 on /api/projects", and offer a restart rather than a rollback that wouldn't help.

Fixes on this stack
WhereFixes
VercelRoll back to the previous deployment; redeploy
SupabaseRestart the project; add compute (billed, so it always asks)

Updated .

Free for you and one backup · 3 apps · no card

Sleep through the small stuff.

Run one command in your repo. Pagerless shows every change before it makes it.

npx pagerless connect