Database
Neon
Run managed PostgreSQL with compute and storage managed separately.
Sources checked
Our recommendation
When to choose it
Start with Neon for this database role when your app already has a backend and needs PostgreSQL. Decide separately which other Neon services to adopt.
A good fit for
- A PostgreSQL database for an existing app backend
- SQL projects needing an independent database provider
Choose something else when
Choose Turso instead when SQLite compatibility or local-first synchronization is an actual requirement.
Watch out for
- A database connection string is a credential. Keep privileged connections on the server.
- Neon also offers backend services; do not assume this database choice automatically configures authentication or storage.
How costs work
Usage-based compute and storage plans
Check current project settings, compute behavior and storage usage before estimating a monthly bill.
Check current official terms and pricing ↗This is a pricing model, not a monthly quote. Check your region, intended usage and current plan before buying.
What connects to it
- PostgreSQL clients and SQL tools
- Server and serverless application backends
These are technical connections you can configure. Selecting a card creates no accounts or resources.
Compare the alternatives
Learn the boundary before you connect it
Lessons open through your account and the kits you own.
Check the evidence
Feature sources were reviewed on 4 Oct 2026. Plans and availability can change.
- Postgres role ↗
Separation of PostgreSQL compute and storage.
- Billing model ↗
Usage-based compute and storage model; check the current pricing page for amounts.
- Broader backend ↗
Neon includes additional backend services; database selection is one role.