Skip to content
For fireworks display teams

Sound that arrives with the light.

From the far end of the shoreline, the boom shows up a second late — and PA music arrives with it. PulseMesh puts your soundtrack on every spectator's phone, locked to the firing script, so the music lands with the flash, not after it.

±10mssync for every spectator
0speakers to rent or rig
anydistance from the launch site
Fig. 5 — The soundtrack outruns the boom
Your firing scriptCloud Player · firing-system playback · SMPTE timecode (soon)MASTER
PulseMesh sync engineone clock for the sky and the crowdCLOUD
  • Spectator phones — geo or QR entry±10ms
  • Car stereos at the tailgatedelay-compensated
  • Bluetooth speakers on the blanketdelay-compensated

No stacks to rig, no broadcast license — the crowd brings the speakers.

01 / THE PROBLEM

Physics is against your PA

A shell bursts at 800 feet over the water. Your audience is spread along a mile of shoreline. No speaker stack can serve them all at once.

// The usual options

  • Speaker stacks fight the speed of sound — at 1,000 feet the music runs a full second behind the burst
  • Covering a shoreline or a stadium lot means delay towers, generators, cabling, and crew at every show
  • Water, barges, and closed fallout perimeters put speakers exactly where you can't
  • FM broadcast: licensing, hardware, and an audience that no longer carries radios

// With PulseMesh

  • Every phone plays within ±10ms of the firing script — the last row hears what the front row hears
  • Zero audio infrastructure at the site — nothing to barge in, power up, or tear down at midnight
  • Distance stops mattering: shoreline crowds, rooftop watchers, and the overflow lot all stay on the beat
  • Spectators connect by GPS or a QR on signage and tickets — any browser, no app required
NO INTEGRATION REQUIRED

Start with the Cloud Player

Upload your soundtrack, open your dashboard, and press play on the first cue. Your first synced show needs no timecode and no firing-system integration — add those later if you want them.

See how it works
02 / WORKFLOW

From load-in to finale

STEP_01

Create your show site

Define the venue and audience geo-radius in the dashboard — the lakefront, the stadium, the fairgrounds.

STEP_02

Load your soundtrack

Upload it to the Cloud Player for one-button playback — or sync to your firing system or SMPTE timecode. Soon

STEP_03

Point spectators at the sky

Guests inside the geo-radius connect automatically; QR codes on signage and tickets catch everyone else.

STEP_04

Fire

The music locks to the show on every phone, first cue to finale. Afterward: attendance and engagement numbers in your analytics.

03 / FIELD CONDITIONS

Built for show sites, not server rooms

Remote-site ready

Runs from a cellular hotspot at ~2MB/hour, and sync holds even on the congested networks of a packed venue.

Crowd-scale by default

A county fair or a city waterfront — capacity lives in the cloud, not in gear you truck to the site.

Geo-fenced connection

Spectators inside your show radius connect automatically — no codes to distribute, no frequency to announce.

Car audio compensated

For tailgate-style viewing, automatic Bluetooth delay compensation keeps CarPlay and Android Auto on the beat.

Licensing included

US performance rights (ASCAP, BMI, SESAC) handled automatically on commercial plans — one less contract per event.

Prove the turnout

Per-show analytics — connected listeners, peak concurrency, dwell time — become the numbers in your next client proposal.

Give the finale its soundtrack.

Tell us about your operation — show sizes, venues, and firing systems — and we'll set you up with a pilot event.