Is everything okay?
Surface approaching limits, sync failures, inactivity, and unusual usage in one prioritized view.
Database portfolio visibility
Track size, usage, growth, limits, and operational signals across Neon and Supabase—without confusing provider metering with database workload.
Secure Neon and Supabase Management API connections are available now. Demo data remains an explicit preview.
Portfolio overview
Good afternoon
Projects
8
5 need attention
30-day growth
+12.1%
Known databases
Lattice API
neon · US East
3.8 GB
+4.8%
Orbit Commerce
neon · US West
18.6 GB
+18.2%
Pulse Analytics
neon · EU Central
11.2 GB
+7.9%
Archive Notes
neon · US East
840.0 MB
+0.1%
Answers, not chart clutter
Surface approaching limits, sync failures, inactivity, and unusual usage in one prioritized view.
Compare 7- and 30-day database trends and see which projects are changing fastest.
Compare provider usage with observed PostgreSQL workload while keeping the distinction explicit.
Neon + Supabase
Normalized views make projects comparable, while metric labels and provenance retain what Neon or Supabase actually reported. Missing data stays unavailable—it never becomes a misleading zero.
Neon projects
4
Synthetic
Supabase projects
4
Synthetic
Known size
75.2 GB
Across 8 fixtures
Needs attention
5
Deterministic rules
Optional PostgreSQL telemetry identifies observed workload contributors and possible keep-awake patterns. DatabaseMeter never claims that SQL execution time equals exact provider billing attribution.
How workload telemetry works →Track current database size, growth pace, and user-configured thresholds. Explainable projections show assumptions and remain clearly labeled as projections.
Explore monitoring features →Security posture
Authentication is server-enforced with Auth0. Neon API credentials are validated and encrypted server-side, then never displayed again. DatabaseMeter’s normal monitoring model does not collect application table-row contents.
Read the security model →Secure workspace
Checking your session…