NEON COST MONITORING
Neon Postgres Cost Monitoring by Project
Database cost only becomes actionable when it is connected to the product and workload creating it. Neon currently supports resource discovery and consumption ingestion. Usage is not exact billed USD: confirm monetary charges in Neon before using them for margin or invoice reconciliation.
What problem does it solve?
- project
- compute
- CU-hours
- storage
- branches
- network transfer
What to check first
- Establish current spend, previous-period spend and forecast using the same scope.
- Use Compute CU-hours and autoscaling behavior 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
- Compute CU-hours and autoscaling behavior
- Storage GB-month growth
- Active branches and branch lifetime
- Public/network transfer and long-running queries
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 Neon, investigate Compute CU-hours and autoscaling behavior and Storage GB-month growth before assuming the total moved for a single reason.
How it works
What to check in the provider dashboard
Open the Neon usage and billing dashboard; this guide does not imply live CostNerve ingestion. Compare project, compute, CU-hours 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
Neon currently supports resource discovery and consumption ingestion. Usage is not exact billed USD: confirm monetary charges in Neon before using them for margin or invoice reconciliation.
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 Neon signals should I inspect first?
Start with Compute CU-hours and autoscaling behavior, Storage GB-month growth, Active branches and branch lifetime. 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.