One week
Seven days from the campaign closing to backers being on the new machine. Not a quarter, not “in the new year”.
It can be a week because nothing is being manufactured and nothing is being posted.
Days 1–4
Move to a bigger machine
The site currently runs on a box sized for a demonstration. Backers arriving is the first time it has to be sized for people.
Database, uploaded photographs and configuration move across, the new machine is brought up alongside the old one, and traffic switches only once the new one is serving correctly.
Days 5–6
Backups, and restoring from them
Nightly backups, integrity-checked, copied off the machine they protect. Today every copy sits on the same disk as the thing it is backing up, which is the single most consequential gap on the list.
Then the part that is usually skipped: actually restoring from one. A backup nobody has restored from is a hypothesis, not a backup.
Day 7
Live for backers
Names go on the credits page. Anyone whose tier includes the build log receives it as a document.
Nothing is posted, so nothing can be lost in transit or held at a border.
Restored, not just taken
A backup you have never restored from is a hypothesis.
That line has been at the top of the backup script since long before this campaign, and it is why two of the seven days are spent on something no backer will ever see.
The backups already run nightly, are checked for integrity, and have been restored from once — a real file was deleted and came back byte-identical. What they are not is anywhere other than the machine they protect.
Day five and six fix that, and then prove the fix by using it.
Counted from when
- Campaign closes
- Thursday 8 October 2026
- Backers are on the new machine
- Seven days after that, whenever it is.
The two features on the roadmap are not part of this week and are not claimed to be. Delivery week is the move, the backups and the credits — the roadmap is the year.