Supabase Integration
Supabase uptime monitoring integration
Store PingAlert incidents in your Supabase Postgres database, stream them over Realtime, and create, update or pause monitors from Edge Functions. For teams that build on Supabase and want uptime data inside their own project.
Already have a PingAlert account? Log in
At a glance
- 01Incidents stored in public.pingalert_incidents
- 02Live incident feed through Supabase Realtime
- 03Create, update, and pause monitors from Edge Functions
- 04Signed webhooks, dedupe, and tenant routing
Path 1
Receive incidents in Postgres
- Run the migration to create
public.pingalert_incidents. - Deploy
pingalert-webhookas a public Edge Function. - Point PingAlert webhook delivery to the Supabase function URL.
- Subscribe to incident inserts through Realtime or query Postgres directly.
Path 2
Manage monitors from Supabase
- Store PingAlert API credentials in Supabase secrets.
- Deploy create, update, and pause-management functions.
- Invoke them from your backend or Edge Functions with a Supabase user JWT.
- Create, update, pause, resume, disable, or enable monitors programmatically.
Why teams use it
Supabase-native
Uses Edge Functions, Postgres, RLS, Realtime, project secrets, and optional Vault lookup.
Safe webhook handling
Webhook signature verification, dedupe protection, tenant-aware routing, and upstream 4xx error passthrough.
Documented end to end
Setup docs, security details, and a support path are published here, alongside PingAlert's privacy, terms, and acceptable-use policies.
Start with PingAlert
Create a PingAlert account, then connect your Supabase project.
Sign up for the free plan, create your first webhook or API credential, and use these integration docs to finish the Supabase setup.
PingAlert integration for Supabase: incidents in Postgres and monitor management from Edge Functions.