Provider capabilities
Supported does not mean identical.
DatabaseMeter combines Neon and Supabase in one portfolio while preserving the source, scope, and limits of every measurement.
Unavailable stays unavailable
DatabaseMeter does not treat missing provider values as zero and does not translate one provider’s disk, requests, or workload telemetry into another provider’s billing metric. Optional PostgreSQL telemetry is identified separately from Management API usage.
| Capability | Neon | Supabase |
|---|---|---|
| Provider project discovery | Available Discovers accessible projects through project, organization, or personal API-key scope. | Available Discovers accessible projects in the selected organization through a personal access token. |
| Provider usage API | Available Current project metrics plus daily consumption history when the key scope and plan permit it. | Partial / provider-limited Current filesystem utilization and daily API request categories are collected where permitted. |
| Postgres database size | Available Current logical Postgres storage is collected from the project API. | Available with telemetry connection The Management API value used by DatabaseMeter is filesystem disk use; direct read-only telemetry can measure the selected database. |
| Provider compute usage | Available Daily CU-hours and current-period CPU-hours are retained with their original units and periods. | Not currently available The current project endpoints do not provide compatible dedicated-compute consumption. |
| Egress / network data | Available Available daily public and private network transfer values remain separately identifiable. | Not currently available DatabaseMeter does not receive a compatible project byte total from its current endpoints. |
| Object / provider storage | Partial / provider-limited Postgres storage and provider-native storage categories are retained; Neon is not treated as object storage. | Partial / provider-limited Filesystem disk use is available, but object storage bytes are not supplied by the current endpoints. |
| Database, table, and index telemetry | Available with telemetry connection A dedicated read-only PostgreSQL role supplies database and relation statistics. | Available with telemetry connection A dedicated read-only PostgreSQL role supplies database-level and relation statistics. |
| pg_stat_statements workload telemetry | Available with telemetry connection Available when the extension and required statistics visibility are configured. | Partial / provider-limited Managed-role delegation can limit cross-role statement visibility even when database telemetry is connected. |
| Cost planning | Available Qualified Launch/Scale planning ranges use versioned rules and stored compatible usage. | Not currently available No project estimate is produced without compatible compute history and defensible organization allowance allocation. |
| Scheduled collection | Available Provider collection and optional telemetry use protected, independently scheduled dispatchers. | Available Provider collection and optional telemetry use protected, independently scheduled dispatchers. |
| In-app alerts | Available Rules evaluate only when the required stored metric is available. | Available Rules evaluate only for the subset of stored metrics each project actually exposes. |
Availability describes the implementation currently shipped in DatabaseMeter. Provider permissions, plans, extensions, and API responses can still limit an individual project.