Consider it for
Developers needing Postgres preview branches or variable, intermittent database workloads.
Databases · Written evaluation
Neon
Managed Postgres with branching, autoscaling and compute metered by active capacity.
Plan at a glance
Plans & sources ↓100 projects; 100 CU-hours/month per project; 1 GB database storage/project; up to 2 CU compute; unlimited team members.
Limits to check
Paid compute and storage meter from zero; free quotas do not carry into paid plans. History, branches, egress and backend services can add cost.
Official sources read 9 October 2026. The evaluation below is editorial judgement based on documentation; no hands-on product test was performed.
Research scope & testing evidence
Our evaluation
Neon is a strong candidate when database environments need to follow application development: preview branches, experiments and intermittent workloads are central to the choice. Branching makes a safer workflow possible, but the team must still decide which data can enter a preview and when that branch expires. Autoscaling and scale-to-zero can avoid paying for idle capacity; always-active applications should calculate their real compute hours rather than extrapolate from a tiny demo. I would evaluate connection handling, wake-up behavior and restore requirements before choosing a production plan. The current pricing page also offers backend services beyond Postgres, but those have separate usage allowances. Keep the database estimate explicit, then add storage history, network traffic and any other services instead of treating one headline example as the complete bill.
Fit and limits
Fit and limits
Check before committing
Paid compute and storage meter from zero; free quotas do not carry into paid plans. History, branches, egress and backend services can add cost.
What the documentation confirms
What the documentation confirms
- Postgres compute can autoscale and scale to zero when inactive.
- Branches, read replicas and pooled connections are documented platform features.
- Free now includes 100 projects, each with 1 GB database storage and 100 CU-hours/month.
Selected official documents read 9 October 2026. Access can depend on plan, region and account.
Price and billing scope
| Plan or charge | Observed price | Billing, allowance and limits |
|---|---|---|
| Free | $0 within Free project allowances | Per-project quotas, scale-to-zero and free-plan limits apply. 100 projects; each gets 100 CU-hours/month and 1 GB database storage. Official source ↗ |
| Launch compute | $0.106/CU-hour on Launch | CU size × active hours. Storage, history, network and other services are separate. Postgres compute only; no monthly minimum on current paid plans. Official source ↗ |
| Paid database storage | $0.35/GB-month for database storage | Separate from compute and history storage. Launch/Scale database storage. Official source ↗ |
| Scale compute | $0.222/CU-hour on Scale | Usage rate, not a fixed monthly subscription. Scale Postgres compute; advanced production scope. Official source ↗ |
These are selected published charges, not a complete account bill. Check eligibility, tax, add-ons and the price shown for your account before paying.
Recorded editorial criteria
Recorded editorial criteria
These are the previously recorded editorial opinions used in the directory. They have no individually recorded assessment date and were not rescored during this documentation refresh. They are not product-test results.
| Functionality | 9/10 |
|---|---|
| Pricing value | 9/10 |
| Ease of use | 9/10 |
| Reliability | 8/10 |
| Founder fit | 9/10 |
Try one complete task
Create a small application database, branch it for a migration preview, run the change and restore it. Measure active CU-hours and inspect connection behavior after an idle interval.
Create a trial worksheet →Compare requirements
Edited by Clinton Feyisitan · Evidence policy · Suggest a correction