Skip to main content
Every project can provision exactly one managed Postgres database. It lives at the branded endpoint db.korve.app; you never see (or manage) the machinery behind it.

​
Provision

The full connection string — including the password — is shown exactly once and is never retrievable later. Store it immediately, typically as a project environment variable:
API: POST /v1/orgs/{orgId}/projects/{projectId}/database (admin role, active billing). MCP: await korve.database.provision({ orgId, projectId }). See the Database API.

​
Inspect

Returns status (provisioning | ready | failed), host, port, database name, and user — never the password.

​
Rotate

Issues a new password and prints the new connection string once. The old password stops working immediately — update DATABASE_URL and redeploy in the same breath.

​
Delete

Deletes the database and all of its data. This cannot be undone.

​
Connecting

Connect with any standard Postgres client using the connection string.
  • Connections work from anywhere — external runtimes, always-on apps, and code inside scale-to-zero apps alike. TLS verifies fully against db.korve.app.

​
Billing

The project database meters database.compute (per month) and database.storage (per GB-month) — exact prices on the rate card.