Database hosting
Deploy your databases.We keep them running.
Add a database next to your app. We handle uptime and backups so you can keep building.
With the app
The database stays connected.
It sits on the same worker as the app. The connection stays private. You keep building.
app
storefront-api
running
U01 · sidecar
orders-db
Postgres · postgres:16
same worker · private network
Engines
Use the engine your app already knows.
Add the database next to the app. The app stays connected. ClickHouse is available. Backups for it are not.
image
env key
reference
backups
hourly · daily · weekly · monthly
connection · postgres://storefront:••••••@orders-db:5432 · postgres:16
Operations
The database stays recoverable.
You do not run backups. We keep 24 hourly, 7 daily, 4 weekly, and 3 monthly copies on the worker disk, or in an S3, R2, B2, Wasabi, or MinIO bucket you already have. Restore and download from the dashboard. Not on managed dFlow compute, and not for ClickHouse.
- Postgres24 7 4 3
- MongoDB24 7 4 3
- Redis24 7 4 3
- MySQL24 7 4 3
- MariaDB24 7 4 3
- ClickHouseunsupported
S3 · R2 · B2 · Wasabi · MinIO
Live runtime logs
- 14:02:11 listening on 5432
- 14:02:12 checkpoint complete
- 14:02:18 streaming
Restore and download
- source
- orders-db-daily-07
- target
- orders-db
- status
- ready
Private by default
- internalorders-db:5432
- exposedoff
Data plane
Your data stays with the app.
Database files live beside the app, not in the dashboard. DPA, GDPR, and subprocessors stay on the Trust Center.
worker · orders-db
POSTGRES_URI
Container beside the app. URI on the private network.
attach
Add the database.Keep the app connected.
No $. No env: prefix. The app reads the key the sidecar publishes.
storefront-api
{{ orders-db.POSTGRES_URI }}
orders-db · postgres:16
ClickHouse is available. Backups for it are not available yet.