PostgreSQL beta
Review PostgreSQL Database Hosting for an app
DB Alpha is proven for approved beta and internal workloads; public self-service provisioning remains gated.
Understand the access boundary
- Public checkout and portal creation do not provision a PostgreSQL database yet.
- Approved beta and internal workloads use an explicit DB Alpha project and tenant scope.
- Review the launch gate before requesting any owner-controlled provisioning.
Use the connection path
Approved DB Alpha app bindings can receive DATABASE_URL and POSTGRES_URL through protected references. Secret values remain redacted in the portal and logs.
The approved beta path supports owner-only TLS verify-full access for psql or pg_dump. Public connection reveal is gated; never copy a connection into source control or support messages.
Run migrations deliberately
Your application or release process owns schema migrations, indexes, queries, and seed data. Test destructive changes before running them against production data.
A healthy database resource does not prove that the application schema is current. Verify a path that reads and writes the expected tables.
Plan and verify recovery
Approved beta workspaces can use the owner-only TLS connection with pg_dump and verify restored data before relying on it.
Public self-service deletion and database export controls are not enabled yet. Preserve the source and recovery evidence for any approved workload.