Roar AI backs up your app’s database twice a day and keeps each copy for ninety days, so you can always go back to an earlier version. Your database runs in Colombo, and the copies are stored away from that server.
Every backup goes through the same three steps automatically.
Each copy is encrypted before it leaves the server. The key that opens it is not kept on any of our servers.
Each copy is checked to make sure it is complete, then checked again once it has been stored.
Copies are stored away from the server that runs your app, so losing that server does not lose them.
Choose a backup in the console and Roar AI restores it while your app keeps running.
In your app’s Database tab, open Restore and choose the copy you want.
The copy is set up next to your current data while your app keeps running.
Your app moves to the restored data, and the data it had before is kept rather than overwritten.
In Colombo, alongside your app. The off-site copies are kept away from the server itself, so they are still there if the server is not.
Twice a day, about twelve hours apart. If something goes wrong between two backups, up to twelve hours of changes can be lost.
Your app’s database. Files your app stores, such as uploads, are not part of the backup.
You choose the copy in the console, and Roar AI completes the restore. Every restore needs two people at Roar AI, so a single mistake or a stolen login cannot replace your data.
Away from the server that runs your app, in storage that may be in another country. Backups are encrypted before they leave the server, and the key that opens them is kept on no Roar AI server.
Not while it is stopped. Its earlier backups are still kept, and backups start again when the app does.
They are kept for ninety days after the app is deleted, then removed.
Every push to GitHub goes live, and a failed build never replaces your app.
Learn moreCreate a free account and add a database to your app in Colombo. Backups start on their own.