Eventbuoy's WiFi/BLE mesh — powered by RuView's WiFi DensePose — turns every festival ground into a live intelligence layer. Real-time heatmaps, panic detection, brand activation ROI, and superfan engagement from $8/node hardware.
RuView changes Eventbuoy's category from "event app with smart features" to venue intelligence platform. The ESP32 mesh is the physical infrastructure; everything else — the fan app, brand dashboards, safety alerts, MINY drops — runs on top of it. That's a fundamentally different product than any pure-software competitor can replicate.
sec_panic_motion.rs detecting fleeing and struggling movement patterns. LSTM forecasting predicts crowd surges 30 minutes ahead. All running locally on the exe.dev VM or a festival-deployed edge server via Docker.
Of the three candidate repos evaluated — graphiloc (GNN-based indoor positioning), WifiIndoorPositioning (Android RSSI fingerprinting), and RuView — RuView is the only one that solves Eventbuoy's actual problem. Passive crowd sensing at festival scale, no attendee action required, privacy-first architecture, sub-$100 hardware per venue, and a Docker deployment that's live in 30 seconds. It also ships with exactly the edge modules Eventbuoy needs: dwell heatmaps, customer flow, queue length, and panic motion detection — out of the box.
graphiloc is academic indoor positioning (wrong scope). WifiIndoorPositioning is a client-side Android app requiring user action (wrong model). RuView is infrastructure. That's the distinction.
./install.sh --profile iot. BLE gateway nodes (same hardware) for opted-in wristband tracking. Total hardware budget for a 5,000-person festival: ~$54–108.
ret_dwell_heatmap.rs · ret_customer_flow.rs · ret_queue_length.rs · sec_panic_motion.rs.
Each is a tiny WASM file (5–30KB) uploaded OTA. Decision latency: <10ms. No internet connection required during the event.
RuView is not a feature to be added to Eventbuoy — it's the reason Eventbuoy's three GTM motions are defensible. The organizer white-label is defensible because no pure-app competitor includes passive crowd sensing. The brand activation is defensible because no other activation partner can quantify foot traffic to the activation zone. The platform is defensible because the CSI dataset compounds with every event. Without RuView, Eventbuoy is another event app. With RuView, it's the only event platform that knows where 10,000 people are standing at any given second.
| Buyer | RuView Data Used | How It's Surfaced | Revenue Impact | Competitive Lock-In |
|---|---|---|---|---|
| Festival Organizer White-Label | Crowd density heatmap, panic motion alerts, flow vectors, surge forecasting, zone capacity | Live safety dashboard (web) — real-time heatmap, red alerts for panic motion and capacity breaches, 30-min surge prediction | Justifies 2–3× price premium over pure-app competitors. Safety angle bypasses budget committee — goes direct to ops/safety manager who has authority. | Once mesh nodes are calibrated to a venue, the organizer has a spatial model that improves with each event. Physical hardware creates switching cost no SaaS competitor can replicate. |
| Brand / Agency Activation | Activation zone dwell heatmap, unique device count, dwell time distribution, flow into zone, notification-to-visit correlation | Live counter during event (brand dashboard). Post-event PDF report: unique visits, avg dwell time, traffic lift vs. baseline, push notification attribution | The only activation partner who delivers quantified foot traffic proof. Shifts the brand pitch from creative to data-backed investment. Commands 30–50% campaign premium. | Brand agencies operate on case studies. A single post-event report with real foot traffic data locks in the next booking. No camera-based alternative exists at festival scale without privacy risk. |
| Platform Ecosystem | Cross-event crowd behavior patterns, stage clustering signatures, artist-to-crowd correlation, multi-venue audience graph | Aggregate intelligence dashboard for promoters and labels. Predictive booking recommendations. Cross-event fan journey analysis. | Cross-event dataset monetized to labels, promoters, venue operators. Audience intelligence licensing. Network effects accelerate with each event added. | The CSI dataset is unique — no one else is building it at festival scale. Each new event makes the dataset more valuable to every participant. Classic data network effect. |
| Venue / Insurer Safety SaaS | Full crowd history: timestamped density records, surge events, panic motion flags, capacity compliance logs | Compliance reporting portal. Downloadable timestamped density records for post-incident documentation. Annual safety audit package. | $15K–$40K/yr standalone contract. Entirely separate from the fan app — venue buys it for liability protection. Recurring, low-churn, high-margin. | Insurers and venues have no equivalent product. Documentation of crowd density management during an incident is invaluable for liability. This is a category Eventbuoy creates. |
| Fan App | Real-time zone density, queue length, stage fill level, brand activation proximity | In-app crowd indicators per stage. "Stage 2 is 40% full — perfect time to grab a spot." Smart push notifications contextual to current crowd state. | Higher app engagement → higher brand push notification CTR → higher brand willingness to pay for activation package. Indirect but compounding. | No other festival app tells fans where the crowd is right now. This is the feature that drives app adoption and word-of-mouth before Eventbuoy has brand recognition. |
Three motions in 90 days only works because one event simultaneously generates proof for all three buyer types. The RuView mesh running at that event is the safety dashboard (organizer), the activation analytics (brand), and the platform data seed — all from the same hardware deployment.
| Motion | Revenue Type | Sales Cycle | First Dollar | RuView Unlock |
|---|---|---|---|---|
| White-Label Organizer | SaaS / Per-Event License | 4–8 weeks | Month 2 | Safety dashboard shortens sales cycle — bypasses budget committees, goes direct to ops |
| Brand Activation Brand/Agency | Campaign / Project Fees | 2–6 weeks | Month 1–2 | Foot traffic attribution = only data-backed activation offer in the market |
| Platform Ecosystem | Take-Rate + Data Licensing | Ongoing | Month 4+ | CSI dataset compounds — moat grows with every event added |
| Safety-as-a-Service New | Annual Compliance License | 6–12 weeks | Month 3+ | Standalone — sell crowd intelligence to venues, insurers, authorities with no app required |
2,000–5,000 attendees is enough to generate credible RuView data, a brand activation case study, and a white-label proof point simultaneously. Offer it at cost or free in exchange for full data rights and case study publication rights. The RuView deployment at that pilot is worth more than any sales deck you will ever produce.
./install.sh --profile iot --yes. Source mounting brackets for PA masts or scaffolding. Total hardware budget: $54–108.docker pull ruvnet/wifi-densepose:latest and configure UDP ingestion from ESP32 nodes. Set up WebSocket feed to Eventbuoy backend. Test full pipeline end-to-end before event day.sec_panic_motion.rs throughout — whether it triggers or not, the log is valuable for the safety case study.ret_dwell_heatmap.rs and ret_customer_flow.rs for activation zone analytics simultaneously.| Stream | Buyer | Pricing | RuView Component | Timeline |
|---|---|---|---|---|
| Per-Event White-Label | Festival organizer | $5K–$20K / event | Safety dashboard + heatmaps as premium tier — mesh hardware rental or organizer-owned | Month 2+ |
| Annual SaaS License | Recurring organizer | $30K–$80K / yr | Continuous mesh + cross-event analytics — venue fingerprint improves over time | Month 3+ |
| Brand Activation | Brand / agency | $10K–$50K / campaign | Activation zone dwell report — the only deliverable with real foot traffic data | Month 1–2 |
| MINY NFC Drops | Artist / brand | Production + platform fee | NFC tap = RuView zone data point enriching the audience profile | Month 2+ |
| Safety-as-a-Service New | Venue / insurer / authority | $15K–$40K / yr | RuView crowd density records — standalone compliance product, no app required | Month 3+ |
| Platform Take-Rate | Ecosystem | 5–15% on transactions | Volume funded by mesh-verified audience intelligence attracting more organizers | Month 4+ |
| Intelligence Licensing | Labels / promoters / venues | Custom | Cross-event CSI crowd behavior dataset — unique, compounds with every event | Month 6+ |
Outdoor festivals are episodic — the mesh deploys for a weekend, then leaves. Indoor venues are permanent. A nightclub, arena, conference centre, or hotel ballroom that installs the RuView mesh once gets a system that learns the space, improves with every event, and generates intelligence continuously. That changes the revenue model from per-event license to a hardware + annual SaaS bundle — and dramatically increases lifetime value per client. It also reconnects Eventbuoy to its original MICE roots, where the existing brand relationships and product history already exist.
Validate RuView live mode with physical hardware before pitching indoors. A LinkedIn commenter raised a flag that RuView's Docker simulation mode serves synthetic data, not live CSI — and they were unable to verify live sensing in their setup. CSI-based sensing is real and well-documented in academic literature, but RuView's production readiness for live ESP32 → server pipelines needs a real-world validation run before committing to a venue client. Run the hardware test: ESP32-S3 → UDP → sensing server → verify CSI packet flow in a real room. Don't demo to clients off simulation mode.
For crowd density at festival scale, passive WiFi probe request sensing (DBSCAN approach) remains the battle-tested fallback — accuracy up to 97%, no special hardware beyond a Raspberry Pi with monitor-mode adapter. RuView adds pose estimation and vital signs on top of that baseline. Use what's validated, layer in what's emerging.
sec_panic_motion.rs + ret_dwell_heatmap.rs + ret_queue_length.rs. Permanent ceiling install — one setup, every night. Brand activations (drinks sponsors, fashion brands) get dwell analytics identical to outdoor festival activation reports.
ret_shelf_engagement.rs (exhibitor booth = shelf) + ret_customer_flow.rs + bld_meeting_room.rs. Exhibitor ROI reporting becomes the brand activation equivalent for B2B events — same data, different buyer vocabulary.
sec_panic_motion.rs + ret_queue_length.rs + bld_elevator_count.rs. Also the highest-value white-label target — an arena running 200 events/year on a single mesh deployment generates data that no per-event system can match.
An outdoor festival client generates $5K–$20K per event, re-sold each time. An indoor venue client generates a one-time hardware install ($500–$2,000 for permanent mounting + nodes) plus $15K–$60K annual SaaS — recurring, compounding, and churning only if the venue closes. A nightclub running 250 nights/year on a single mesh installation generates 250× the data of a single festival deployment, which compounds the platform intelligence value proportionally. Indoor is lower per-event ticket size but dramatically higher LTV.
| Indoor Venue Type | Hardware (One-Time) | Annual SaaS | Primary RuView Value | Key Buyer |
|---|---|---|---|---|
| Nightclub / Music Venue | $500–$1,200 6–10 nodes, ceiling mount |
$15K–$30K/yr | Nightly crowd density, bar queues, panic detection, brand dwell reports | Venue ops manager + brand sponsor |
| Conference Centre / MICE | $800–$2,000 Per hall section |
$20K–$50K/yr | Exhibitor booth dwell, session attendance, registration queue, compliance docs | Event manager + exhibitors as secondary buyers |
| Arena / Concert Hall | $2,000–$5,000 Full venue grid |
$30K–$80K/yr | Section occupancy, egress modelling, panic detection, insurer compliance | Venue operator + insurer + local authority |
sec_panic_motion.rs module detecting fleeing and struggling movement patterns is something no camera-based festival safety system matches at this price point. Post-Astroworld, every major festival organizer is actively seeking exactly this. It's also the module that unlocks the Safety-as-a-Service revenue stream — a buyer category (risk managers, insurers) that no pure-app competitor can serve.