Hosting
Checking
Querying live state
Backups
Checking
Last 30 days
Restore tests
Checking
Latest monthly run
Your durability
Counts for your account. Each row shows three protection dots in order: hosting, archive copy, Drive backup. Hover for the timestamp.
Right now, across every site
Every deploy creates a second copy in the user's own Google Drive (if connected) and a compressed archive in our cold-storage bucket.
Sites with archive copy
...
Users with Drive backup
...
Backups in the last 30 days
Each successful deploy triggers two background backups.
Google Drive copies saved
...
Monthly restore test
On the 1st of each month at 03:00 UTC, we pick a random archived site, extract it, and verify it opens as a valid HTML document. The result is recorded here and visible below.
How the check works:
- Random site picked from those with a stored backup copy.
- The backup copy is downloaded from where it sleeps.
- The folder inside is unpacked and the file count is checked.
- The main page is found and confirmed to open as a real webpage.
- The outcome is recorded. Failures wake an operator by email.
What happens if…
Three failure scenarios, and what you would actually have to do in each. Nothing here is aspirational. Each line follows directly from where your files and domain already live.
… if WhatImade disappeared tomorrow
- Your domain stays with you. It was registered in your name at Cloudflare from day one, not ours. No transfer paperwork, no consent from us required.
- Your Google Drive backup is in your Google account, in a folder we cannot reach into. Our going away does not remove it.
- Every file in that folder is a normal webpage or image, in the same format anyone else on the internet uses. You can upload them to any other website host and your site is live again.
- You would not need our permission, our software, or a migration tool to leave.
… if you lost access to your Google account
- Your site stays live. Hosting does not depend on your Google account.
- We could no longer write new Drive backups for you (Drive access ends with the account). Publishing still works.
- The compressed archive in our cold storage is untouched. You can still download it from your dashboard using your session cookie or, failing that, through support.
- Reconnect a fresh Google account later and Drive backups resume on the next publish.
… if Cloudflare had a major outage
- Sites served from WhatImade would be unreachable for the duration of the outage (we run on Cloudflare's edge).
- The Drive backup in your Google account is untouched and reachable from anywhere else on the internet. It is the independent second copy the page above counts.
- A publish attempted during the outage is queued locally in our Worker and replays when Cloudflare returns. Nothing is lost.
- For a multi-day Cloudflare outage, the scenario the Drive design specifically pays for, you can take the files from your Drive folder and host them on any other static host (Netlify, Vercel, GitHub Pages, an S3 bucket) and be live again within minutes.
What we do not do
For trust to mean anything, it has to cut both ways.
- We do not read, open, or scrape the contents of your Google Drive. We hold the
drive.file scope, which only lets us read files we created.
- We do not touch your Drive backup if you delete your account. The copy stays entirely yours.
- We do not silently extend the 7-day deletion window. If the daily cleanup misses a day, your site is still there; the next run picks it up.
- We do not use your site content to train models or sell to third parties (see Terms of Service, section 4).