Console And Connections

Many Prisma Postgres tasks are quickest in the Console: viewing Studio data, checking metrics, and retrieving connection details. This avoids unnecessary API or CLI work for simple operational tasks.

Console workflow

1. Open https://console.prisma.io.
2. Select workspace and project.
3. Use dashboard metrics for usage and billing visibility.
4. Open the Studio tab in the sidebar to inspect and edit data.

Local Studio

You can also inspect data locally:

Linking an existing project

If the Prisma Postgres database already exists, link the local project instead of provisioning a new one:

For CI or non-interactive usage:

This command updates or creates .env with DATABASE_URL. If the project is already linked, use --force to re-link. After linking, run prisma generate, then prisma migrate dev if you need to apply the schema.

Connection setup

For direct PostgreSQL tools and drivers:

• Generate/copy direct connection credentials from the project connection UI.
• Use the resulting PostgreSQL URL as DATABASE_URL for pg and @prisma/adapter-pg.
• For Prisma Postgres direct TCP, include sslmode=require.

Typical direct TCP format:

Management API connection responses expose both endpoints.direct (db.prisma.io:5432) and endpoints.pooled (pooled.db.prisma.io:5432); prefer those fields over the deprecated flat connectionString. Connection secrets are shown once at creation (one-time view); store them immediately.

Adapter choices

• Standard Node.js apps: prefer @prisma/adapter-pg with the direct TCP URL above.
• Edge/serverless runtimes: use @prisma/adapter-ppg with @prisma/ppg only when you specifically need the Prisma Postgres serverless driver.

References

• Prisma Postgres overview (opens in a new tab)
• Viewing data (opens in a new tab)
• Direct connections (opens in a new tab)