All work

Professional · Next.js

TrackThirtyTwo

A subscription product rather than a brand site: tiered memberships for sim racers, with live telemetry, hardware integrations and an iOS companion app, designed and built end to end as a side project. Launched as Daniel Newman Racing, since renamed TrackThirtyTwo.

Type
Professional
Started
October 2025
Status
Live
Stack
10 tools
Preview
Screenshot
TrackThirtyTwo, screenshot

Problem

What it had to solve

A sim-racing hardware brand needed a subscription product: tiered memberships priced per licence, live telemetry from the rig into overlays and dashboards, and race-day controls on hardware, all reading from one source of truth so nothing drifts out of sync on race day.

I was the sole engineer through the early months; the owner contributes to the codebase now too. My later work there turned to what it costs to run and how fast it responds.

Decisions

The calls and their trade-offs
  1. Telemetry in its own service, not in the web app

    The Next.js app runs on Vercel, where each request is handled by a short-lived function that cannot hold the long-lived connections live telemetry needs. So telemetry runs as a separate Socket.IO service with Redis behind it, feeding the overlays, dashboards and hardware integrations, while the web app stays serverless.

  2. Licences and devices checked against Stripe's state

    Stripe is the source of truth for what a customer has paid for, and licence and per-plan device limits are enforced against that state. 21 scheduled cron jobs carry the billing lifecycle, league holds and iRacing member sync.

  3. Profile first, then fix the one query that mattered

    Profiling showed a single aggregation dominated database time. A covering index plus caching took it off the hot path.

  4. Middleware only where it is needed

    A middleware matcher bug was invoking middleware on requests that did not need it. Tightening the matcher removed those calls without changing what any page does.

  5. Size the database to memory, not CPU

    Peak-hour data showed memory, not CPU, was the real constraint, so the database plan was chosen for its working set rather than its processor.

Outcomes

What changed
  • 98%less database CPU on the hottest query
  • 84%fewer middleware invocations
  • ~60%smaller stored dataset
  • 96%fewer error groups
  • 20,000+ sign-ups and 8,000+ racers in its Discord, with the tooling used by an Indy 500 champion, a Rolex Daytona winner and an Esports World Champion.

Screens

04 captures
TrackThirtyTwo screen 1
TrackThirtyTwo screen 2
TrackThirtyTwo screen 3
TrackThirtyTwo screen 4

What it's made of

5 products, one ecosystem
  • CORE

    Subscription Platform

    Tiered memberships with monthly and annual billing, per-licence device limits, and an enterprise plan, on Clerk and Stripe.

  • 02

    Telemetry Pipeline

    A dedicated WebSocket service and SimHub plugin streaming live rig telemetry into custom overlays and dashboards.

  • 03

    Stream Deck App

    Race-day controls and live status, one button-press away.

  • 04

    Ulanzi Dock App

    A second hardware integration for race-day status and controls.

  • 05

    iOS App

    A companion app for checking status and results away from the rig.

Details

How it was built
  • Three subscription tiers with monthly and annual billing, priced per licence, plus a separate enterprise offering
  • Authentication, checkout, and customer billing on Clerk and Stripe, with VAT-exclusive pricing for international customers and GDPR-compliant consent management
  • A SimHub plugin plus Stream Deck and Ulanzi Dock integrations for race-day control, and an iOS companion app for status and results away from the rig
  • A league and esports system, a downloads and changelog pipeline, and a support knowledge base
  • Bot mitigation via Cloudflare Turnstile and a hand-tuned Content Security Policy locking the app to known origins
  • Background jobs on BullMQ and Redis, and ClamAV malware scanning on every upload
  • 551 automated tests and 5 GitHub Actions CI/CD pipelines covering the web app, the WebSocket service, and the Discord bot

Six products across one ecosystem, covering 600+ cars with real RPM and redline data and 100+ LED profiles, supporting iRacing, ACC, Le Mans Ultimate, EA F1, AMS2 and WRC. Over 20,000 sign-ups on the web app and 8,000+ racers in its Discord, and the tooling is used by drivers including an Indy 500 champion, a Rolex Daytona winner, and an Esports World Champion.

Stack

10 tools
  • Next.js
  • TypeScript
  • MongoDB
  • Clerk
  • Stripe
  • Socket.IO
  • BullMQ
  • Redis
  • SimHub Plugin SDK
  • Vercel