Always-on relay nodes with a dashboard. The one thing no phone-only mesh has.
A mesh built only from phones inherits two failure modes no amount of clever routing fixes: the operating system takes the radio away, and an empty room has nothing to relay through. A fixed, always-on node closes both gaps at once. It anchors a venue: a festival operations tent, an incident command post, a campsite with no cell signal, and it keeps listening when every phone around it has gone quiet in someone's pocket.
Apple suspends Bluetooth advertising the moment an app leaves the foreground. Two locked phones in the same pocketed crowd stop finding each other. Every phone-only mesh degrades quietly the moment people stop staring at their screens.
A mesh needs density to be worth anything. Walk into an empty venue an hour before doors open and a phone-only mesh is only a phone: no neighbors, no relay, no signal.
Every benchmark scenario in the litepaper runs twice: once with a hub present on the site, once without. The delta between those two runs, not either number alone, is the figure that tells an operator whether a hub is worth deploying. That comparison is the entire point of the benchmark campaign, and it publishes in full once the campaign passes its gate. Nothing here is estimated in the meantime.
Numbers publish with the litepaper once the benchmark campaign passes its gate.
The relay-node role is part of the open protocol spec. Anyone can read it, implement it, and run a relay of their own. Nothing about how a phone talks to a phone, or a phone talks to a relay, is held back. The production Windows hub, the dashboard, the per-device aggregation, the fleet and location layer, the audit trail, the priority routing, is the commercial implementation of that open role. The open protocol stays complete on its own, with no hidden hooks reserved for the paid version.
Anything that serves one user is open. Anything that serves someone responsible for many users is commercial.
Pricing is set per deployment, not published on this site. Get in touch through the contact page to talk through a venue or operations use case.