Security And Trust
Supabase uptime monitoring integration security
How the integration stores credentials, verifies webhook deliveries, controls function access, and protects incident data in Postgres. For teams reviewing the integration before connecting it to production.
Already have a PingAlert account? Log in
At a glance
- 01Credentials read from Supabase project secrets
- 02JWT verification on management functions
- 03Invalid webhook signatures rejected with 401
- 04Incident reads protected by RLS
Secrets and credentials
- PingAlert credentials are read from Supabase project secrets first.
- Vault lookup is optional and only used when the Vault extension is available.
- Recommended client-credential scopes are
monitors:readandmonitors:write.
Function access model
pingalert-webhookis public and intended for PingAlert webhook delivery.- Management functions keep JWT verification enabled by default.
- Incident writes use service-role privileges while reads stay behind RLS for authenticated users.
Webhook protections
Signature verification
If PINGALERT_WEBHOOK_SECRET is configured, the webhook receiver verifies signed requests and rejects invalid deliveries with 401.
Idempotency
Incident persistence uses dedupe_key upserts so retried deliveries do not create duplicate events.
Tenant routing
The receiver supports tenant_id routing through query param, header, or payload fields, so one Supabase project can segment multiple PingAlert workspaces.
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.