A corps built to run itself.
The plan: makers who build privacy witnesses for people who can't, neighbors who ask, and a community that holds no data and runs no backend. None of it is finished yet.
Two sides, and the gallery between them
Each door is open today for raising your hand; the machinery that connects them isn't built yet.
Makers
Handy with a printer and an iron? Get certified in stages and build for people who can't build their own.
Are you a maker? →Requesters
Can't build it yourself? Post what you need, for a maker who chooses to make it — no race.
Have one made →The gallery
Built one already? Share your shell, your color, your remix — and make the next person's build easier.
Show your build →It holds no data and runs no backend
A privacy company shouldn't run a honeypot of its users. So the corps is built like the camera: public things live in the open; private things stay on your device.
GitHub is the “backend”
Build stories, enclosure remixes, and the maker roster are files, issues, and pull requests in the public repo; the site just renders them. You contribute by opening a pre-filled issue — versioned, reviewable, and run by no server we own.
Your situation never leaves
A request's sensitive story stays in your browser (localStorage) — we never receive it, so it isn't ours to leak or hand over. If private pairing is built, you'd share it end-to-end with one maker you choose, and nowhere else.
Earned in stages, not bought
Apprentice, Builder, Certified Maker, Steward — four tiers, earned in the Lab and then on real hardware. How the tiers work →
A market that accounts for itself
The long game: no escrow agent in the middle.
in design
The idea: settle each commission on the device's own signed build-and-health record, leaving only human conduct to a small steward quorum. Written up as a draft RFC; nothing here ships yet.
Everything above is a plan, honestly labeled. The doors are open for raising your hand; the machinery that connects them isn't built yet.