Data

Availability: Available

Postgres, MySQL, or Redis in your project

Create Postgres, MySQL, or Redis inside your private project and bind it to a container app through framework-aware environment variables. Backup and recovery coverage is stated by engine.

What you get

Three engines, one workflow

Create Postgres, MySQL, or Redis from the portal, then list, inspect, link, and delete each one exactly like a container.

Service binding

Connect a database to a container app and its credentials arrive as secret-backed variables like DATABASE_URL, SPRING_DATASOURCE_*, or PG*/DB_*/REDIS_*.

Framework-matched contract

The env contract adapts per runtime, so Spring reads SPRING_DATASOURCE_*, Node reads DATABASE_URL, and Redis clients read REDIS_* without hand-wiring.

Ready-to-use connection block

Each database detail view returns the engine-correct host plus a connection block you can paste straight into a client or migration tool.

Backups and point-in-time recovery

Postgres and MySQL include backup and point-in-time recovery controls billed with the database. Redis does not include backup or PITR today.

One project, one network, one bill

The database runs inside the same private project as your app, on one private network, drawn from one prepaid credit balance.

How it works

  1. 01

    Create

    Pick Postgres, MySQL, or Redis in the portal and the instance provisions inside your project's private network in a single form.

  2. 02

    Bind

    Open your container app, choose Connect a database, and its credentials land as secret-backed environment variables plus a Connected services card with code snippets.

  3. 03

    Ship and recover

    Your app reads the connection at boot. For Postgres or MySQL, the documented backup and point-in-time recovery controls are available; Redis has no backup or PITR today.

Pricing

Each service uses its published meter against prepaid credit: provisioned time, storage, tokens, or another listed unit. Estimate any setup in the calculator.

Open the pricing calculator
Managed Postgres / MySQLplus $0.05/GB-mo backups and $0.10/GB-mo storage, metered hourly on prepaid credit
$12/vCPU-mo, $6/GB-mo, $3/instance-mo
Managed Redisplus $0.10/GB-mo storage, metered hourly on prepaid credit
$10/vCPU-mo, $5/GB-mo
Worked examplesa 1 vCPU / 1 GB / 10 GB Postgres runs about $22.50/mo
starter Postgres from ~$9.15/mo, Redis from ~$3.85/mo

Questions

Can I run a database with replicas or failover?

No. Postgres and MySQL run as a single instance by design; read replicas, failover, and multi-AZ are not offered today.

How does my app get the credentials?

Bind the database to a container app and the portal injects secret-backed variables such as DATABASE_URL or SPRING_DATASOURCE_*, matched to your framework.

Which Redis version do I get?

Redis is fixed at version 8, so every Redis instance you create runs the same engine version.

Are backups included?

Postgres and MySQL include billed backup and point-in-time recovery controls. Redis does not include backup or PITR today, so keep your own copy of critical Redis data.

Related products

Deploy this in your first project.

Claim your $5 trial credit and go live today.

Start free