Independent. Engineer-led. Proven in production.
PulseMesh is an independent synchronized media platform built for displays, events, and live productions. Here's how it started, how it's engineered, and the production record behind the technology.
The numbers come first
Production figures are measured directly from real deployments — the same numbers, counted the same way, that we publish in the field reports. Capacity is validated separately, through load testing.
Attendance estimates and device counts are two different measurements, and we never convert one into the other. See the deployments → · How we count →
Started at one house. Scaled to the national stage.
PulseMesh started with a question every display operator eventually asks: a synchronized show deserves synchronized audio — so why is that still hard? FM works, but it comes with tradeoffs: transmitter hardware, limited coverage, regulatory constraints, and no direct connection to the devices your audience is already carrying.
So we built the answer we wanted for displays: every phone in the audience on one clock, with playback averaging within ±10ms of source timing — no transmitter, no PA, no app-store friction for viewers.
The holiday-lights community shaped the product from the first season. What it became — a synchronized experience platform for drone shows, fireworks, screens, and live production — grew out of the same engine, hardened by every season since.
- Early 2024
Built for our own display
The first sync engine runs on a single residential light show — because the FM transmitter had to go.
- October 2024
Open beta, a full season in the field
The open beta launches in time for the season, and displays across the US run PulseMesh free through the holidays, with plugins for FPP and xSchedule. The community files the bugs; we fix them fast.
- 2025
A real product, a real season
Paid plans launch with built-in US performance licensing. 1,492 displays across 34 countries later, the platform has its first production season on record.
- 2026
Beyond the lights
The 2026 National Jamboree fireworks run on PulseMesh — 915 simultaneous devices at a ~12,000-person event. Drone shows, fireworks, screens, and timecode for live production join the platform.
Designed to run unattended
Your event never depends on someone at PulseMesh doing something at showtime. Synchronization, scaling, recovery, and geographic placement are automated — the platform is engineered the way broadcast infrastructure is: to run, not to be run.
Shows run themselves
Sync, scaling, recovery, and geographic placement are automated. The system that served every deployment on this page was designed to run unattended — and yours is too.
Distributed by design
PulseMesh operates across multiple independent infrastructure providers — including Cloudflare and Oracle Cloud — reducing reliance on any single hosting environment. Audio and sync timing are served from a global edge network, near your audience, and capacity is validated in load testing to 20,000 devices per show — before the season, not during your event.
Direct show-night support
Automated monitoring runs season-round for every display. For major events, staffed show support is available as an option — your show's telemetry monitored live for the duration of the event, with a direct line if anything needs attention.
Ready for procurement
PulseMesh LLC, registered in Ohio. Standard terms, privacy documentation, commercial agreements, and versioned legal acceptance are already in place — security questionnaires and custom procurement requests are handled directly.
Answers before you ask
The questions that come up in vendor review, answered up front. Anything deeper — reference calls, security questionnaires, custom terms — is handled directly.
Can PulseMesh support custom commercial agreements?
Yes. Beyond the self-serve plans, commercial and event engagements can run on negotiated agreements — custom terms, capacity commitments, invoicing, and event-specific support arrangements, with a signed contract and a direct line. White-label options for the web player and apps are available for commercial deployments.
How does deployment preparation work?
Events get a pre-show verification run — connectivity, placement, and sync checked against your actual venue and show source before doors open. It's the same process used for the 2026 National Jamboree.
Can we talk to references?
Yes — reference conversations with operators running PulseMesh in production can be arranged. The field reports also document named deployments, with an explanation of exactly how each number was measured.
How is audience data handled?
Listeners join by QR code, GPS, or NFC — no account, no personal profile required. Precise location is used only with device permission, for nearby-show discovery and listening-radius checks — and is never used for advertising or sold. Beyond that, PulseMesh collects the technical and usage data needed to operate the service and provide show analytics, as described in our Privacy Policy.
What happens if connectivity is interrupted?
Devices fetch audio ahead of the moment it's needed and continuously correct against the show clock, so playback rides through congested networks. And in audience-audio deployments, your existing show controller keeps running the show locally — PulseMesh doesn't need to sit in its critical control path.
What U.S. performance licensing is included?
PulseMesh holds blanket US performance-rights agreements with ASCAP, BMI, and SESAC covering audio played through the PulseMesh site and apps. Licensing is included with commercial plans — no separate paperwork, no per-event filings.
Built from show-night experience
Bob has spent more than a decade building and operating production software and distributed systems at companies including AWS and Mapbox — and runs his own synchronized holiday display, which is exactly why PulseMesh works the way it does. Every feature starts with a real operational need, and the platform is developed with show-night conditions in mind from the beginning.
That engineering-first approach shows up where it counts: support stays close to the engineering, so technical questions don't disappear into layers of account management or outsourced support — and when something matters for your event, the path to a technical decision is short.
Let's talk about your show
Questions a page can't answer — reference calls, pilot events, procurement paperwork — get a direct answer.