Neon Pricing
Start free, launch with predictable costs, and scale efficiently.
Neon pricing plans
- 0.5 GiB storage
- 24/7 for your main compute
- Community support
- Fixed capacity at 0.25 vCPU
- Instant Read Replicas
- IP Allow Rules
- 10 GiB storage included
- 300 compute hours included
- Standard support
- Autoscaling up to 4 CU
- Instant Read Replicas
- IP Allow Rules
Scale
From $69 /month
Get startedFull platform and support access, designed for scaling production workloads.
- 50 GiB storage included
- 750 compute hours included
- Priority support
- Autoscaling up to 8 CU
- Instant Read Replicas
- IP Allow Rules
- Storage and compute discounts
- Higher resource limits
- Customer-owned S3
- Enterprise support w/SLAs
Not sure which plan is right for you?
Explore the .
Increase velocity. Scale efficiently.
Teams of all sizes use branching to increase development velocity, and autoscaling means costs stay efficient with zero effort.
Explore case studieslaunch
Uses Neon to streamline dev, test and prod of their YC-backed SaaS startup.
Scale
Built Insurtech on Neon to focus on shipping product, not babysitting infrastructure
enterprise
Vercel and Neon unlock the first Serverless Postgres database for the Frontend Cloud.
enterprise
75% cost reduction by moving a fleet of databases powering multi-tenant SaaS to Neon.
Detailed plan comparison
Find the plan that fits your needs.
Frequently Asked Questions
In Neon, you are charged a monthly fee (corresponding to your pricing plan) plus any additional compute and/or storage usage over the limits included in your plan. For example, the Launch plan includes 300 compute-hours of compute usage; if you consume 320 compute-hours in a month, you will be billed additionally for 20 compute-hours.
Neon bills for the past month's usage at the beginning of each calendar month. For more information, see Manage billing.
Compute hour is the metric for compute usage in Neon. The quick math: [compute hours] = [compute size] x [hours your compute runs]. Each pricing plan includes a certain number of compute hours; how quickly you consume these hours depends on the size of your compute and how long it runs. Once you exceed the allocated amount of compute hours, you'll be billed for overages in a given month.
You can get a good idea by estimating how many hours your databases run, and at which compute size. For example: imagine you’re running a 2 CPU, 8 GB RAM database for 2 hours a day (or 62 hours per month). This equals [2 CU * 62 hours] = 124 compute hours per month.
When enabling autoscaling, you will set a maximum autoscaling limit (e.g. 2 CU) that will act as a de-facto cost limit.
Neon implements a unique storage engine that enables database branching on copy-on-write, without duplicate storage. You can create instant database copies (database branches) without adding to the storage bill. Since Neon retains database history, the size of storage for a Neon project will be calculated as the size of your tables plus the WAL up to the configurable history retention period.
Yes, we display your usage consumption in the Neon admin console and we will also email you when you’re getting close.
Neon implements usage limits for branching in order to prevent potential abuse of the service which can negatively impact other users. For customers seeking higher limits please contact customer-success@neon.tech.
Still have questions?
Interested in learning more about our plans and pricing? Complete the form below to get in touch with our Sales team.
Talk to Sales