Skip to main content
Neon Postgres Docs
current

Search documentation

Type to search this documentation.

On this pageOverview

Monitor billing and usage

You can monitor usage and costs in the Neon Console or programmatically with the Neon API. For what each metric means and how it maps to your invoice, see Usage metrics and Invoice metrics on the Plan...

You can monitor usage and costs in the Neon Console or programmatically with the Neon API. For what each metric means and how it maps to your invoice, see Usage metrics and Invoice metrics on the Plans page.

Neon exposes usage in three places in the Console: the Billing page (account-level charges and plan summary), the Projects page (org-level usage metrics), and the Project dashboard (project-level usage metrics when you are inside a project).

From the Billing page (Organization → Billing in the Neon Console) you see account-level information: this month's summary including current plan, included features, usage-based pricing, and charges to date. Invoice line items appear only when there is a charge for that metric.

To open the Billing page:

  1. Navigate to the Neon Console.
  2. Select your organization from the profile menu in the top-right of the console.
  3. Select Billing.

From the Projects page (Organization → Projects) you see an org-level summary of four metrics across all projects: Compute, Storage, History, and Network transfer.

When you open a project, the Project dashboard (Project → Dashboard) shows the same four metrics for that project only: Compute, Storage, History, and Network transfer.

Usage is shown since the start of the current billing period. Metrics may be delayed by about an hour and are not updated for inactive projects.

On usage-based plans (Launch, Scale, Agent, and Enterprise), use the project consumption metrics API. It returns metrics that align with usage-based billing and match your invoice.

See Querying consumption metrics for the endpoint, required and optional parameters, example requests and responses, pagination, polling behavior, and building usage dashboards. For a guide to converting the raw API values into billing units and calculating your costs, see Usage and cost calculations.

Suggest an edit

Propose a replacement for this page. The site team reviews it before applying any changes.

Export
Documentation menu