Backup Empire

Origin

Built rapidly in 2026 in response to a structural realization: every line of code, every photograph, every paper, every model checkpoint that lives on a third-party platform is a hostage. The platform's terms can change; the account can be suspended without notice; the contents of years of work can become unreachable in an afternoon. A serious operating practice cannot run on hostage data.

Problem

Most backup tooling treats the working set as primary and the backup as redundant — which means recovery is reconstruction. What is needed is a backup that is itself a complete operating substrate: not a copy of the work but a substitute for the platform underneath the work.

Approach

Self-hosted git on dedicated hardware. Deduplicated, encrypted snapshots written to offsite storage on a regular cadence with versioned retention. An external watchdog confirms a heartbeat on every successful run. A tunnel provides global reach without exposing a port. The whole stack runs on hardware physically present in one room and visible at a glance on a single internal dashboard.

Methodology

Sovereignty boundaries are non-negotiable. No code on third-party platforms by default. Secrets sit on filesystems that enforce permissions; the working set sits where it has to. Passphrases never enter a chat transcript or a commit message. Restore drills run on a fixed monthly cadence and verify the backup actually restores — not just that it exists.

Selected milestones

• Sovereign git substrate operational; all source migrated off third-party hosts by default
• Deduplicated encrypted offsite mirror; versioned retention
• Monthly restore drill in production; last test passed
• External watchdog confirms a heartbeat on every successful run

Open questions

• Whether to add a second offsite jurisdiction for additional resilience
• What the right cadence is for restore drills as the corpus grows
• How to extend the model to data that lives in third-party operational systems (chat, calendar, mail)

Ask me about

• What triggered the build and what was at stake
• How the monthly restore drill is actually verified
• Why sovereignty over a third-party host, and where the boundary sits

Stack