How do I create a new project in Neon?

A Neon project is the top-level container for your database environment. Each project has its own root branch, default database, default role, and primary compute. To create one, click New Project in the Neon Console and pick a name, Postgres version, and AWS region. Or use the Neon CLI with neon projects create. Project limits depend on your plan: the Free plan and Launch plan get 100 projects, the Scale plan gets 1,000.

Create the project

Sign in to the Neon Console.
Click New Project.
Fill in:
- Project name (up to 64 characters)
- Postgres version (default is the latest supported)
- Region (pick an AWS region closest to your application)
Click Create Project.

You'll land on the Project Dashboard with the connection string ready in the Connect widget. See Create a project.

What gets created

Every new project comes with:

A root branch (named production in the Console, main via API and CLI)
A primary read-write compute, defaulting to 0.25 CU (≈1 GB RAM)
A database (neondb by default)
A role named after the database (for example, neondb_owner)

For more on what's included, see Default resources.

Troubleshooting "create project" failures

The most common reason a project creation fails is hitting your plan's project limit:

Plan	Project limit
Free plan	100
Launch plan	100
Scale plan	1,000 (request an increase via support)

If you're at the limit:

Delete unused projects from Settings > Delete in the Console. Deleted projects can be recovered within 7 days via the API or CLI.
Or upgrade to the Scale plan for the higher limit.

Other reasons creation can fail:

The chosen region is temporarily unavailable. Try a different region or retry in a few minutes.
Network issues between the Console and the Neon control plane. Check neonstatus.com.

If neither applies and the error message isn't clear, ask in the Neon Discord or open the Help menu in the Console. Include the request ID shown in the error if you have one. Scale plan users can also open a support ticket.

One project per app or per tenant

For most workflows, create a separate project for each application or each customer. That gives each one its own isolated storage, computes, and branches, and keeps blast radius small if something goes wrong. See Multitenancy for patterns.