Create it inside a project.
Choose a project and open its Database tab. Plan allowances are shared across your organization, so you can see what is available before creating another database.
The data belongs with the application
Give your application a managed Postgres database. Keep the connection beside your code and environment settings, with room for your first real users.
Add PostgresManaged Postgres. A connection string. Your choice of database client.
DATABASE_URLKeep the setup together
Use PostgreSQL with your application code. Bring your preferred client, ORM, and migrations.
Choose a project and open its Database tab. Plan allowances are shared across your organization, so you can see what is available before creating another database.
Use the connection string from your project. Store it as a server-side environment variable instead of committing it to Git or exposing it in browser code.
Connect with a PostgreSQL client or ORM such as Drizzle or Prisma. Your schema and migration workflow remain part of your codebase.

A considered default
Keep credentials private, run migrations deliberately, and track your storage allowance as the application grows.
Explore the developer workflowA few useful answers
The database count is per organization. Free includes 1 database up to 1 GB. Pro includes 10 databases, each up to 10 GB.
Your application owns its schema and migrations. Use your existing migration tools and test changes before applying them to production data.
Do not expose a Postgres connection string in browser code. Put database access behind server-side code with your application's authentication and authorization rules.