Encrypted on your own server, scheduled on a cadence you set, and test-restored to prove they come back. SolidOps only ever holds the ciphertext. Live today for PostgreSQL.
3
100%
12m
Encrypted, scheduled, and verified — the whole point is that the copy comes back when you need it. Here is exactly what ships today.
Set how often a database is dumped and how long copies are kept. A grandfather-father-son policy keeps the right hourly, daily, weekly, and monthly copies and rolls the rest off on its own.
The dump is encrypted on your server with your workspace key, in chunks, as it streams out. SolidOps only ever receives ciphertext — we never see the plaintext or hold the key. Zero-knowledge, by design.
Every dump is integrity-checked, and schedules can opt into a real restore: SolidOps restores the backup into a throwaway container and compares row counts. A backup you have never restored is a guess.
Backup freshness rides the same monitoring stack as your endpoints. A stale backup or one that fails to restore opens an incident and sends an alert, exactly like any outage.
A backup is dumped, encrypted, and hashed on the box, then stored and proven. SolidOps only ever handles ciphertext, so a breach of our storage tells an attacker nothing.
The agent runs pg_dump inside your database's own container, on the schedule you set. It reads the database directly — no credentials handed around, nothing exposed off the box.
As the dump streams, the agent encrypts it in chunks with your workspace key and hashes it. What leaves the server is ciphertext and a checksum — SolidOps never sees the contents.
The encrypted blob is uploaded straight to object storage, integrity-checked, and — on the cadence you choose — restored into a throwaway container to prove it actually comes back.
2.4 GB
4m 12s
passed
illustrative run · figures are demo data
Because SolidOps never holds your key, recovery works from any machine — even if the server and SolidOps are both gone. The flip side is that the key is the whole ballgame, and we tell you so up front.
Download the still-encrypted dump and decrypt it on your laptop with your recovery key, or have the agent decrypt it back onto a box. It works with the source server gone, the provider down, or SolidOps itself unreachable — because the plaintext and the key were never ours to lose.
It is shown exactly once, when you set backups up. There is no reveal and no reset. Lose it and every backup is permanently unrecoverable — that is the zero-knowledge guarantee working as intended, not a gap.
Store it in a password manager the moment it appears, off the box being backed up.
No asterisks on the parts that are real, and no hiding the edges that aren't finished yet.
PostgreSQL
Containerized databases, discovered on your enrolled servers. More engines are on the way.
Metered above a base
A base storage allowance is included with the plan. Only what sits past it is billed, monthly.
In-server restore
A real restore into a throwaway container on the same box, size-limited, with a row-count compare.
Yours, anywhere
Download the encrypted blob and decrypt it laptop-side, or have the agent decrypt it back onto the box.
PostgreSQL today · encrypted on the box · verified restores · your key
Encrypted, scheduled, verified backups are live now, with freshness that alerts like any outage. Buy the core today, and the rest of the platform lands as it ships.