FAQ
Clear answers about the meter.
What DatabaseMeter measures, what it deliberately avoids, and what comes next.
Does DatabaseMeter connect to Neon and Supabase?
Yes. Provider Management API connections are encrypted and server-side. Phase 4 also supports a separate optional read-only PostgreSQL telemetry connection per monitored project.
Does it read the rows in my application tables?
No. Optional PostgreSQL telemetry uses fixed read-only queries against system catalogs and aggregate statistics. It does not select application tables or store customer row contents or SQL text.
Is query activity the same as provider compute billing?
No. Observed SQL execution can help explain workload, but it is not exact CU-hour, compute-hour, or cost attribution unless a provider supplies an authoritative mapping.
What happens when a metric is unavailable?
DatabaseMeter displays it as unavailable. A missing value is never silently replaced with zero.
How are credentials protected?
Authentication is handled by Auth0. Neon and Supabase credentials are validated server-side, encrypted with a separate versioned key before storage, decrypted only for provider calls, and never displayed after submission.
Can I monitor more than one provider?
That is the core product direction: a single portfolio containing Neon and Supabase projects while preserving each provider’s terminology.