Neon is a complete set of cloud backend primitives built around Lakebase Postgres. You create a project, copy a connection string, and connect. There's no instance to size and no OS to patch. Compute autoscales between bounds you set and scales to zero when idle.

How it works

The lakebase architecture separates storage from compute, so a database isn't tied to a fixed instance:

  • Autoscaling. Compute moves between a minimum and maximum CU based on load: up to 2 CU on the Free plan and up to 16 CU on the Launch and Scale plans. The Scale plan also offers fixed sizes up to 56 CU. See Autoscaling.
  • Scale to zero. Compute suspends after 5 minutes of inactivity and resumes within a few hundred milliseconds on the next query. The Free plan keeps the 5-minute timeout and can't disable it. The Launch plan can turn scale to zero off. The Scale plan is configurable from 1 minute to always on. See Scale to zero.
  • Branching. A new branch is a copy-on-write clone of your database, ready in seconds. Use it for schema changes, preview environments, or recovering from a bad migration.
  • Usage-based pricing. On the Launch plan, compute is $0.106/CU-hour and storage is $0.35/GB-month, with no monthly minimum. When compute is suspended, CU-hours stop; storage continues to bill.

Provisioning a database

With the Neon CLI:

neon projects create --name my-app --set-context
neon connection-string

The second command prints a Postgres connection string you can paste into DATABASE_URL. --set-context saves the new project as the CLI's default, so later commands don't need --project-id. You can do the same through the Neon API or the Console.

What Neon manages

OperationOn Neon
Instance sizingAutoscaling between min and max CU
Connection poolingBuilt-in PgBouncer on every compute
BackupsInstant restore from change history, plus snapshots
Read replicasAdd via API or Console; replicas share the primary's storage
Postgres minor releasesApplied automatically at the next compute restart
Patching and OS updatesManaged by Neon

What you manage

Schema, queries, indexes, roles, and which extensions to enable. Lakebase Postgres supports common extensions, including pgvector, PostGIS, and pg_stat_statements; see the extension reference. Major version upgrades are also on you: each project is locked to its major version, so you create a new project and migrate the data.

How this differs from other "serverless" Postgres options

CapabilityNeonAurora Serverless v2RDS for PostgresSupabase
Scales to zeroYes, by default after 5 min idleYes, when min capacity is 0 ACUsNoNo on paid plans; the Free plan pauses projects after low activity over 7 days
AutoscalingUp to 2 CU (Free plan), 16 CU (Launch/Scale)Min/max ACU range per clusterManual resize, brief downtimeManual compute size change, usually with under 2 minutes of downtime
Database branchingBuilt in, copy-on-writeCloning via copy-on-writeNone nativeBranching for preview environments
Billing modelUsage-based (CU-hour, GB-month)Usage-based (ACU-hour) plus storageInstance-hour plus storagePlan fee plus per-project compute hours
Connection poolingBuilt-in PgBouncerRDS Proxy, set up separatelyRDS Proxy, set up separatelyBuilt-in Supavisor pooler

Neon and Aurora Serverless v2 with a minimum of 0 ACUs both stop billing compute while idle, and both still bill storage. On Neon, the pooler is built in; on Aurora, RDS Proxy is a separate resource you set up.

Try Lakebase Postgres

Create a Neon project in seconds and connect from your app with a standard Postgres connection string.