Everything we've learned about crowds and networks.
Research, answers and the materials you need to evaluate Zeva, written for operators first and engineers second.
Research on the third wireless layer.
- Research5 min readWhy wireless infrastructure can't keep up with crowdsCarriers and venues spend years and tens of millions preparing one stadium for one game. Demand still grows faster than they can build.Read
- Vision6 min readThe third wireless layerEvery generation of wireless added a layer that filled a gap the previous one couldn't. The next one is made of the devices themselves.Read
- Technology5 min readThe phone-side hardware caught upThree years ago a Bluetooth mesh at stadium density drained batteries and dropped packets. Today the radios and chipsets do the heavy lifting.Read
The questions that always come up.
Battery and privacy first, then what you actually install.
Open specification v1 publishes with our first validated deployments.
Standards start as one product that works. The spec, a reference implementation and a certification program are how Zeva goes from a venue product to a layer embedded in operating systems and chipsets.
Want early access to the draft, or to be part of the review group? Tell us who you are and what you build.
Request early accessLogo, wordmark and boilerplate.
Use the assets as provided. The wordmark is set in Michroma; please don't recreate it in another face.
One-line description
Zeva is a routing protocol that turns every phone in a crowd into part of the network. Venues deploy it inside their existing app; attendees never think about it. Live events are where Zeva proves it, on the way to a global standard for device-to-device routing.
Boilerplate
Zeva Corp builds the third wireless layer: after cellular and Wi-Fi, a network made of the devices themselves. Founded by veterans of military mobile ad-hoc networking and live event production.
Press enquiries: connor@zeva.io
Prove it at your next event.
We're selecting festivals, conferences and venues for validated 2026–27 deployments with published uptime data. A 30-minute call is enough to scope one.