Appearance
Provisioning Storage
This guide walks you through provisioning databases and object storage for your applications.
Navigate to Storage in the sidebar.
Provisioning a Database
- Under the Database section, enter your Application ID (e.g.,
my-app) - Click Provision
- The database is created and connection details are displayed
Connection Credentials
After provisioning, you'll see:
- Database — The database name
- Username — The database user
- Password — The database password
- Connection string — A ready-to-use PostgreSQL connection URL
WARNING
The password is shown only once. Copy and save it immediately.
Resetting Database Credentials
To generate a new password:
- Click the key icon next to the database
- Confirm by typing the application ID
- A new password is generated (the old password is invalidated immediately)
Backups
Turn on backups when you provision the database: a database provisioned without them cannot switch them on later. The database's Backups tab then shows its backups.
- Every night at 03:30 UTC a full dump of the database is made. Dumps are kept for the retention you choose (1, 3, 7, 14 or 30 days) and are stored encrypted (AES-256).
- Backup now makes an extra dump straight away, for example before an upgrade that migrates the database. It is refused while the newest backup is less than 10 minutes old.
- Restore puts the whole database back to the state of one dump. It first backs up the current state, so restoring that backup undoes the restore. The restore runs in a single transaction: if it fails, the database is left as it was.
- A restore puts back the tables in the dump. Tables created after the dump was made, for example by a migration, stay. If such a table depends on a table in the dump (a foreign key, a view), the restore fails and changes nothing: drop that table first, then restore.
- Backup now and restore work for databases up to 512 MB and dumps up to 100 MB. A restore is refused when the backup of the current state is over 100 MB, because that backup could not be restored here. For larger ones, contact support.
Deprovisioning a database deletes its backups too.
Deprovisioning a Database
- Click the trash icon next to the database
- Confirm by typing the application ID
WARNING
Deprovisioning permanently deletes the database and all its data. This cannot be undone.
Provisioning Object Storage
- Under the Object Storage section, enter your Application ID
- Click Provision
- The S3 bucket is created
S3 Connection Details
After provisioning one or more buckets, the page shows:
- S3 Endpoint — The S3-compatible endpoint URL
- Access Key — Shared across all buckets in your organization
- Bucket name — Same as the application ID
Each provisioned app appears as a separate bucket at the shared endpoint.
Using S3 Storage
Connect with any S3-compatible client. Example with AWS CLI:
bash
S3_ENDPOINT="https://<s3-endpoint>"
aws s3 --endpoint-url "$S3_ENDPOINT" \
ls s3://my-app/Or upload a file:
bash
aws s3 --endpoint-url "$S3_ENDPOINT" \
cp ./data.csv s3://my-app/data.csvDeprovisioning Object Storage
- Click the trash icon next to the bucket
- Confirm the deletion
WARNING
Deprovisioning permanently deletes all objects in the bucket. This cannot be undone.
TIP
Deployed apps can access their database via environment variables. Set the connection string as an env var in the deploy dialog.
Next Steps
- Deploy an app that connects to your provisioned storage
- Manage your deployments and add storage connection env vars