Skip to content
launchroom
Install

Databases and backups

Lose the server, keep everything.

Add a database to the canvas and connect it to your app. Backups go to your own S3-compatible bucket, encrypted before they leave the server, and launchroom checks every week that they restore.

Read the docsInstall launchroom
Backups tab of orders-db: backed up 7 minutes ago, daily schedule, retention 7 daily, 4 weekly, 3 monthly, last verified 19 minutes ago, point-in-time recovery on with a 7-day window, and a snapshot list.Backups tab of orders-db: backed up 7 minutes ago, daily schedule, retention 7 daily, 4 weekly, 3 monthly, last verified 19 minutes ago, point-in-time recovery on with a 7-day window, and a snapshot list.

Managed databases

Drop it on the canvas. It’s connected.

Draw a line from your app to the database. The app receives the connection details with the variable names its framework expects. Nobody copies a password.
  • PostgreSQL, MySQL, Redis, Valkey, MongoDB and ClickHouse
  • Credentials are generated and given to the apps you connect
  • Data lives on named volumes and survives every redeploy
Managed databases
Add database sheet with engine choices PostgreSQL, MySQL, Redis, Valkey, MongoDB and ClickHouse, a version picker and a service name.Add database sheet with engine choices PostgreSQL, MySQL, Redis, Valkey, MongoDB and ClickHouse, a version picker and a service name.

Point-in-time recovery

Restore Postgres to the second.

Pick a moment before the bad migration. launchroom rebuilds the database up to that second and hands you the result.
  • Changes are shipped every 30 seconds, plus a daily full backup
  • Restore as a new database next to the old one, or in place
  • Move apps and domains to the restored copy in one step
Point-in-time recovery
Snapshot list with 'Any point in time' selected and a date-time picker set to a second inside the recovery window, above the restore options.Snapshot list with 'Any point in time' selected and a date-time picker set to a second inside the recovery window, above the restore options.

Disaster recovery

One command brings it all back.

If the server is gone, run the installer with --restore on a new machine. Your projects, secrets, private network and databases come back.
  • launchroom backs up its own database and keys, sealed with your recovery passphrase
  • The recovery kit holds what a new server needs
  • Recovery mode guides you through replacing the lost server
Restore and disaster recovery

Data tab

Look inside without a database client.

Browse tables and run queries in the dashboard. It is read-only by default. Writes are allowed per session and recorded statement by statement.
Console and Data
Data tab of a ClickHouse database: a read-only query grouping pageviews by path, and a result table with four rows of paths, view counts and average milliseconds.Data tab of a ClickHouse database: a read-only query grouping pageviews by path, and a result table with four rows of paths, view counts and average milliseconds.

Details

Encrypted on the server
Backups are encrypted before they are uploaded.
Any S3
Cloudflare R2, Hetzner Object Storage, AWS S3, MinIO and others.
Volumes too
Named volumes back up on the same schedules.
Final backups
Deleting a database takes one last backup first.
Checked weekly
Backups are restored into throwaway containers and verified.
Alerts
A failed or missing backup sends an alert.

More of launchroom

Install it on your server with one command.

curl -fsSL https://launchroom.vantezzen.io/install | sh