
Sly Paddock Sim Racing Platform
Server provision time
< 40 sec
Real regions
10
Pace tiers
7
Sessions recorded
100%
Overview
Point it at a track, pick a car and a mode, and it spins up a real dedicated server in under 40 seconds, opens the ports, and starts ingesting results the moment the session ends. Every lap comes back scored against a reference and dropped into a pace tier. You share the password, your friends join from in-game, and the leaderboard writes itself.
It is a managed platform, not a control panel bolted onto a rented box: Slytrunk provisions the VM, runs the game binary, handles Steam identity linking, and turns raw session data into standings - for Assetto Corsa EVO and ACC today, with AC1 on the roadmap. It runs on Google Cloud with real Stripe payments. Sly Paddock is the second project out of Slytrunk Labs: take a category everyone had accepted as fiddly and rebuild it until spinning up a race and keeping the data takes one form and under a minute.
The challenge
And the market is genuinely hard. Hosting is commoditized and priced to the floor. SimGrid already runs the hosting-plus-Discord-plus-results loop across 12+ titles at 2,800+ communities. Winning here isn't about doing more things - it's about doing a few things, on a few titles, impossibly well, and being found for them.
What we built
01 · A server in under 40 seconds
A warm VM pool means provision time is a concrete, measurable number - under 40 seconds - where competitors just claim "instant." Status flows in the open: scheduled → starting → running → connected, polled until clients can actually join.
02 · 10 real regions
US East/West, Canada, UK, Germany, Belgium, Japan, Singapore, Australia and Brazil - the VM comes up close to your grid.
03 · Results that stick, performance quantified
The game POSTs to a webhook on session end; Sly Paddock ingests it automatically. Every lap is scored against a reference and clustered into one of seven pace tiers - Alien through Learning. Alien is a lap within 100.5% of the fastest recorded time.
04 · Depth on the Kunos titles - and a cut line
AC EVO and ACC are hosted; AC1 is next. iRacing and Le Mans Ultimate are structurally closed to self-hosting, so they're treated as link-out rounds, never hosting targets - a deliberate scope decision, not an oversight.

One
The product is Slytrunk's design work, not a template. The brand and identity, the marketing surface, and the product's original systems are ours - the seven-tier pace model, the create-a-server flow with cascading track/layout/mode selectors that stay valid as you pick, the leaderboard drill-down from grid to sector - designed from the racer's job backward.
Two
Slytrunk leveraged Claude across the entire stack to implement that design:
The backend - a Fastify/TypeScript service on Cloud Run - servers, results, admin, auth, payments, developer API, ingest and replay.
The frontend - a Next.js surface with a full design system - hero, narrative panels, steps, standings, pricing, track maps.
The hard layer - the dedicated-server path: Docker image and startup that provisions the AC EVO binary on demand, including reverse-engineering of the server's proto-derived config schema and log format.
Infrastructure and data - Terraform for GCP and a BigQuery ingest/leaderboard pipeline with a game-agnostic schema so new titles are an additive column, not a migration.
Where it stands
Live for AC EVO and ACC with real Stripe payments, real GCP hosting, and a validated free-and-paid tier model.
AC1 support, a results/points/standings engine, and bundled league-ops are sequenced next - built only behind real demand.
SEO is the acquisition play: a thin-margin hosting business has to be found, not bought.
Contact
Next