Neon
Serverless Postgres that separates storage from compute, with copy-on-write branching and compute that suspends when idle.
- database
- Yes
- Not documented
- 8 AWS regions: N. Virginia, Ohio, Oregon, Frankfurt, London, Singapore, Sydney, São Paulo. A project's region is fixed at creation and cannot be changed.
Who it suits.
Workloads that are idle most of the time, and teams who want a real database per pull request. Compute suspends after five minutes and storage is billed separately, so a staging branch costs almost nothing while nobody is using it.
Consider something else if…
You need predictable monthly billing. Usage pricing with no minimum fee cuts both ways, and a runaway query on an autoscaling compute is billed at the rate it ran.
Editorial · Palash Bagchi · approved
What the documentation says.
Each value below links to the page it was read from, with the sentence it came from. Criteria Neon does not publish are not listed.
Pricing
Free tier
Yes
Sources (1) →Sources ↓
- Neon plans — Neon Docs ↗
“On the Free plan, there is no monthly cost. You get usage allowances for projects, branches, compute, storage, and more, for $0/month.”
Read 2026-09-05 · official pricing
Pricing model
Usage-based with no minimum monthly fee on paid plans: $0.106/CU-hour compute and $0.35/GB-month storage on Launch, $0.222/CU-hour on Scale
Sources (1) →Sources ↓
- Neon plans — Neon Docs ↗
“On Launch and Scale plans, you pay only for what you use; there's no minimum monthly fee. Usage for compute, storage, extra branches, and other features is billed at the published rates”
Read 2026-09-05 · official pricing
Egress over allowance
5 GB per project included on Free; 500 GB per project included on Launch and Scale, then $0.10/GB
Sources (1) →Sources ↓
- Neon plans — Neon Docs ↗
“Public network transfer 5 GB per project included 500 GB per project included, then $0.10/GB 500 GB per project included, then $0.10/GB”
Read 2026-09-05 · official pricing
Limits
Storage (entry plan)
No included allowance on the Launch plan; storage is metered at $0.35/GB-month. The Free plan includes 0.5 GB per project.
Sources (1) →Sources ↓
- Neon plans — Neon Docs ↗
“Storage 0.5 GB/project $0.35/GB-month $0.35/GB-month”
Read 2026-09-05 · official pricing
Execution
Managed connection pooling
Supported
Sources (1) →Sources ↓
- Connection pooling — Neon Docs ↗
“Neon uses PgBouncer to provide connection pooling, enabling up to 10,000 concurrent connections.”
Read 2026-09-05 · official docs
Infrastructure
Scales to zero
Supported
Sources (1) →Sources ↓
- Neon plans — Neon Docs ↗
“Scale to zero After 5 min After 5 min, can be disabled Configurable (1 minute to always on)”
Read 2026-09-05 · official docs
Regions
8 AWS regions: N. Virginia, Ohio, Oregon, Frankfurt, London, Singapore, Sydney, São Paulo. A project's region is fixed at creation and cannot be changed.
Sources (1) →Sources ↓
- Regions — Neon Docs ↗
“Each Neon project exists in exactly one region. Your database runs in that region. You cannot change the region for an existing project. If you need your data in a different region, you create a new Neon project in that region and migrate your database there.”
Read 2026-09-05 · official docs
Data
Engine
PostgreSQL
Sources (1) →Sources ↓
- Connection pooling — Neon Docs ↗
“Each Postgres connection creates a new process in the operating system, consuming memory and CPU resources. Postgres limits the number of connections based on available RAM.”
Read 2026-09-05 · official docs
Connection limit
Scales with compute size: 104 direct connections at 0.25 CU (1 GB RAM), 419 at 1 CU, 2517 at 6 CU; up to 10,000 through the pooler
Sources (1) →Sources ↓
- Connection pooling — Neon Docs ↗
“Neon uses PgBouncer to provide connection pooling, enabling up to 10,000 concurrent connections. [...] In Neon, this limit is defined by max_connections, which varies by compute size: Compute size (CU) RAM max_connections 0.25 1 GB 104 0.50 2 GB 209 1 4 GB 419”
Read 2026-09-05 · official docs
When idle
Compute suspends after 5 minutes idle on Free and Launch, and can be disabled on Launch; configurable from 1 minute to always-on on Scale. The database is not deleted or paused — the next query restarts the compute.
Sources (1) →Sources ↓
- Neon plans — Neon Docs ↗
“Scale to zero After 5 min After 5 min, can be disabled Configurable (1 minute to always on)”
Read 2026-09-05 · official docs
Database branching
Supported
Sources (1) →Sources ↓
- Neon plans — Neon Docs ↗
“Each Neon project is created with a root branch, like the main branch in Git. [...] You can create child branches for testing, previews, or development. [...] Free: 10 branches/project Launch: 10 branches/project Scale: 25 branches/project”
Read 2026-09-05 · official docs
Point-in-time recovery
History window of 6 hours up to 1 GB-month on Free, up to 7 days on Launch, up to 30 days on Scale
Sources (1) →Sources ↓
- Neon plans — Neon Docs ↗
“History window 6 hours, up to 1 GB-month Up to 7 days Up to 30 days”
Read 2026-09-05 · official pricing
Read replicas
Supported
Sources (1) →Sources ↓
- Neon Read Replicas — Neon Docs ↗
“Neon read replicas are independent computes designed to perform read operations on the same data as your primary read-write compute. Neon's read replicas do not replicate or duplicate data. Instead, read requests are served from the same storage”
Read 2026-09-05 · official docs