A free Splunk app · built by a dad and his daughter who never miss a race

Learn Splunk by replaying a real Formula 1 Grand Prix.

Install one free app and a real race is already moving inside Splunk: the 2025 Italian GP, 20 cars at 3.7 Hz on a circuit rebuilt from the cars' own GPS, with the SPL behind every panel.

Get SPLap free on Splunkbase See it move

Install it, open it, Monza is already moving. No API key, no data prep, no internet needed.

Free · Apache-2.0 · no LLM · real telemetry, reproducible SPL · not affiliated with Splunk or Formula 1 · Campaigning for a spot at .conf26 Denver

Real 2025 Italian GP data · a race that moves · SPL on every panel · 17 sourcetypes · no LLM · AppInspect-validated · free on Splunkbase

NOR lap 48 vs PIA lap 47 · aligned by distance+0.207seconds at the line · observed lap times

Telemetry rows122,300location + car data

Searches per frame0replay runs in the browser

Corners from GPS115,745 m centreline · pit lane too

See it move

The race is the demo.

Twenty-five seconds recorded from a stock Splunk Enterprise 10 install, nothing staged. The loop at the top of the page is the Pit Wall doing the same thing with all 20 cars.

25 seconds, start to finishSomeone put a real Grand Prix inside Splunk. Muted, captioned; press play if it does not start on its own.

0:03Pit Wall: the 2025 Italian GP replaying, Norris into the pit lane on lap 46, timing tower and driver card live.
0:09Position Worm: the whole race on one chart. Hover a moment, click it, and the replay jumps there.
0:14Show SPL on the timing tower: the query, the fields, rows scanned and runtime. Copy it or open it in Search.
0:19Lap Delta: NOR lap 48 against PIA lap 47, aligned by distance. 0.207 s at the line, and the corner table shows where it came from.

Twenty more secondsLap Delta, corner by corner, then an Incident Review window playing. Muted; press play if it does not start on its own.

Rated 5.0 by Splunk users on Splunkbase

Get SPLap free on Splunkbase

Installs in a minute. Nothing to configure. If it earns one, an honest rating over there is what keeps a two-person project visible.

Why we built it

Built on Sundays by two people who never miss a race.

Lilli wanted to see if the timing screen was lying to us.

She also wanted to learn how real software gets built: the kind with tests and a release and strangers installing it. Lloyd wanted an excuse to model race physics. Neither of us expected the circuit map to come out of the cars' own GPS, or that a Monza pit stop would show up in the data as clearly as it does on TV.

Splunk turned out to be a great place to do it. It swallows a hundred thousand telemetry events without blinking, its search language was made for exactly these time-series questions, and its dashboards let us draw a race instead of a bar chart. We aren't affiliated with Splunk in any way; we just think it's a good platform for this.

What is on Splunkbase today is the groundwork: a clean data model, a real session, the whole race on one chart, deterministic race-engineer findings you can check. The physics is next.

Lloyd Clark & LilliCo-developers · weekends, 2026

What's inside · version 2.3.0

Grounded in the data, not the vibes.

Everything on screen is either observed provider data or labelled as derived. Every chart has a Show SPL button. Nothing is generated by a language model.

13:00:00DATA2025 Italian Grand Prix, Monza, from the community OpenF1 API: laps, sectors, stints, pit stops, positions, intervals, race control, weather, overtakes, team radio, and 3.7 Hz location + car telemetry (speed, RPM, gear, throttle, brake, DRS). Bundled as lookups; import any other session yourself.

14:00:00CIRCUITGeometry derived from the cars' GPS: centreline, pit lane as its own road, sector boundaries, DRS zones, numbered corners. No official track art.

14:00:17PIT WALLHybrid SVG + Canvas renderer, livery-coloured cars with collision-aware labels, timing tower with gap and interval, driver card, 0.25×–4× replay, jump to pit / overtake / flag. Zero searches per animation frame.

14:00:33INCIDENT"Turn 5 incident involving cars 55 (SAI) and 87 (BEA) noted." A 30-second evidence window around any race-control message, overtake or pit stop, with map, both cars' telemetry, gaps and weather on one cursor.

