Role: Full-stack engineer & architect Stack: TypeScript, Next.js, tRPC, PostgreSQL, Redis, Cloudflare Workers

SparkMotion is a multi-tenant platform that turns NFC wristbands into a dynamic engagement channel for live events. When an attendee taps their wristband, they're redirected to different experiences depending on where the event is in its timeline pre-show, live, or post-show with geo-aware routing and per-event customization.

A single tour stop can host 200,000 attendees generating 600,000+ taps in one night, roughly 18 million taps across the full tour. Every tap needs a sub-second redirect, and every tap must be captured for analytics. A conventional server-side approach would buckle under that burst load and drive infrastructure costs through the roof.

Edge-first routing. Redirect decisions are resolved at the network edge, closest to the attendee, so the vast majority of taps never touch an origin server. The result: sub-15ms redirects that hold up under stadium-scale bursts, and a system that keeps working even if the origin goes down entirely.

Burst-tolerant analytics. Tap data is captured thpeline designed to absorb massive spikes withoutputting the database in the hot path. Analytics stay complete and accurate at full tour scale while the write load on the core database stays flat.

Cost-aware by design. The data layer is structuret and storage costs stay predictable as tap volumegrows into the tens of millions, without sacrificing historical reporting.

Multi-tenant SaaS structure. Separate admin and customer portals give the platform operator a global view while each organization manages its own events, campaigns, and wristband cess, recovery-friendly deletion, andtransactional email built in.

Load-tested at up to 25,000 concurrent virtual users against a 200,000-band dataset, verifying redirect latency and ingestion throughput before opening night.

Results

Sub-15ms redirects for the vast majority of liv

600K taps per event absorbed with no database pressure

Resilient by design: redirects keep working evene

One codebase powering the edge layer, attendee routing, and both portals