Neon Pricing

Your questions,
answered

• What is a project?

  A project in Neon is the top-level container for your database environment. Each project includes your primary database, its branches, and compute resources. You can think of it like a GitHub repo - one project, many branches. Learn more about Neon’s object hierarchy.

• What is a CU?

  A CU (short for Compute Unit) is Neon's way of representing instance size. It defines how much CPU and memory your database is using at any moment. At Neon, 1 CU = 1 vCPU + 4 GB RAM.

• How is compute usage measured in Neon?

  Neon is a serverless database: it bills per true monthly usage. Your compute monthly usage is based on how long your compute runs and at what size.
  We measure compute usage in CU-hours:

  CU-hours = CU size of your compute × number of hours it runs

  For example: if a 2 CU machine runs for 3 hours, that’s 6 CU-hours of usage.
  Learn more about Neon’s serverless model.

• How is storage usage billed in Neon?

  Neon also charges for storage based on actual data usage, not allocated capacity. We measure this in GB-months:

  1 GB-month = 1 GB stored for 1 full month

  Storage is metered hourly and summed over the month, so you only pay for what you actually use, not for the maximum size your database reaches.

• What happens with branches and storage?

  Each project in Neon starts with a root branch (your main database). You can then create child branches, which are isolated copies of your database state - great for testing, previews, and development.
  But Neon uses a copy-on-write model, so:

  • Child branches do not increase your storage bill unless they diverge from the root.
  • Only the differences (delta) between the root and each branch are counted.

  At the end of the month, your total storage usage is:

  Total GB-month = Root branch size + delta from all child branches
  Learn more about Neon’s serverless model.

• How are Instant Restores billed?

  Instant restores (also known as Point-in-Time Recovery, or PITR) are billed based on how much data changes in your primary branch over time, not how many restores you do:

  • The Free plan gives you up to 6 hours of restore history, or 1 GB of data changes - whichever comes first. If your app writes a lot of data, you may get less than 6 hours of coverage.
  • In the Launch plan, you can choose any restore window from 0 to 7 days. You're charged $0.20 per GB-month, based on how much data changes during that window. Setting it to 0 disables Instant Restores, and implies $0 additional costs.
  • In the Enterprise plan, you can set a restore window up to 30 days, billed at $0.20 per GB-month for the changed data (same logic as Launch).

  Read the docs for more information on Instant Restores.

• How does billing for additional branches work?

  Each Neon plan includes a number of simultaneous branches per project at no extra cost. For example, the Launch plan includes 10. You can create and delete as many branches as you like throughout the month; you’ll only be billed if the number of active branches at the same time exceeds this included quota.

  If that happens, we’ll meter the extra usage using a metric called a branch-hour, which is:

  1 additional branch × 1 hour of lifetime

  For example: if your plan includes 10 branches and you briefly run 2 extra branches for 5 hours each, that’s 10 branch-hours, billed at $0.002 per branch-hour, or a total of $0.02 added to your bill.

  To be exact: we bill extra branches at $1.50/month each, prorated to hours based on the month’s length. The effective hourly rate varies slightly, but rounds to $0.002/hour in most cases — which is what we show for simplicity.

• Why is the monthly minimum the same in the Launch plan vs. the Scale plan?

  Instead of charging a higher flat monthly fee, we’ve chosen to price the premium features of the Scale plan through compute usage - via a higher price per CU-hour.

  This means you only pay more when you actually use the additional capabilities. You’re choosing to pay more for higher availability and enhanced security, which require operational redundancy on our side, while still keeping costs tied to your usage. Read more.

• How can I control my costs?

  Neon lets you control compute usage by setting a maximum autoscaling limit per branch. This acts as a de-facto cost ceiling - your database won’t scale beyond the limit, even if traffic spikes.

  For example, if you set a limit of 1 CU, your usage will never exceed 1 CU-hour per hour, regardless of demand. Learn how to configure autoscaling limits.

• Do you offer credits for startups?

  Early startups that have received venture funding are eligible to apply to our Startup Program.

  Learn more and apply here