Databases
Databases provisions managed PostgreSQL databases within a Project. It provides a resource API for creating a database, inspecting its provisioning state, and preparing a connection for runtime use.
Why use Databases?
An application needs persistent storage for its records. Databases gives that storage a Project-owned identity and a managed provisioning path, with connection credentials that can be passed to a runtime through Secrets.
What you can do
- Create a Database with a name and storage allocation.
- Inspect its provisioning status, endpoint metadata, or reported error.
- List, rename, and delete Databases within the Project.
- Create a database connection stored as an immutable Secret version.
Core concepts
A Database is an isolated PostgreSQL resource with its own endpoint and provisioning state. The connection operation stores DATABASE_URL in Secrets and returns the Secret and version references.
Use the returned Secret reference when configuring the application's runtime. The connection response contains metadata references rather than the connection value. Your application uses PostgreSQL to read and write its records; the Databases API manages the database resource.
Use Databases
Read the CLI reference for command availability or the API reference for provisioning and connection operations.