Monitor billing and usage

Neon exposes usage metrics in the Neon Console and through the Neon API.

View usage metrics in the Neon Console

Usage metrics in the console can be found on the Billing page.

Billing page

You can monitor billing and usage for your Neon account from the Billing page in the Neon Console.

Navigate to the Neon Console.
Select your organization from the breadcrumb menu at the top-left of the console.
Select Billing.

Here you will find the current bill and usage for your Neon account.

Usage metrics on the Billing page include:

Compute, CU-hour
Extra branches, branch-month
Instant restore storage, GB-month
Private data transfer, GB
Public data transfer, GB
Storage (root branches), GB-month
Storage (child branches), GB-month

These are the usage metrics you'll find on your monthly invoice, if they apply to your plan.

For an explanation of usage metrics, refer to the Plan feature explanations.

note: billing metrics for pre-2025 custom contract customers

If you signed a contract with Neon prior to 01/01/2025, different billing metrics apply:

Storage is measured in GiBs instead of GB-month, and if you exceed your contract's monthly storage allowance, extra storage units are automatically allocated and billed. Extra storage charges are applied based on the number of additional storage units needed to cover peak storage usage during the current billing period, prorated from the date the extra storage was allocated. Peak usage resets at the beginning of the next billing period.
Written data is the total volume of data written from compute to storage over the during the monthly billing period, measured in gigibytes (GiB).

If you have questions or want to change the billing metrics defined in your contract, please contact your Neon sales representative.

Retrieve usage metrics with the Neon API

You can retrieve a variety of usage metrics using the Neon API.

monitoring usage for a large number of projects

Enterprise users can use Neon's advanced consumption endpoints to monitor account and project usage. These endpoints are recommended when monitoring usage for a large number of projects. See Querying consumption metrics.

Any user can query usage metrics for a branch or a project, as described below. See:

Get branch details
Get project details

Get branch details

This example shows how to retrieve branch details using the Get branch details API method. Usage data is highlighted. Refer to the response body section of the Get branch details documentation for descriptions.

curl --request GET \
     --url https://console.neon.tech/api/v2/projects/summer-bush-30064139/branches/br-polished-flower-a5tq1sdv \
     --header 'accept: application/json' \
     --header 'authorization: Bearer $NEON_API_KEY' | jq

Response body

{
  "branch": {
    "id": "br-polished-flower-a5tq1sdv",
    "project_id": "summer-bush-30064139",
    "name": "main",
    "current_state": "ready",
    "logical_size": 427474944,
    "creation_source": "console",
    "default": true,
    "protected": false,
    "cpu_used_sec": 2505,
    "compute_time_seconds": 2505,
    "active_time_seconds": 9924,
    "written_data_bytes": 1566733560,
    "data_transfer_bytes": 40820887,
    "created_at": "2024-04-02T12:54:33Z",
    "updated_at": "2024-04-10T17:43:21Z"
  }
}

Get project details

This example shows how to retrieve project details using the Get project details API method. Usage data is highlighted. Refer to the response body section of the Get project details documentation for descriptions.

curl --request GET \
     --url https://console.neon.tech/api/v2/projects/summer-bush-30064139 \
     --header 'accept: application/json' \
     --header 'authorization: Bearer $NEON_API_KEY' |jq