Skip to main content

Supabase

Supabase works well with pocketPG as a managed PostgreSQL provider. The important distinction is that pocketPG monitors Supabase through the PostgreSQL connection itself, not through a separate Supabase API integration.

What to use when connecting​

Use the direct PostgreSQL connection string from the Supabase dashboard.

Do not use the pooler endpoint for pocketPG monitoring. A pooled connection can hide backend-level visibility that pocketPG expects for workload analysis and operational diagnostics.

What pocketPG reads normally​

With a direct connection and pg_monitor, pocketPG can still read the PostgreSQL-side signals that power the product:

  • health and checkpoint diagnostics
  • query analysis from pg_stat_statements
  • WAL and replication-pressure views
  • table and index statistics
  • tuning recommendations based on pg_settings and runtime activity

Provider-aware behavior​

When an instance is marked as Supabase, pocketPG keeps the provider identity so it can:

  • show the correct setup guidance
  • keep managed-provider checkpoint caveats attached
  • avoid pretending that a separate cloud metrics API integration exists

What is not integrated yet​

Supabase does not currently have an API-backed Infrastructure card in pocketPG for CPU, memory, or disk charts.

That is different from Aiven, which has a dedicated provider API integration. For Supabase, the current product boundary is: PostgreSQL monitoring yes, provider API monitoring not yet.