14:04:10WORMPosition Worm: all 20 drivers, all 53 laps, one canvas. Pit stops dotted, safety-car periods shaded, the telemetry window highlighted. Click any moment and the replay jumps there.

14:05:52LAP DELTAAny two laps aligned by distance. Click a corner for braking point, minimum speed, throttle reapplication and time gained or lost.

14:07:14ENGINEERDeterministic findings (pit-loss anomaly, undercut/overcut, tyre degradation change, battle closing rate, braking-point change), each with rule version, confidence, provenance, evidence and the SPL that reproduces it.

··:··SCHEMAsplap.canonical/1: one index, 17 sourcetypes, provenance on every event, idempotent import id. Import wizard in the browser, offline race bundles with checksums, or a Python CLI. Credentials never touch browser code.

Engineering notes, published: Canonical data schema · Data sources · Importing a race · Visualization architecture · Reading room. The package also ships the full release evidence (AppInspect, clean install, browser suite).

Position Worm: all 20 drivers' positions across all 53 laps of the 2025 Italian GP on one chart, with pit stops dotted and the telemetry window highlighted — **Position Worm**The whole race on one canvas: every position change, pit stop and flag for all 20 drivers. Click any moment and the replay jumps there.Open full size

Lap Delta: NOR lap 48 against PIA lap 47 with speed, throttle, brake, gear, RPM and cumulative delta traces aligned by distance — **Lap Delta**NOR 48 vs PIA 47, aligned by distance: 0.207 s at the line, corner by corner.Open full size

Incident Review: a race-control message with both cars highlighted on the circuit map and their telemetry below — **Incident Review**One race-control message, both cars on the map, 30 seconds of telemetry on one cursor.Open full size

If you build on Splunk

Zero searches per frame

The replay is precomputed into frames and drawn on Canvas; SPL builds the world, the browser runs it. No SearchManager in the animation loop.

One schema, provenance on every event

splap.canonical/1: 17 sourcetypes, each event tagged observed or derived, idempotent import ids so a re-import cannot double-count.

Findings you can reproduce

Every race-engineer finding carries a rule id, version, confidence and the exact SPL. No language model anywhere in the pipeline.

Next release · in the garage

Next: the physics.

2.2 is the data foundation. The next version turns SPLap from a viewer into something you can argue with: every model labelled with its confidence and its SPL, same as today.

Tyres
Degradation curves
Lap time versus tyre age per compound and stint, with fuel load and traffic corrected out. "This stint is losing 0.08 s per lap", with error bars.
Strategy
Undercut simulator
Drag a pit stop on the timeline and watch the projected running order, built on the pit-loss we measure and the degradation we fit.
Driving
Corner-by-corner analysis
"VER brakes 8 m later into Turn 1 than NOR." Braking points, minimum speeds and throttle pickup projected onto the track.
Energy
Deployment inference
Where the battery is spent on the straights, inferred from speed and throttle traces.
Race story · shipped in 2.2
The position worm
Lap-by-lap positions for the whole field with overtakes and stops marked; click anywhere to seek the replay. Done, and on Splunkbase now.
What-if
Re-run the race
Change one strategy call and watch the race replay under the new plan. The big one.

Stint ordersoftmediumhard

The learning lab · nobody is born knowing Splunk

A Grand Prix is a better SPL tutorial than another security log.

SPLap was built by a dad and his daughter partly so she could learn how real software gets shipped. It works just as well the other way around: a whole Grand Prix of real data to poke at is a pretty good first date with SPL, time-series analysis and telemetry, at any age.

A friendly first Splunk app

Nothing to configure, no accounts, no internet needed, and an Install Doctor inside that runs 28 checks and tells you in plain words if anything is off. If SPLap is your first ever Splunk app, it will hold your hand.

Learn by asking the data

Every chart has a Show SPL button: the real query, explained. Copy it, change one thing, run it again. That loop, question, query, evidence, is data science; the F1 wrapper just makes you want to do it. The SPL Garage and Labs pages ship guided challenges with answers you can check.

For kids, and their adults

Free, offline, no chat, no sign-ups, nothing to buy. A curious kid can ask "who was actually fastest into Turn 1?" and get a defensible answer from real telemetry. Teachers and parents: the engineering notes and reading room go as deep as anyone wants.

