A Neon project starts with one database (neondb by default) on its root branch. You can add more databases to that branch (or any child branch) from the Roles & Databases tab in the Console, with the Neon CLI, or with a standard CREATE DATABASE statement. Each branch supports up to 500 databases.

Create the database

  1. Open your project in the Neon Console.
  2. Select Branches in the sidebar.
  3. Click the branch where the database should live.
  4. Open the Roles & Databases tab.
  5. Click Add database.
  6. Enter a name and pick an owner role.
  7. Click Create.

The owner role you pick becomes the database owner and has full privileges on it. See Manage databases for screenshots.

After it's created

  • The new database lives on the branch you created it in. If you create a child branch later, this database is copied to the child too.
  • The role you picked owns the database and has CREATE on its public schema. Other roles need an explicit GRANT CREATE ON SCHEMA public TO <role>; to create objects there (Postgres 15 and up).
  • Reserved names (postgres, template0, template1) aren't permitted.
  • Connect to it by clicking Connect on the Project Dashboard and picking the new database in the Connection Details modal. The connection string updates automatically.

One database per app, or many?

A single Neon project can hold many databases, but in most apps you'll have one database per logical app and use schemas to organize data inside it. For multi-tenant patterns where each customer needs full isolation, consider one project (not just one database) per tenant. See Multitenancy.

Manage databases end to end

Includes creating, renaming, deleting, transferring table ownership, and the API reference.

Read the docs