Neon integration on Vercel: Create a branch for every Preview DeploymentLearn More

Billing

Neon offers the following plans: Free Tier, Pro, Enterprise, and Platform Partnership. The Pro plan is usage-based, ensuring you never over-provision and only pay for what you use. The Enterprise and Platform Partnership plans are custom volume-based plans that offer potential discounts. You can find out more about our plans below.

Neon billing metrics

Neon charges for usage based on the following metrics:

  • Compute time: A measure of the amount of computing capacity utilized by Neon for a given time interval.
  • Project storage: The size of the data and history stored for your project.
  • Written data: The amount of data written from compute to storage.
  • Data transfer: The amount of data transferred out of Neon.

See Billing and usage metrics explained for a detailed description of each metric and how Neon calculates costs.

Neon plans

Free TierPro (usage-based)Custom - Enterprise or Platform Partnership (volume-based)
Best forPrototyping and personal projectsSmall-to-medium teams, setups with 1 to 3 active databasesMedium-to-large teams, Database fleets, Resale
Projects120Unlimited
Branches10UnlimitedUnlimited
Compute active time per month100 hours*UnlimitedUnlimited
Compute size1 Shared vCPU with 1 GB RAMUp to 7 vCPUs, each with 4 GB RAMCustom
Storage3 GB per branchUnlimited*Unlimited
Dedicated resources--
Project sharing-
Auto-suspend compute
Configurable auto-suspend compute (coming soon)-
Autoscaling (coming soon)-
PaymentFreeCredit Card, Pay As You Go with monthly invoicingPrepaid, Custom Contract, Volume Discounts
SupportCommunity, support ticketsCommunity, support tickets, video chatCommunity, support tickets, video chat, resale customer support

Notes:

  • The limits described above are plan defaults. If you want to adjust the limits to tailor a plan to your specific requirements, please contact sales@neon.tech.
  • The Pro plan has a 200 GB safety limit on storage to protect your account from unintended usage, but the Pro plan supports any data size. To increase the safety limit for your Pro account, simply send a request to sales@neon.tech with the data storage size that you require.
  • The Free Tier has a 100 hour compute active time per month limit, but you are always able to connect to the compute endpoint assigned to the primary branch of your Neon project, which ensures that access to data on the primary branch of your project is never interrupted.

Account billing page

Each Neon account has a billing page, where you can:

  • View your current billing total for the month-to-date, including a cost breakdown by billing metric.
  • Update your payment details
  • Download your latest invoices

To access your billing page:

  1. Navigate to the Neon Console.
  2. Select Billing from the sidebar.

Neon invoices

A Neon invoice includes an Amount due for billing period and the cost broken down by billing metric.

Download invoices

You can download invoices from the Billing page.

  1. Navigate to the Billing page in the Neon Console.
  2. Under Latest invoices, locate the invoice you want to download and click the PDF download icon.

Cancel a subscription

To cancel your subscription to a Neon paid plan:

  1. Navigate to the Billing page in the Neon Console.
  2. Click Cancel subscription.
  3. Enter your cancellation request and click Submit.

This action initiates the cancellation. If your data exceeds Free Tier storage limits, you will need to reduce your storage before the paid plan is canceled and Free Tier limits are applied. Your request will be processed by the Neon Support team.

Billing and usage metrics explained

This section provides a detailed explanation of Neon's billing and usage metrics and how they are calculated. Billing in Neon is account-based. For the billing rate for each metric, see Billing rates.

note

The Project storage, Written data, and Data transfer billing metrics are calculated in gibibytes (GiB), otherwise known as binary gigabytes. One gibibyte equals 230 or 1,073,741,824 bytes.

Compute time

The Compute time metric is a measure of the amount of computing capacity utilized by Neon for a given time interval. Neon takes a measure of compute utilization every five seconds, which is averaged based on the observed computing capacity. Computing capacity is based on Compute Units (CU). A CU in Neon is 1 vCPU and 4 GB of RAM. A Neon compute endpoint can have anywhere from .25 to 7 CUs. A connection from a client or application activates a compute endpoint and its CUs. Activity on the connection keeps the compute endpoint and its CUs in an active state. A defined period of inactivity places the compute endpoint and its CUs into an idle state.

