Edgebox
The box a house keeps. A disk, and open-source software already loaded on it. Sensitive files stay here. The house decides what they are for.
What it is for
Edgebox is the local sink. Room recordings and the other files that should not be uploaded in order to be shared stay on the disk in the building. The same machine runs the community’s ordinary software: the tools a house actually uses, already on the box.
The first machines are a Raspberry Pi 5 with an SSD. Mini-PCs follow. The job does not change with the case. The repository is not public yet, so this page is the description.
The second copy
A fire in the house must not be the end of the record. The design is a second copy, encrypted, on Vault or on any S3 store — Backblaze B2, or a store the house brings. The host sees ciphertext, so the copy can live somewhere the house does not control.
That copy is not running yet. The disk in the building is the part we are putting together.
What sits on the box
Lightning Mesh is the network the box joins. Reachability is meant to come through those nodes, and over Iroh, without a setup ritual. That path is the design.
IdentiKey is who is allowed near the files. A guild — the house, deciding together — is how a community chooses what surveillance footage may be used for. The decision is meant to grant real access by vending a recryption key, not by publishing a policy. Guilds are not running yet. The key you mint is.
Recrypt is the share and the revocation. The library works. Mjolnir is meant to run the small machines on Edgebox that do the recryption. Mjolnir is still being built. Embassy SF is a Lightning Mesh install. It is not an Edgebox.