Density-aware egress routing
Live counts on every gate, ramp and stairwell. The system computes per-exit dwell and density, ranks them, and surfaces the under-used routes attendants can push the crowd toward - in seconds, not minutes.
01 · Industries · Events & stadiums
Crowd flow, density safety, exits - before the brief is too tight.
Real-time density across the bowl, the concourses, the egress routes. Threshold alerts to ops in seconds. Post-event reconciliation with hard numbers.
02 · Entry queue & gates
The queue, the chokepoint, the concourse.
Outdoor queue feeds the gates. Gates throttle the flow. Concourse swallows the throughput. Each zone counted on-device, wait-time and throughput alerts long before a brief gets tight.
Sample · Entry queue flow
Demo data simulated locally. Dots flow queue → gates → concourse → exits. Real deployments stream from edge sensors over MQTT or HTTPS.
People on site
-
Total across queue, gates, concourse and exits
In queue
-
Approaching gates
At gates
-
Chokepoint throughput
Concourse
-
Inside, moving
Exiting
-
Leaving the venue
Each dot is one anonymous occupancy count. No faces, no video, just flow. Same architecture as the seated map below.
03 · Live arena seating
Inside the bowl, section by section.
Once they're in their seats, the same architecture counts density per section. Hot sections light up. No faces. No video. Just numbers ticking on each section.
Sample · Arena seating
Demo data simulated locally. Each section ticks live. Real deployments stream from edge sensors over MQTT or HTTPS.
People on site
-
Anonymous count across every section
Capacity
-
Across 64 sections
Density
-
% of capacity filled
Lower bowl
-
Sections 100s
Mid bowl
-
Sections 200s
Upper bowl
-
Sections 300s · two tiers above the mid bowl
Hottest section
-
Highest density right now · ops alert candidate
Privacy mode
By architecture
Edge inference only · no raw video transmitted
"No faces. No video stored. Just counts." - the section numbers tick, the seats stay anonymous.
04 · Exit & evacuation
The minutes after the final whistle are the minutes that matter.
When sixty thousand people stand up at once, density crosses safety thresholds faster than a control room can read them. The same on-device counts that fill the seats during the match become the routing layer that empties the venue safely afterwards - and during an evacuation, they become the runbook trigger.
Live updates to attendants
Threshold crossings push to the right attendant's device with the right message - "Gate B sustained 92%, redirect to Gate D" - timestamped, location-tagged, ack-required. No radio chatter, no guessing, no waiting for a control-room call.
Transport-hub coordination
The tram stop holds 200. The next train arrives in 4 minutes. The system reads the platform's live counts (or the operator's feed) and paces the venue's release rate to match - holding the concourse so the platform never crushes.
Evacuation runbook trigger
Sustained over-threshold in a designated zone, smoke detector, or operator panic-press fires the preset runbook: every attendant on the affected floor pinged with the assigned route, every digital sign repointed, every gate state-changed. Drilled monthly. Auditable post-event.
Sample · Live ops feed during egress
19:42:08
Gate B · sustained 92% · 8 min · attendants A4, A5 pinged · 4 ack within 12 s
19:43:21
Reroute pushed · 1,200 of 1,800 in Aisle 5 redirected to Gate D · density falling at Gate B
19:45:02
Transit · platform 2 reading 86% · next train 3 min · holding 60 people at Concourse N exit
19:48:14
Gate B down to 64% · platform 2 cleared · holds released
19:53:40
Bowl 87% emptied in 11:32 · 96th-percentile route dwell 5:18 · post-event report queued
05 · Crowd flow built into the architecture
Run the event off the live numbers - queue in, bowl seated, egress routed.
From the gate to the train platform, every chokepoint counted on-device. No faces. No video. Just the density numbers your ops team needs to keep the night safe.