FAQ

Every phone is both a broadcaster and a listener. Messages hop from phone to phone, roughly 30 m at a time, until they reach their destination or run out of mesh. No internet connection is required for any of it. An internet connection is optional and, when present, adds extra bandwidth on top of the mesh rather than replacing it.

No. A standard iOS, Android, or Windows device is all that is required to join the mesh. The optional Windows relay hubs run on any PC already on hand: nobody has to buy anything purpose-built.

The protocol is designed for end-to-end encryption, and an independent security audit is scheduled but not complete. Until that audit publishes, this is not something to rely on for high-risk communication. The security page lays out the full threat model and the disclaimer in detail.

Free for consumers, forever. The organizations responsible for other people pay: event operators, search-and-rescue teams, emergency managers. A dashboard and a fleet of always-on relay hubs are what they need, and they are the ones who can fund it.

It is scheduled, and a date publishes once the scope is finalized. No high-risk-user positioning goes out before that audit passes.

iOS, Android, and Windows.

No. Everything runs over Bluetooth between devices. An internet connection is an optional enhancement on top of the mesh, never a dependency underneath it.

Roughly 30 m per hop. The real driver is density and relay coverage, not raw distance: a crowded venue with a hub outperforms an empty field regardless of hop range. Measured figures for delivery and latency publish with the litepaper.

Not yet. The site refers to the project by a working name until a public one is chosen.

Event and disaster-response operators first: the people who need a dashboard, a fleet view, and an always-on hub. A free consumer app sits underneath all of that, and its job is to prove the mesh works at real density rather than to earn revenue.