It provides true zero-knowledge end-to-end encryption.
Data is encrypted at the source before it ever touches the network.
Even if we were compromised, your data is secure.
#database #buildinpublic #mongodb #postgresql #mysql
@DRYAPAPER Great question. Iโm planning to use Envelope Encryption.
Basically, each backup gets its own unique key, which is then wrapped by a Master Key. This allows for key rotation by just re-wrapping the metadataโno need to re-encrypt the actual backup data. For management, I'm looking at using the system's native keychain and providing a BIP-39 recovery phrase at setup.
Why settle for standard backups when you can have ๐ญ๐ฒ๐ฟ๐ผ-๐๐ป๐ผ๐๐น๐ฒ๐ฑ๐ด๐ฒ ๐๐ฎ๐๐?
The upcoming ๐ข๐ผ๐ฝ๐ ๐๐ด๐ฒ๐ป๐ (built in Go) is designed to handle your PostgreSQL, MySQL, and MongoDB backups with local-first encryption. Your keys never leave your infrastructure.
Security shouldn't be an afterthought.
Itโs the core of everything we do at Oops Backup.
#SelfHosted #Database #Privacy #SaaS #CyberSecurity #BuildInPublic
Roadmap Update!
Currently prototyping an Open Source Agent for those who need true End-to-End Encryption.
Local Encryption: Data is encrypted on your server before it ever hits the wire.
Zero-Knowledge: We never see your keys or your raw data.
Simplicity: Keeping the 1-line install goal.
Managed backups for speed, Agents for high-security. Best of both worlds coming soon. Stay tuned.
A great lesson in building in public today.
Peteris from Healthchecks called me out on HN regarding End-to-End Encryption. And he was 100% right. my managed setup is "Encrypted at Rest," but not true E2EE because data is "seen" in-flight.
Already updated the site to be technically accurate (no more E2EE buzzwords) and defined Oops Backup as the "easy/managed" choice for indies.
Next?
Building an Open Source Agent for true E2EE.
Thanks for keeping the bar high.