Architecture/In design
Infrastructure layer
Compute resources that can be continuously replaced, relocated and reconfigured.
Static servers are easy to find and easy to watch. The infrastructure layer treats every server as temporary.
How it works
- Replace. Relays and service instances are created from clean images and destroyed after their lifetime. Nothing accumulates logs or state.
- Relocate. New instances appear on different providers, networks and regions, so infrastructure relationships stay hard to map.
- Reconfigure. Addresses, ports and parameters change between generations of the same service.
Stateless by default
Because instances are short-lived, they keep no user state. Anything that must persist goes to the storage layer in fragments, not to the disk of a single machine.
Node operators
Later phases add node software so independent operators can contribute capacity. Operators run instances on the same rotation schedule, and diversity of operators is part of path selection. See Roadmap.