Databases

Managed Postgres, pgvector, MySQL, Valkey, and ClickHouse.

Create one from Databases → New. Pick the engine, a version, a name, a region, and a plan. The form grays out regions that cannot take that plan right now.

Redis is not offered. Use Valkey when you need a Redis-compatible store. The default env key for Valkey is stillREDIS_URL, so existing apps keep working.

Plans

Every plan includes local NVMe. Discovery shares CPU. General Purpose and High Performance use dedicated vCPU. A -L suffix is the same compute with double the disk. See Pricingfor live numbers.

Attach to an app

On the application Environment tab, attach the database and choose which connection fields become env vars. Those values are injected on the next deploy. Detach or edit the key names there. Manage the database itself from the Databases list.

The app and the database must be in the same region. The API rejects a cross-region attach.

Cluster, backups, access

Postgres, pgvector, and MySQL can add read replicas and an HA standby. Valkey can do HA. ClickHouse can run as a three-node cluster on an empty database. Those tabs appear only when the engine supports them.

Backups are opt-in on engines that support them (not Valkey, and not a ClickHouse cluster). Restore creates a new database. It does not overwrite the original.

Overview shows private access on the internal hostname, and optional public TLS. Detach every app before you delete a database.

Previews

A preview environmentgets a fresh database. It is not a clone of production data.