PostgreSQL wire protocol
Applications use pooled PostgreSQL connections with trusted TLS on the owner-controlled connection path.
Managed PostgreSQL
Create PostgreSQL. Copy the connection string. Keep building.
Start at 0.25 CU, scale to zero when idle, and wake on the next connection. Usage, recovery, and destructive controls stay in the same workspace.
The useful defaults
A real database without the infrastructure ceremony.
Reserve the database immediately, copy its secure URL, and let compute finish in the background. Advanced lifecycle work stays available without crowding creation.
Protected app bindings
App bindings use protected connection references. Secret values are not stored in ordinary portal state.
Lifecycle operations
Create, query, pause, resume, rotate credentials, and delete from one customer-owned lifecycle.
Encrypted logical backups
Encrypted backup and isolated restore copies protect the primary database from restore work.
What happens next
PostgreSQL by itself or beside your app.
Start with a standalone database or add PostgreSQL beside an application. Both use the same workspace wallet, ownership boundary, and metered database engine.
Create and connect
One-click reservation, pooled TLS, owner-only connection reveal, SQL workbench, usage, pause, resume, and recoverable deletion.
Scale when needed
Start at 0.25 CU and scale within your plan. Idle databases release compute after five minutes and wake on connection.
Not promised
Neon-compatible branching, PITR, HA, or an independent elasticity promise.
Your database can be ready before your environment file is.
Name it, choose a compute ceiling, and copy the secure connection from one workspace.