services

Engines, sizing, connection strings and backups.

Managed databases

Create a database from Databases → New database, or over the API. The engine determines the image, the default port and the connection-string shape.

EngineDefault portNotes
postgres5432Replicas supported; pgvector available as a variant.
mysql3306Replicas supported.
mongodb27017Replica sets, one primary plus secondaries.
redis6379In-memory; persistence optional.
vector5432PostgreSQL with pgvector for embeddings.

Sizing

A database is shaped by four numbers: CPU (500m, 1, …), memory in MB, storage in GB and replica count. Storage can be grown later; shrinking is not supported because it risks data loss.

Connecting

Connection details appear once the resource reports ready. Prefer the injected environment variables over hard-coded hosts:

bash
DATABASE_URL=postgresql://user:pass@orders-db.databases.svc:5432/orders

Databases are reachable from services inside the same organization only. There is no public ingress by default.

Backups

Managed engines take automated snapshots on a schedule and keep them for the retention window of your plan. Restoring creates a new database from the chosen snapshot rather than overwriting the original.

Deleting

Delete is destructive and immediate. The API requires the resource name to be confirmed in the request body so a mistyped id cannot destroy a live database.