Restore any Postgres or SQLite database with one API call, to any point in the last 7 days by default. Conjoin also takes a daily snapshot of every database and an on-demand backup whenever you request one.
Conjoin writes the daily snapshot and the point-in-time recovery data of every database instance to Conjoin Storage in a second region. From those backups, you can restore a database to any second of its retention window.
Conjoin takes a full snapshot of each database once a day, during the hours when that database receives the least traffic. Because Conjoin keeps that schedule, you write no cron job or script for it.
Conjoin can restore a database to any second inside its retention window, which is 7 days by default. For example, you can choose the second before a faulty migration starts.
Start a backup through the API before you apply a migration or change a schema. Conjoin completes an on-demand backup in minutes and counts it toward the retention window of the database.
By default, Conjoin writes each backup through Conjoin Storage to a region separate from the database. If the region of the database goes down, you can restore from the copy in the other region.
Conjoin verifies every snapshot by checking that it can restore the database from that snapshot. When a snapshot fails verification, Conjoin alerts you straight away, so you learn about the problem before you need that backup.
Send one restore call with a timestamp through the API or the Console. Conjoin rebuilds the database to its state at the exact second that you name.
Because Conjoin stores the retention setting for each instance, you can give a production database a longer window than a development database, up to the limit of your plan.
Conjoin encrypts every backup at rest with AES-256 by default and manages the encryption keys itself, so you configure nothing to turn that encryption on.
Send one restore call with a timestamp through the API or the Console. Conjoin rebuilds the database to its state at the exact second that you name.
Because Conjoin stores the retention setting for each instance, you can give a production database a longer window than a development database, up to the limit of your plan.
Conjoin encrypts every backup at rest with AES-256 by default and manages the encryption keys itself, so you configure nothing to turn that encryption on.
Configurable per instance
API or Console
Automated, no setup
Conjoin snapshots each database every day and tests every snapshot with a restore check. If a snapshot fails that check, you receive an alert from Conjoin at that point.
Conjoin performs the snapshot and the restore check for you, so you keep no backup script in your repository.
Send one API call or one Console action with the timestamp that you want. Conjoin provisions the restored database, loads the data as of that second, and sets up its connections.
Your restore procedure becomes a single call with a timestamp, so you maintain no runbook of provisioning and data-loading steps.
Conjoin Storage keeps every backup in a region other than the one that hosts the database. When the region of the database is unavailable, you can start a restore from that second region.
Conjoin places the backup copy in a second region by default, so you set up no cross-region replication for your backups.
Add an on-demand backup call to your deployment pipeline ahead of the migration step. Once Conjoin finishes the backup, the pipeline can apply the migration, because you can now roll the database back to the moment before the schema change.
With one API call in your pipeline, every migration starts from a backup that you can restore.
Conjoin will open with a free Build tier, while the pricing page already lists the launch prices for Pro and Business. If you tell us what you're building, we'll talk you through early access.