Rowsafe Storage
Keep backups without a bucket of your own, encrypted so Rowsafe can't read them.
Rowsafe Storage skips the bucket setup: Rowsafe runs the bucket, and your organization gets its own private space in it. Servers Rowsafe creates for you and Rowsafe Cloud servers use it from the first minute.
Your backups stay private. They're encrypted on your server with a passphrase Rowsafe never has. We store them but can't read them, and neither can anyone who gets the bucket.
Use Rowsafe Storage
Choose it in the installer
The installer asks where backups go:
Where should backups go?
1) Rowsafe Storage nothing to set up (10 GB free)
2) Your own bucket Cloudflare R2, Amazon S3, Backblaze B2, ...
Choose 1-2 [1]:Press Enter. The dashboard's command already ends with --storage rowsafe, which skips this question.
Save the passphrase
The installer shows the passphrase once. Save it in your password manager, then type its last 4 characters. Why it matters.
That's it
The installer tests the storage and goes on to find your database. Settings → Storage shows your usage.
Without a terminal, pass --storage rowsafe. The passphrase comes from ROWSAFE_REPO_CIPHER_PASS; without it, the installer makes one and keeps it in /etc/rowsafe/agent.env. Copy it to your secret manager right away: sudo grep CIPHER_PASS /etc/rowsafe/agent.env.
How much is included
| Plan | Rowsafe Storage |
|---|---|
| Free | 10 GB |
| Pro | 250 GB |
| Business | 2 TB |
Usage counts full and differential backups, plus every change since the oldest kept backup. Measured hourly.
- At 80%: a warning in Settings → Storage, and an email to your weekly Pulse recipients and email alert channels.
- At 100%: new full backups pause. Every change is still saved, so Rewind keeps working, and nothing is ever deleted to make room. Upgrade, keep fewer full backups, or move to your own bucket, and full backups resume.
How access works
Your server never holds a long-lived key. The agent gets temporary access to your organization's space only, valid 7 days, renewed daily. It can't see other organizations' backups. A removed server gets no new access, and its access runs out within 7 days.
If the server can't reach Rowsafe, backups go on until access runs out, 6 days after the last renewal. Rowsafe alerts you two days before. Once it reconnects, it renews by itself.
Move to your own bucket
Your bucket's keys must never leave your server, so you move on the server:
- Create a bucket and an access key.
- Run
curl -fsSL https://rowsafe.sh | sudo sh -s -- --setup-storageand answer y to "Move them to your own bucket?". It tests the bucket and keeps your passphrase. - Rowsafe takes a new full backup in your bucket right away.
Restores and Rewind start from the first backup in your bucket. Older backups stay in Rowsafe Storage for 30 days, then are deleted, but Rowsafe doesn't restore from them after the move.
To go back, run the same command and choose Rowsafe Storage (or add --storage rowsafe).
When backups are deleted
Rowsafe deletes your backups only in these cases, always after 30 days and with an email a week before:
- You removed a database from Rowsafe.
- A server moved to its own bucket.
- Your organization is deleted.
Settings → Storage lists what's scheduled. To keep a removed database's backups, add it back under the same name, on a server using Rowsafe Storage, before the date. Every deletion is in the audit log.
Kept for you
When an AI agent removes a database, its backups are kept with no date, under Kept for you in Settings → Storage. Add the database back to use them.
Only an owner can click Delete these backups. Then the usual 30 days and email apply, and adding the database back still keeps them.
There's no "download your backups" button: they're encrypted with your passphrase, so a copy from Rowsafe wouldn't help. To hold them yourself, move to your own bucket.
Good to know
- A removed database with "keep archiving" on keeps writing WAL here until you turn archiving off. Those files go with the rest after 30 days.
- Rowsafe Storage comes with Rowsafe's hosted service.
- A second copy always goes to your own bucket, alongside Rowsafe Storage.
- A standby isn't available yet on Rowsafe Storage: move to your own bucket first.
- Test the storage:
sudo sh install.sh --check-storage, orrowsafe-agent storage testaspostgres.