serverless Postgres

Neon

Neon is a serverless Postgres product that branches databases like code. This profile covers what it does, how it is priced, and where it stops being the right choice.

What it does

Neon sits in the serverless Postgres layer. The core of the product is straightforward: branches databases like code. Around that core the vendor has built the things a team needs before it can trust the system in production — access control, audit history, and a way to see what changed and when.

How it is priced

Pricing is per seat for small teams and per unit of usage once volume matters. The line that surprises people is usually the second one: storage, bandwidth or API calls scale faster than headcount, so a plan that looked cheap at ten users can look different at a hundred. Read the usage table before committing.

Where it fits

Choose Neon when the constraint it removes is the constraint you actually have. A team fighting schema migrations is not helped by cheaper storage; a team fighting storage costs is not helped by faster deploys.

Sources

Neon public documentation, pricing page, and product changelog, read October 2026.