Backups you can restore, proven regularly.
teleon.dev/docs/worm keeps write-once copies by the 3-2-1-1-0 rule and proves them with clean-room restores, replaying the outbox log in order so the restored state matches.
teleon.dev/docs/wormImmutable backupshttpsjsonmcp
Where the copies live
Primarylive database
copy 1
Second mediumobject storage
copy 2
Offsite, immutablewrite once
copy 3
restore proof
Each copy fills one part of the rule; the latest clean-room restore matched exactly.
What it does
3-2-1-1-0
Three copies on two media, one offsite, one immutable, and a clean result in the latest restore proof.
Clean-room restores
Restores run on a fresh machine and are compared with the source.
Ordered replay
The outbox log replays in order, so effects happen once.
The contract
A restore proof names the snapshot, the replay range and the comparison result.
Rule3-2-1-1-0 copies
StorageWrite once, read many
ProofsClean-room restores on a schedule
AccessRING-1
Identifiers
teleon_admin_control_tower_snapshot/v1
Execution contracts
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/restores/latest | RING-1 | Read the latest restore proof | |
GET | /v1/copies | RING-1 | List copies by rule |
Listed paths appear in the service’s published files today. In the one-host plan every path here is served under api.teleon.dev/v1/worm.
Words on this page
- WORM
- Write once, read many: storage that keeps backups exactly as written, for clean restores.
- Idempotent
- Safe to repeat: running the same request twice leaves the same result as running it once.