I built WebsiteSave because a backup alone isn't enough
by KhubabI’ve spent 7 years working on WebsiteSave, a SaaS for website backups, security checks, health insights, and recovery.
The idea started with a simple question:
When a website breaks, is having a backup really enough?
You might have multiple backups sitting there, but you still need to figure out what changed, when it changed, and which recovery point makes sense.
So I built WebsiteSave around that problem.
It automatically creates website backups and combines them with security and website-health information to give you more context when something goes wrong.
The core idea is:
Protect → Detect → Understand → Recover.
WebsiteSave is now live, and I'm starting to put it in front of real users.
I'm particularly interested in hearing from other indie hackers:
How do you currently back up your websites, and what happens when you actually need to restore one?
-
1
Seven years of product experience makes the problem credible, but the key signal seems to be what happens during recovery. Have real users used the context to choose a restore point yet?
-
1
This system has granular restorations and yes you are correct, taking backup is a bit simple thing but restoring a backup needs precise and accurate logic. The system is already tested and operational by real users. Let me add one more layer to this answer. It also store encrypted backups and when it restore then it decrypt those files on fly.
-
1
The real-user usage is a useful signal, especially around restoration. If you’re open to it, what’s the best email to reach you on?
-
-