Factors that affect the amount of compute time include:

  • The number of active compute endpoints
  • The number of CUs per compute endpoint
  • Neon's Auto-suspend compute feature, which suspends a compute endpoint (and its CUs) after a period of inactivity. The current default is five minutes.
  • Neon's Configurable auto-suspend compute feature, which allows you to disable or configure the timeout period for the Auto-suspend compute feature (coming soon).
  • Neon's Autoscaling feature, which allows you to set a minimum and maximum number of CUs for each compute endpoint. The number of active CUs scale up and down based on workload (coming soon).

note

Neon uses a small amount of compute time, included in your billed amount, to perform a periodic check to ensure that your computes can start and read and write data.

The cost calculation for Compute time is as follows:

compute units * active time (hours) * price per hour

Project storage

The Project storage metric measures the amount of data and history stored in your Neon projects. Project storage includes:

  • Current data size

    The size of all databases in your Neon projects. You can think of this as a snapshot of your data at a point in time.

  • History

    Neon retains a history to support point-in-time restore and database branching.

    • Point-in-time restore is the ability to restore data to a past point in time. Neon stores seven days of history in the form of WAL records for a Neon project. WAL records that fall out of this seven-day window are evicted from storage and no longer counted toward project storage.

    • A database branch is a snapshot of your data (including history) at the point of branch creation combined with WAL records that capture the branch's data change history from that point forward. When a branch is first created, it adds no storage. No data changes have been introduced yet, and the branch's snapshot still exists in the parent branch's history, which means that it shares the data in common with the parent branch. A branch only begins adding to storage when data changes are introduced or when the branch starting point falls out of the parent branch's history, in which case the branch's data is no longer shared in common. In other words, branches add storage when you modify data and allow the branch to age out of the parent branch's history.

      Database branches can also share a history. For example, two branches created from the same parent at or around the same time will share a history, which avoids additional storage. The same is true for a branch created from another branch. Wherever possible, Neon minimizes storage through shared history. Additionally, to keep storage to a minimum, Neon will take a new branch snapshot if the amount data changes grow to the point that a new snapshot would consume less storage.

The cost calculation for Project storage is as follows:

project storage (GiB) * (seconds stored / 3600) * price per hour

Written data

The Written data metric measures the amount of data changes written from storage. Neon processes this data in a reliable way to ensure durability of your data.

The cost calculation for Written data is as follows:

written data (GiB) * price per GiB

Data transfer

The Data transfer metric counts the amount of data transferred out of Neon (egress). Neon charges for each GiB of data transfer at the egress cost set by the cloud provider. Contact sales@neon.tech for custom solutions to minimize data transfer costs.

The cost calculation for Data transfer is as follows:

data transfer (GiB) * price per GiB

Billing rates

Cloud providerRegionBilling metricPriceUnit
AWSUS East (Ohio)Compute time$0.10200Compute-hour
AWSUS East (Ohio)Project storage$0.000164GiB-Hour
AWSUS East (Ohio)Written data$0.09600GiB
AWSUS East (Ohio)Data transfer$0.09000GiB
AWSUS West (Oregon)Compute time$0.10200Compute-hour
AWSUS West (Oregon)Project storage$0.000164GiB-hour
AWSUS West (Oregon)Written data$0.09600GiB
AWSUS West (Oregon)Data transfer$0.09000GiB
AWSEurope (Frankfurt)Compute time$0.11800Compute-hour
AWSEurope (Frankfurt)Project storage$0.00018GiB-hour
AWSEurope (Frankfurt)Written data$0.09600GiB
AWSEurope (Frankfurt)Data transfer$0.09000GiB
AWSAsia Pacific (Singapore)Compute time$0.12100Compute-hour
AWSAsia Pacific (Singapore)Project storage$0.00018GiB-hour
AWSAsia Pacific (Singapore)Written data$0.09600GiB
AWSAsia Pacific (Singapore)Data transfer$0.09000GiB

Support

Support channels for the Neon Free Tier and paid plans are outlined below.

Support channelsFree TierProCustom
Neon Community Forum
Ability to submit support tickets
Video chat-
Resale customer support--

note

Pro plan users that submit support tickets through Neon's console can expect an initial response time of 2 business days, from 6am to 6pm Pacific Standard Time (UTC -8), Monday through Friday, excluding public holidays in the United States.

Free Tier users are not guaranteed a specific response time. For custom solutions, please contact sales@neon.tech.

Edit this page
Was this page helpful?