[metadata]
description: Neon brings serverless architecture to Postgres, which allows us to offer you flexible usage and volume-based plans.
og:description: Neon brings serverless architecture to Postgres, which allows us to offer you flexible usage and volume-based plans.
og:image: https://neon.com/images/social-previews/pricing.jpg
og:site_name: Neon
og:title: Pricing — Neon
og:type: website
og:url: https://neon.com/pricing
twitter:card: summary_large_image
twitter:description: Neon brings serverless architecture to Postgres, which allows us to offer you flexible usage and volume-based plans.
twitter:image: https://neon.com/images/social-previews/pricing.jpg
twitter:site: @neondatabase
twitter:title: Pricing — Neon
viewport: width=device-width, initial-scale=1, viewport-fit=cover

[canonical-links]
https://neon.com/pricing

[document-links]
10,000 connections: /docs/connect/connection-pooling
22.8k: https://github.com/neondatabase/neon
AI Gateway One API for frontier and open-source models: /docs/ai-gateway/overview
About us The company and the mission: /about-us
About: /about-us
Add files to your Postgres branches via Neon Object Storage, our S3-compatible object store: https://neon.com/blog/building-neon-object-storage
Agents Build full-stack AI agents: /use-cases/ai-agents
Apache Software Foundation: https://www.apache.org
Auth Authentication built into your database: /docs/neon-auth/overview
Autoscaling Automatic instance sizing: /docs/introduction/autoscaling
Available: /docs/security/compliance#soc-2
Available: /docs/security/hipaa
Blog Technical posts & product updates: /blog
Blog: /blog
Branching Faster Postgres workflows: /branching
CCPA Compliant: https://trust.neon.com/?itemUid=4064ac33-7b48-407b-aed7-ce02971d1ec1
California Privacy: https://www.databricks.com/legal/supplemental-privacy-notice-california-residents
Careers Join the team: https://www.databricks.com/company/careers/open-positions?department=engineering&location=all&itm_source=www&itm_category=company&itm_page=engineering-at-databricks&itm_location=body&itm_component=hero&itm_offer=open-positions
Careers: https://www.databricks.com/company/careers/open-positions?department=engineering&location=all&itm_source=www&itm_category=company&itm_page=engineering-at-databricks&itm_location=body&itm_component=hero&itm_offer=open-positions
Case studies Explore customer stories: /case-studies
Changelog Product updates: /docs/changelog
Changelog: /docs/changelog
Community Connect on Discord: https://discord.gg/92vNTzKDGp
Community Guides: /guides
Compliance Guide: /docs/security/hipaa
Contact Sales: /contact-sales
Contact sales Contact sales team: /contact-sales
Database per tenant Data isolation without overhead: /use-cases/database-per-tenant
Dev/Tests Production-like environment: /use-cases/dev-test
Discord: https://discord.gg/92vNTzKDGp
Docs: /docs
FAQs: /faqs
Functions Serverless compute next to your data: /docs/compute/functions/overview
GDPR Compliant: https://trust.neon.com/?itemUid=45220873-6e51-4dbb-b1b1-37d66ee9ef95
Get started: https://console.neon.tech/app/billing#plans
Get started: https://console.neon.tech/signup
GitHub: https://github.com/neondatabase/neon
HIPAA Compliant: /docs/security/hipaa
History window: /docs/introduction/history-window
ISO 27001 Certified: https://trust.neon.com/?itemUid=1fed9faa-4a87-427c-9a95-96b4d6bf66b7
ISO 27701 Certified: https://trust.neon.com/?itemUid=dc79cbc7-c99d-4eb9-891e-f5dc44b943d7
Instant Restore Instant recovery when mistakes happen: /docs/introduction/branch-restore
Lakebase Architecture Storage-compute separation: /docs/introduction/architecture-overview
Lakebase Postgres Serverless Postgres database: /docs/postgres/overview
Learn about scale to zero.: /docs/introduction/scale-to-zero
Learn how to configure autoscaling limits.: /docs/guides/autoscaling-guide#configure-autoscaling-defaults-for-your-project
Learn more about App generation platforms: /programs/agents
Learn more about Early-stage startups: /startups
Learn more about Neon's billing.: /docs/introduction/about-billing
Learn more about Open source on Neon: /programs/open-source
Learn more about how Neon billing works.: /docs/introduction/about-billing
Learn more about optimizing storage usage.: /docs/introduction/cost-optimization#storage-root-and-child-branches
Learn more about our Free Plan philosophy.: /blog/why-so-many-projects-in-the-neon-free-plan
Learn more and apply here.: /startups
LinkedIn: https://www.linkedin.com/company/neon-inc/
Log in: https://console.neon.tech/login
Modern Slavery Statement: https://www.databricks.com/legal/modern-slavery-policy-statement
Multi-TB Scale and restore instantly: /use-cases/multi-tb
Multiple options: /docs/introduction/support
Neon API: /docs/manage/branches#branching-with-the-neon-api
Neon CLI: /docs/guides/branching-neon-cli
Neon Console: https://console.neon.tech
Neon Platform Terms: /platform-terms
Neon status loading...: https://neonstatus.com/
Neon: /
Neon’s Sub Contractors: /hipaa-contractors
Object Storage S3-compatible storage that branches: /docs/storage/overview
Platforms Offer Postgres for your users: /platforms
PostGIS: /docs/extensions/postgis-related-extensions
PostgreSQL Tutorial: /postgresql/tutorial
Pricing: /pricing
Privacy Notice: https://www.databricks.com/legal/privacynotice
SOC 2 Certified: https://trust.neon.com/?itemUid=7bfa66da-33ab-49de-8391-e329738a1ae9
Security Compliance & privacy: /security
Security page: /security
Security: /security
Serverless App Autoscale with traffic: /use-cases/serverless-apps
Sign up: https://console.neon.tech/signup
Startups Build with Neon: /startups
Startups: /startups
Status Service status: https://neonstatus.com
Support: /docs/introduction/support
Terms of Use: https://www.databricks.com/legal/terms-of-use
TimescaleDB: /docs/extensions/timescaledb
Trust Center: https://trust.neon.com
Try Neon: https://console.neon.tech/signup
Use branch expiration.: /docs/guides/branch-expiration
What is Neon Built around Lakebase Postgres, by Databricks: /docs/get-started/why-neon
X.com: https://twitter.com/neondatabase/
YouTube: https://www.youtube.com/channel/UCoMzQTJSIr7-RU1QbomQI2w
adjusts compute: /docs/introduction/autoscaling
autoscale: /docs/introduction/autoscaling
built-in authentication: /docs/neon-auth/overview
contact us: /contact-sales
expiration times: /docs/guides/branch-expiration
history window: /docs/introduction/history-window
multi-AZ: /docs/introduction/high-availability
pg_vector: /docs/extensions/pgvector
read-heavy queries: /docs/introduction/read-replicas
real-time: /docs/introduction/monitoring-page
resetting them: /docs/guides/reset-from-parent

