SUPABASE USAGE MONITORING
Supabase Usage Monitoring
Supabase Usage Monitoring is useful when it answers a concrete operating question. For Supabase, start with organization/project usage, compute, egress, storage, Auth/MAU, Realtime and functions. Supabase currently supports resource discovery and Project Map. CostNerve does not ingest Supabase monetary billing evidence; check usage and charges in the provider dashboard. Missing amounts are not zero cost.
What problem does it solve?
- project
- database
- storage
- egress
- realtime
- edge functions
What to check first
- Establish current spend, previous-period spend and forecast using the same scope.
- Use Uncached versus cached egress as the first provider-specific check, then attribute spend by project or service. Leave uncertain cost unallocated instead of guessing.
- Rank the top cost drivers by absolute money and growth rate, then investigate the first few deeply.
- Attach every saving or budget action to an owner, expected impact and a verification date.
Metrics and signals that matter
- Uncached versus cached egress
- Egress source: Database, Storage, Realtime, Auth, Edge Functions or Log Drains
- High-frequency queries and API endpoints
- Realtime subscriptions, large responses and download traffic
Likely causes
Deployment or configuration regression
A release can change request fan-out, runtime, memory, model choice, logging volume or cache behavior without obvious user-facing breakage.
Traffic, retries or loops
Legitimate growth, bots, retry storms and recursive/background loops can all multiply a normally cheap unit of work.
Billing dimension changed
For Supabase, investigate Uncached versus cached egress and Egress source: Database, Storage, Realtime, Auth, Edge Functions or Log Drains before assuming the total moved for a single reason.
How it works
What to check in the provider dashboard
Open the Supabase usage and billing dashboard; this guide does not imply live CostNerve ingestion. Compare project, database, storage over equal, complete periods. Keep usage, estimates and invoice amounts separate. Record the scope, currency and last update. Check integration coverage before connecting; use available connectors for supported evidence.
Integration status
Supabase currently supports resource discovery and Project Map. CostNerve does not ingest Supabase monetary billing evidence; check usage and charges in the provider dashboard. Missing amounts are not zero cost.
Worked example with explicit assumptions
Illustrative alert: a project normally spends 20 USD/day. A reading of 35 USD is 15 USD and 75% above baseline. Check both the absolute increase and the percentage, and exclude incomplete days before escalating.
Frequently asked questions
Which Supabase signals should I inspect first?
Start with Uncached versus cached egress, Egress source: Database, Storage, Realtime, Auth, Edge Functions or Log Drains, High-frequency queries and API endpoints. Compare the same time window before and after the change so volume and unit-cost effects do not get mixed.
Does a budget alert stop spending?
No. A notification is not a spending cap. Verify delivery, data freshness and escalation separately. Any supported control must be explicitly enabled and its effect checked; read-only monitoring does not change infrastructure.
Should uncertain cost be forced into a project?
No. Keep it unallocated until tags, project IDs, resource IDs or another reliable signal justify attribution. False precision produces worse decisions than visible uncertainty.