--- title: "Edge Vault | The Undo Button for Infrastructure" description: "Checkpoint any machine — any cloud, any host — in seconds, before anything risky happens. Roll back in one call when it goes wrong. For humans and AI agents, with free restores forever. And every checkpoint is a backup." url: https://edge.network/vault/ --- # Edge Vault | The Undo Button for Infrastructure [Vault](https://edge.network/vault) Vault # The undo button for your infrastructure. Checkpoint any machine — any cloud, any host, bare metal — in seconds, before anything risky happens. Roll back in one call when it goes wrong. Built for humans **and** AI agents, with rollbacks that cost **$0, at any size, forever**. Join the Waitlist [For AI Agents](https://edge.network/vault/agents) # ten seconds before the risky bit $ vault snap "before nginx change" ✓ snap_9f2c · 2.1s · +38 MB new chunks # …the risky bit goes wrong ✗ nginx: [emerg] invalid parameter # undo $ vault undo ✓ restored snap_9f2c · 41s · cost $0.00 <5s Warm checkpoint $0 Rollbacks & restores, any size Any Cloud, host or bare metal 2 Doors in: humans & agents ## Works where your servers actually are Vault is a small daemon, not a platform commitment. It protects infrastructure on any provider — Edge is just where the encrypted checkpoints live. 01 ### Install anywhere One line on any Linux, macOS, or Windows machine — Hetzner, EC2, bare metal, the Mac mini under your desk. Vault doesn't care where your infrastructure lives. 02 ### Add your key Generate a vault key (or paste an existing one) and pick your paths. Keys never leave the machine — Edge only ever stores ciphertext. 03 ### Checkpoint before anything risky vault snap takes seconds on a warm machine, thanks to dedupe. Break something? vault undo. That's the whole workflow. # any Linux, macOS or Windows machine, any host $ curl -fsSL vault.edge.network/install | sh $ vault init # generates your key — add it and you're off ## One product, two doors The same checkpoint-and-rollback loop, whether the hands on the keyboard are human or the keyboard doesn't exist. ### For humans The ten-seconds-before-you-edit-nginx tool. - vault snap "before nginx change" — then edit fearlessly - vault undo rolls back the last checkpoint in one command - Continuous watching between checkpoints, cron-free - Menubar & tray apps on macOS, Windows, and Linux - Fleet view in Control: every machine, last checkpoint, alerts ### For AI agents Reversibility as a primitive, in the toolbox from day one. - Pre-flight checkpoints via the Agent API and MCP server - "Always checkpoint first" — a one-line system-prompt policy - One-call rollback converts disasters into non-events - Machine-readable fleet health and restore verification - Agents can even self-provision Vault mid-session, no human needed [The agent surface in depth](https://edge.network/vault/agents) ## Built to be trusted with the worst day Under the surface it's proven engineering — content-addressed chunks, an open repository format, client-held keys — tuned for one thing: making reversibility instant. ### Checkpoints in seconds Dedupe against a local chunk index means a warm checkpoint only reads and ships what changed. Fast enough that "always checkpoint first" is a habit, not a decision. ### Rollbacks that cost nothing Zero egress is Edge's cost structure, so there is no restore meter. Recovery is never a budget decision — for a 2 KB config or a 2 TB machine. ### Honest about databases Files roll back cleanly; running databases need consistency. Declare hooks — a pg_dump before each checkpoint, say — and Vault runs and versions them alongside your files. ### We cannot read your data Keys are generated on your machine and never transmitted. What reaches Edge is encrypted, content-addressed chunks — ciphertext we couldn't decrypt if we wanted to. ### Open format, no lock-in Repositories use the battle-audited restic format. Your checkpoints are readable with open tooling, without Edge — that's the point. ### Silence alerts The scariest state is a machine that quietly stopped checkpointing. Vault surfaces last-checkpoint age everywhere and alerts you when a device goes dark. The byproduct ## Oh — and you now have backups. Every checkpoint is a snapshot in an encrypted, deduplicated repository, and Vault keeps watching between checkpoints. Use the undo button for its own sake, and continuous backup falls out for free. The backup industry sells a chore that pays off never; Vault is a tool you'll want ten seconds from now — and the chore does itself. Encrypted, deduplicated snapshots on every checkpoint Continuous watching between manual checkpoints Sensible retention: 7 daily / 4 weekly / 12 monthly Automated restore verification — a fact, not a hope Browse and restore any snapshot from Control Free restores at any size, forever ## Undo shouldn't have a price tag. Provider snapshots bill you to restore. Cold archives make your disaster wait in a 12–48 hour queue. Object storage charges egress the day the disk dies. Vault's rollback meter doesn't exist — recovering a 2 KB config and a 2 TB machine cost the same: nothing. [Vault vs snapshots, Git, ZFS, and backup tools](https://edge.network/vault/compare) Recovering 2 TB AWS S3 (egress at $0.09/GB) ~$184 Edge Vault $0 — every time, at any size ## Vault is coming The daemon, CLI, and agent surface first; desktop apps next. Leave your email and be first through the door — early users get the free tier plus launch pricing.