built reference
Join Lightning Mesh
Lightning Mesh is a network of ordinary routers that talk to each other directly, with no company in the middle. It keeps working when the internet doesn't. Pick the path that matches what you actually have:
| I have… | Start here | Time |
|---|---|---|
A pre-flashed Lightning Mesh router (Wi-Fi named ⚡ or Lightning Mesh after it boots) |
Unbox | 10 min |
| A stock Cudy (or other) box that still shows the vendor UI | Flash OpenWrt | 1–2 h |
| Only a phone or laptop, and someone else's mesh is already on the air | Connect to the Wi-Fi | 10 min |
| Something to share (camera, wiki, game) on a mesh I can SSH to | Publish a service | 10 min |
| Code to contribute | Contribute |
If you just powered a box and no Lightning Mesh / ⚡ network appears
after two minutes, it was not pre-flashed. Use the flash path, not Unbox.
The path for a new house (pre-flashed box)
- Unbox: power, optional WAN, join the client Wi-Fi.
- First hour:
http://hello.mesh, optional identity. - How it works: client Wi-Fi vs backhaul, addresses, roaming, directory.
- Administer: names, internet sharing, SSH, Lightning Admin.
- Share a service:
.meshnames and the Apps shelf. - Add another router: second box — SSH peer exchange is still required.
The path for a new person
- Connect to the Wi-Fi: join the open network.
- Say hello: open
http://hello.mesh. - Create your identity: an IdentiKey you hold, and its recovery phrase.
- Sign in to mesh apps: approve apps with your identity.
- Find services: Apps shelf and Services list.
- Take your identity with you: restore it anywhere; nothing locks you in.
Stuck? Troubleshooting.
What works today
Each page carries a status. It describes what's in the software, not a promise that every box in a mixed fleet has been updated.
| Status | Meaning |
|---|---|
| built | In the current tree and meant to work on a current node |
| partial | Works, with a stated gap |
| coming soon | Designed or in progress, not usable yet |
| Built | Partial or not yet |
|---|---|
| Open Wi-Fi, internet when any router has WAN, offline hello.mesh | Seamless sessions when you walk between routers (DHCP roam exists; long calls can still drop) |
| IdentiKey with a 24-word recovery phrase | Deleting your identity from a mesh |
Sign-in from another tab (/assert) and from an Apps card |
Reviewing or revoking remembered app approvals (clear site data) |
.mesh names, operator publish, key-owned name API |
Claiming a pretty name from the hello.mesh UI |
Apps shelf on hello.mesh (app=v1 + manifest) |
Trusted HTTPS names without a certificate warning (in progress) |
| Adding routers, automatic internet sharing | A membership gate; automatic peering (you still paste node ids) |
Reading this guide as an agent
- Reading order and one-line summaries: `llms.txt`.
- Every page starts with YAML frontmatter:
id,path,status,requires,next_step,verified_against. - Every step has Do, Expect, If not.
- Treat
status: coming-soonas design, not as a working feature.
The human site is https://lightning.worldtree.network/.
To rebuild it, run cd docs-web && bun run build. To publish, docs-web/scripts/publish.sh.