[kovacivan]

Wait, you are the Healthchecks.io founder? Big fan of your work!

You’re 100% right on the terminology. The pg_dump | gpg flow is definitely the correct way to achieve true E2EE.

The trade-off I made with Oops Backup was purely about eliminating the agent or script management. For many of the indie devs I'm targeting, setting up and maintaining that cron job/script is the hurdle that prevents them from having backups at all.

By handling the connection string on our end, we provide a 2-minute set and forget experience, even though it means we have access in-flight before the data is encrypted at rest.

Honestly, I built this because I was tired of managing custom backup scripts for my own side projects and just wanted a easy safety net.

I’m updating the site to remove the 'End-to-End' claim. I definitely don't want to mislead anyone on the architecture. It’s 'Zero-Knowledge' for the stored data only.

Thanks for the catch and for keeping the bar high.