[content]
Pricing — Neon
Add files to your Postgres branches via Neon Object Storage, our S3-compatible object store
Neon
Product
Solutions
Docs
Pricing
Resources
Core Primitives
Lakebase Postgres
Serverless Postgres database
Auth
Authentication built into your database
Functions
Serverless compute next to your data
Object Storage
S3-compatible storage that branches
AI Gateway
One API for frontier and open-source models
Features
Lakebase Architecture
Storage-compute separation
Autoscaling
Automatic instance sizing
Branching
Faster Postgres workflows
Instant Restore
Instant recovery when mistakes happen
What is Neon
Built around Lakebase Postgres, by Databricks
Use cases
Serverless App
Autoscale with traffic
Multi-TB
Scale and restore instantly
Database per tenant
Data isolation without overhead
Build & operate
Platforms
Offer Postgres for your users
Dev/Tests
Production-like environment
Agents
Build full-stack AI agents
Learn
Blog
Technical posts & product updates
Case studies
Explore customer stories
Changelog
Product updates
Community
Connect on Discord
Startups
Build with Neon
Company
About us
The company and the mission
Careers
Join the team
Contact sales
Contact sales team
Security
Compliance & privacy
Status
Service status
Discord
22.8k
Log in
Sign up
Neon pricing
Get started for free. Pay per usage as you grow.
Neon pricing plans
Free
$0
Build and learn free with no time limits and no credit card required.
Try Neon
Lakebase Postgres
100 projects
100 CU-hrs monthly per project
0.5 GB of storage per project
Sizes up to 2 CU (8 GB RAM)
Unlimited team members
Backend
Managed Better Auth
Object Storage
Beta
Functions
Beta
Launch
Usage-based
Typical spend:
$
15
/mo
Based on:
Intermittent load
,
1
GB
Get started
Lakebase Postgres
100 projects
$0.106 per CU-hr
$0.35 per GB-month
Sizes up to 16 CU (64 GB RAM)
3-day metrics/logs in UI
Backend
Managed Better Auth
Object Storage
Beta
Functions
Beta
AI Gateway
Beta
Scale
Usage-based
Typical spend:
$
701
/mo
Based on:
High load
,
100
GB
Get started
Lakebase Postgres
1,000+ projects
$0.222 per CU-hr
$0.35 per GB-month
Sizes up to 56 CU (224 GB RAM)
SLAs, HIPAA, private network
Backend
Managed Better Auth
Object Storage
Beta
Functions
Beta
AI Gateway
Beta
Special programs
Agent Plan
App generation platforms
Custom rates and limits for thousands of databases.
Learn more
about
App generation platforms
Startup Program
Early-stage startups
Launch faster with up to $100k in credits.
Learn more
about
Early-stage startups
Open Source Program
Open source on Neon
Credits and funding for building on Neon.
Learn more
about
Open source on Neon
Projects and Branches
Projects
Branches per project
Included
Additional branches
Read more
Lakebase Postgres
Compute rates
Compute sizes
Autoscaling
Scale to zero
When inactive
Database storage
Root and child branches
History
Instant restore storage
History window
For instant restore (configurable)
Snapshots
Scheduled Backups
Backend
Managed Better Auth
Object Storage
Beta
Functions
Beta
AI Gateway
Beta
Network
IP Allow Rules
Private Networking
Private Link
Public network transfer
Egress
Private network transfer
Bidirectional
Account & Management
Monitoring retention
Window for metrics, logs
Metrics and Logs export
Datadog, OTel
Spending limits
Control your monthly spend
HIPAA Compliance
SOC 2 Report Access
Team members
Support Plans
Free
$0
/month
Get started
100
10
100 CU-hours
Per Project
Up to 2 CU (8 GB RAM)
After 5 minutes
when inactive
Free
0.5 GB per Project
Free
with limited window/size
Up to 6 hours
or 1 GB of data changes
1 snapshot
Up to 60k MAUs
No charges applied during beta, with usage limits
No charges applied during beta, with usage limits
5 GB included
1 day
Unlimited
Community (Discord)
Launch
Usage-based
Get started
100
10
$0.002 per branch-hour
$0.106 per CU-hour
Up to 16 CU (64 GB RAM)
After 5 minutes
can be disabled
$0.35 per GB-month
$0.20 per GB-month
based on volume of data changes during your selected history window
Up to 7 days
100 snapshots
$0.09/GB-month
Daily/Weekly/Monthly
$0.09/GB-month
Up to 1M MAUs
If you're planning to go beyond that,
contact us
No charges applied during beta, with usage limits
No charges applied during beta, with usage limits
No charges applied during beta.
Pricing will match model provider
500 GB per project included
then $0.10/GB
3 days
Unlimited
Billing Support
Scale
Usage-based
Get started
1,000
25
$0.002 per branch-hour
$0.222 per CU-hour
Up to 56 CU (224 GB RAM)
Configurable
$0.35 per GB-month
$0.20 per GB-month
based on volume of data changes during your selected history window
Up to 30 days
100 snapshots
$0.09/GB-month
Daily/Weekly/Monthly
$0.09/GB-month
Up to 1M MAUs
If you're planning to go beyond that,
contact us
No charges applied during beta, with usage limits
No charges applied during beta, with usage limits
No charges applied during beta.
Pricing will match model provider
500 GB per project included
then $0.10/GB
$0.01 per GB
14 days
Included
Available
Available
Unlimited
Multiple options
Included with every Neon database, on every plan, by default.
These are core platform capabilities that come out of the box with Neon.
High availability.
Neon’s storage is
multi-AZ
by default, without the need for HA standbys.
Read replicas.
Neon lets you offload
read-heavy queries
without added storage costs.
Autoscaling.
Neon automatically
adjusts compute
and storage based on demand, including on the Free plan.
Monitoring.
Built-in dashboards in the console give you
real-time
visibility into usage and performance.
Connection pooling.
All Neon databases can use pooled connections built on pgBouncer (up to
10,000 connections
).
Postgres extensions library.
You can add extensions like
pg_vector
,
PostGIS
,
TimescaleDB
, and many more.
Managed Better Auth.
Neon comes with
built-in authentication
based on Better Auth, with a one-click install.
GDPR and ISO compliance.
Included across all plans. Learn more on our
Security page
.
Your questions,
answered
Does Neon offer a backend now?
Yes. Alongside our serverless Postgres database, Neon now offers Managed Better Auth, Object Storage, Functions, and AI Gateway - a full backend suite that runs alongside your database and branches with it.
What does the beta label imply on Object Storage, Functions, and AI Gateway?
While these tools are in beta, they're not feature-complete - they're ready to deploy but expect some rough edges, evolving limits, and functionality that's still being built out (for example, monitoring coverage is still expanding, together with region availability). Billing is also paused during the beta phase.
What is a Neon project?
A project in Neon is the top-level container for your environment. Each project includes all branches, with your Postgres databases and (if you deploy them) your Object Storage buckets, Functions, Managed Better Auth endpoints, and AI Gateway access.
What is a CU?
A CU (short for Compute Unit) is Neon's way of representing
Postgres database compute size
. Neon databases
autoscale
, and CUs define how much CPU and memory your database is using at any moment - with each CU allocating approximately 1 vCPU and 4 GB of RAM.
What is a CU-hour?
A CU-hour is Neon's unit for measuring
Postgres database compute usage
. Because Neon databases scale to zero and autoscale, you're billed only for the database compute resources you actually use. In other words, your monthly database compute usage depends on:
How many compute endpoints are you running
How large your compute endpoints are (in CUs)
How long they run (in hours)
For a single compute, the calculation works similar to this:
Monthly CU-hours = [average CU size] × [number of hours the compute runs in the month]
Monthly compute cost = [monthly CU-hours] × [CU-hour price]
The CU-hour price depends on your pricing plan:
Launch plan: $0.106 per CU-hour
Scale plan: $0.222 per CU-hour
Remember that when your database is idle, compute can scale down to zero, so you don't consume CU-hours while it's not running.
Learn more about Neon's billing.
What does 100 CU-hours per project give me on the Free plan?
On the Free plan, each project gets 100 CU-hours of
database compute
per month, and compute automatically scales down to zero when idle. What this means in practice:
You can create up to 100 projects, each with its own independent 100 CU-hour allowance
CU-hours are only consumed while a database is actively running queries. When a project is idle, compute scales to zero and uses no CU-hours
Usage is typically spread across short bursts of activity, not continuous runtime
A realistic example for a single project:
The database runs at an average of 1 CU for ~3 hours per day. It scales down to zero the rest of the time
Over a month, this uses roughly 90 CU-hours, staying within the Free plan limits for that project
This model is designed to make it practical to have many small or intermittent databases (for development, demos, previews, or experiments) without being forced into an upgrade.
Learn more about our Free Plan philosophy.
Is Object Storage, Functions, or AI Gateway usage included in my Free plan CU-hours?
No. CU-hours are specific to Postgres database compute. Object Storage, Functions, and AI Gateway will have their own usage limits that will be published before GA. During the beta phase, they are free to use within the guardrails we've set to prevent abuse.
How are the workload cost estimates calculated?
The typical monthly cost estimates shown in our pricing plans are based on representative database workloads that reflect common usage patterns across different application types. These estimates cover Postgres compute and storage only - they don't factor in Object Storage, Functions, or AI Gateway usage, which are billed separately and currently free of charge during beta.
Each estimate combines two components:
Database compute cost:
Based on the specified CU-hours per month.
Database storage cost:
Based on the specified amount of database storage in GB.
These estimates help you compare typical workloads across plans.
Here's a detailed breakdown of each of the workload sizes and what they represent:
Intermittent Load:
140 CU-hours compute, 1 GB-month of storage. Typical of a small database that doesn't need to run 24/7.
A databse using 140 CU-hours compute per month can scale to zero when idle, and start back up in 350ms when it's needed. When it's running it is set to a minimum size of 0.25 CU but can scale up to 2CU when needed.
Low Load:
190 CU-hours compute, 5 GB-month of storage. A small database that
does
need to run 24/7.
Once scale to zero is disabled, the minimum CU-hours a database can use in a month is 187.5
(750 hours in a month x 0.25 minimum CU size = 187.5)
so this example represents a database that has scale to zero disable but only occasionally needs to scale above the 0.25 minimum size. Good for small production applications and databases that need to be always-on for features like real-time sync.
Medium Load:
720 CU-hours compute, 10 GB-month of storage. Representative of a constant-load application database.
As you can see from the autoscaling chart above, 720 CU hours translates to a database that scales between 0.5 and 4 CU based on load.
High Load:
3,000 CU-hours compute, 100 GB-month of storage.
As an example, a database that is scaling between 3 CU and 7 CU will often use around 3000 CU hours in a month. This level represents production applications with sustained traffic, higher data volumes, and more complex queries requiring consistent compute resources.
XL Load:
6,000 CU-hours compute, 1,000 GB-month of storage.
A database scaling between 6 and 14 CU can use in the range of 6,000 CU hours in a month. This is representative of large-scale production workloads with high traffic volumes, extensive datasets, and applications requiring significant compute capacity and storage.
Your actual costs will vary based on:
How much your database autoscales based on actual query load
How long your computes run before scaling to zero
Your actual data size and number of branches
Your configured history window for instant restore (affects History storage costs)
Remember that Neon bills based on actual usage, not estimates. Use these workload examples as reference points, then monitor your usage in the
Neon Console
to understand your real costs.
Learn more about how Neon billing works.
How are Object Storage, Functions, and AI Gateway billed?
They aren't billed yet. Usage is free of charge for all three during beta, with rate and usage guardrails in place. Public pricing for Object Storage and Functions will be announced before general availability (GA).
AI Gateway requires a paid Neon plan (Launch or Scale) to access, and while it's also free of charge during beta, its pricing model is already public - Neon will charge the same per-token rate as the underlying model provider, with zero markup. Exact per-model rates will be published before billing begins.
What does "no monthly minimum" mean on paid plans?
Neon's paid plans don't require a minimum monthly spend or base fee. You're billed purely based on usage. If one month you barely use Neon, your bill might be just a few dollars.
For example, if your databases are mostly idle that month, or you only run them briefly for development or testing, you'll only pay for the compute and storage actually consumed during that time. Remember that Neon databases scale to zero by default.
Are the Free Plan quotas for database usage included in the paid plans?
No. When you're on a paid plan, database usage starts metering from zero for both compute and storage. Free plan quotas don't apply once you upgrade. Instead, you're billed purely based on actual usage, at the rates of your paid plan.
You should consider a paid plan if:
You expect higher or more sustained usage than what's included per project on the Free plan
You care about production guarantees, such as consistent availability, predictable performance, and never having your database paused due to usage limits
If your usage fits comfortably within the Free plan and you're not running a production workload, there's no reason to upgrade. The Free plan is designed to be genuinely useful for development and prototyping.
Learn more about our Free Plan philosophy.
How is Postgres database storage billed in Neon?
In Neon, you don't provision or manage database storage in advance. It scales automatically and invisibly as your data grows. At the end of each month, you're billed for the database storage actually consumed per project, measured in GB-months.
Neon bills storage usage using two separate metrics:
History storage (or instant restore storage)
Instant restore
relies on Neon retaining a history of database changes so you can restore a branch to a previous point in time, create branches from past states, run Time Travel queries, and more. How long that history is kept is controlled by the
history window
on
Settings → Instant restore
—see
History window
(1 day by default on paid plans).
History
storage is billed based on the amount of Write-Ahead Log (WAL) retained within that history window, at $0.20 per GB-month on paid plans. This is billed separately from your regular database storage.
If you don't need deep recovery or long Time Travel, shorten the history window to reduce costs.
Database storage (root and child branches)
This is the storage used by your database data itself. Since Neon databases can branch, this is how branches contribute to database storage:
Root branches are billed based on their actual data size (for example, 5 GB)
Child branches
might
be billed based on the minimum of: the accumulated data changes since the branch was created, or the underlying storage footprint, which is zero if the branch is still within the history window used for instant restore (in this case, the child branch effectively shares storage with its parent).
The SUM of both components will be billed as your database storage at $0.35 per GB-month.
What this implies:
A child branch that has no data changes compared to its parent and is still within the
history window
does not incur additional database storage costs.
As a child branch accumulates changes over time, its storage usage increases.
If a child branch falls out of the history window, it becomes as expensive as a root branch, since it no longer shares storage with its parent.
To keep database storage costs low, child branches are best kept short-lived - for example, by setting
expiration times
,
resetting them
frequently, or deleting branches when they're no longer needed.
How are extra branches billed?
Each Neon plan includes a set number of branches per project at no additional cost (10 branches per project in Launch, 25 branches per project in Scale) but you can create and delete branches freely within your plan's included allowance:
If the total number of concurrent branches in a project exceeds your plan's allowance, the extra branches are billed as branch-months, prorated hourly.
The price is $1.50 per extra branch-month (≈ $0.002 per hour)
You're only billed for branches that exceed your included limit, and only for the time they exist.
Example: The Launch plan includes 10 branches per project. If you already have 10 branches but create 2 additional branches and keep them for 5 hours each, that'd be 10 extra branch-hours total: 10 × $0.002/hour = $0.02
How to avoid extra branch charges
Use branch expiration.
Set automatic deletion times on temporary branches so they're cleaned up when no longer needed.
Automate cleanup. Use the
Neon API
or
Neon CLI
to periodically delete unused branches and stay within your included allowance.
How is Managed Better Auth billed?
Neon Managed Better Auth is included at no additional cost for all Neon databases until you reach 1 million monthly active users (MAU). If you surpass that threshold, a member of our team will reach out to discuss pricing.
On the Free plan, Managed Better Auth is included for up to 60,000 MAU.
How can I control my Postgres database costs (compute and storage consumption)?
Database compute is often the most variable part of a monthly bill. For Neon databases, the most effective way to control compute costs is to configure maximum autoscaling limits and scale-to-zero.
Autoscaling limits act as a built-in cost ceiling: your database will never scale beyond the limit you set, even during traffic spikes. If you want to prioritize performance over costs in a particular compute endpoint (e.g. production), choose a higher limit. If you want to optimize for cost predictability, set a lower one.
Learn how to configure autoscaling limits.
Another effective way to control database compute costs is to ensure scale to zero is enabled for all non-production branches. When a branch is idle, compute scales down automatically, so you're not charged for unused databases.
Learn about scale to zero.
To manage database storage costs, regularly clean up unused branches, snapshots, and projects, and avoid retaining a large history window for instant restore if your use case does not require it.
Learn more about optimizing storage usage.
Do you offer credit programs for startups?
Early startups that have received venture funding are eligible to apply to our Startup Program.
Learn more and apply here.
ASK AI
Still have questions? Ask our AI.
It knows Neon inside and out.
Get Answers
Neon
Neon is part of the Databricks Platform
Neon status loading...
© Neon 2026. All rights reserved. Apache, Apache Spark, Spark, the Spark Logo, Apache Iceberg, Iceberg, and the Apache Iceberg logo are trademarks of the
Apache Software Foundation
.
Privacy Notice
Terms of Use
Neon Platform Terms
Modern Slavery Statement
California Privacy
Company
About
Blog
Careers
Contact Sales
Security
Resources
Docs
Changelog
Support
Community Guides
FAQs
PostgreSQL Tutorial
Startups
Community
Discord
GitHub
X.com
LinkedIn
YouTube
Compliance
CCPA
Compliant
GDPR
Compliant
ISO 27001
Certified
ISO 27701
Certified
SOC 2
Certified
HIPAA
Compliant
Compliance Guide
Neon’s Sub Contractors
Trust Center