What you can count on

No API key
No LLM
No internet after install
Bundled real session
Reproducible SPL on every panel
28-check Install Doctor
Apache-2.0
No telemetry sent anywhere

Useful for learning SPL, for demos, and for the same time-series, telemetry and IoT questions you would ask of a pump, a turbine or a drone. Every claim on this page is checked against the bundled data before it goes live.

Get SPLap free on Splunkbase Take the Monza challenge

Get it

Install in a minute.

Never touched Splunk? That is fine. There is no configuration step to get wrong: install, open, and Monza is already moving.

1
Grab the package from Splunkbase.
2
Splunk Web → Apps → Manage Apps → Install app from file, and pick the file you just downloaded. Or splunk install app <that file>.
3
Open SPLap. Monza is already moving. No setup page, no index, no internet.
4
Want a different race? Connect Data → Import Historical Race, pick a season and a Grand Prix.

Splunk Enterprise 10.x and Splunk Cloud Platform (AppInspect-validated).

No Splunk? Ten minutes on a laptop

Splunk Enterprise has a free trial and runs fine in Docker. Download SPLap from Splunkbase first, then three commands and Monza is moving (replace the path in the second one with the file you downloaded):

docker run -d --name splap -p 8000:8000 -e SPLUNK_START_ARGS=--accept-license -e SPLUNK_PASSWORD=ChangeMe-123 splunk/splunk:latest
docker cp "<the file you downloaded>" splap:/tmp/splap.tgz && docker exec splap sudo /opt/splunk/bin/splunk install app /tmp/splap.tgz -auth admin:ChangeMe-123
open http://localhost:8000/en-US/app/splap/pit_wall

Feedback

Tell us what you'd like to see.

Questions

Things people ask.

Is SPLap good for learning Splunk or data science?

Yes, that is half the point. It was built by a dad and his daughter as a learning project. It needs no configuration, ships with an Install Doctor, shows the SPL behind every chart, and includes guided Labs challenges. Free, offline, no accounts. See the learning lab.

Is SPLap affiliated with Splunk or Formula 1?

No. It is an independent, non-commercial project by two people who like both. Splunk is a trademark of Splunk LLC; Formula 1 marks belong to their owners. We just think Splunk is a good platform for this kind of time-series work.

Is it free?

Yes. Apache-2.0 licensed, free on Splunkbase, no keys, no sign-up, no telemetry sent anywhere.

Does it need internet access?

No. The 2025 Italian Grand Prix ships inside the package as lookups. Internet is only needed if you choose to import another session from the OpenF1 API.

Does it use AI or a language model?

No. Every finding comes from a deterministic rule with a version, a confidence and the SPL that reproduces it. Nothing on screen is generated.

Which Splunk versions does it run on?

Splunk Enterprise 10.x and Splunk Cloud Platform. It passed AppInspect for both. The free Splunk Enterprise trial in Docker runs it on a laptop.

Can I load a different race?

Yes. Connect Data, then Import Historical Race: pick a season, a Grand Prix and a session. Or use an offline bundle, or the Python CLI. Every import gets an idempotent id so re-importing cannot double-count.

Where does the data come from?

The community OpenF1 API under its non-commercial terms: laps, sectors, stints, pit stops, positions, intervals, race control, weather, team radio and 3.7 Hz location and car telemetry. The circuit geometry is derived from the cars' own GPS, not from official track art.

Who built it?

Lloyd Clark and his daughter Lilli, on weekends, as a way to learn how real software gets shipped and to lay the groundwork for modelling race physics.

Is there something to try once it is installed?

Yes. The Monza challenge is three questions you answer with the bundled race and the Show SPL button: where a lap was won, what a slow pit stop cost, and whether the telemetry backs up a stewards' call. Send your answer or a screenshot and join the Founding Pit Wall.

How do I rate it or report a problem?

Ratings live on the Splunkbase listing (you need a Splunk account). Problems go to lc@federal.ai; the Install Doctor page inside the app copies a secret-redacted diagnostic bundle you can paste in. Honest ratings only, please: a rough edge you tell us about is worth more than a polite five.