Inside the client portal

“You get a portal” is easy to say and hard to check, so here it is. These are the three views a tuning client lives in, rendered from the same components and design tokens as the real thing — filled with sample data instead of somebody's car.

Sample data. This is a realistic but fabricated engagement built to show the format of the deliverable — not a real customer's car, and not a real customer's numbers.

1. The changelog

Every revision ever issued on your car, in order, with its status. Nothing is retired or overwritten — a validated revision is locked and stays in the history. This is what we mean when we say nothing lives in one tuner's head.

Sample data

Client Portal

Tune revisions

Each revision is a set of exact changes to enter, validate with a log, and move on from. One variable at a time.

Revision 4 — WOT fuel correction + timing pull at 220 kPa

Nine changes to enter now, two held for the boost step. WOT band was 4% lean; three knock events on cylinders 5–6 once IAT passed 45 °C.

Jul 27 · 0/11 changes entered

Ready to enter

Revision 3 — Transient enrichment + wastegate feed-forward

Killed the tip-in stumble out of 2nd and cut boost overshoot from 2.1 psi to 0.6 psi. Validated on the Jul 24 log.

Jul 20 · 7/7 changes entered

Validated

Revision 2 — Idle, cruise fuel trim and cold-start enrichment

Cruise cells brought to 14.7:1 and the cold-start table reshaped — first-crank-to-idle now settles in under 4 seconds at 8 °C.

Jul 13 · 11/11 changes entered

Validated

Revision 1 — Baseline review, safety gates and rollback point

Full backup taken before anything was touched. Hard limits set for this build: 11.6:1 WOT ceiling, knock threshold, 85% duty limit, 20 psi program ceiling.

Jul 6 · 6/6 changes entered

Validated
Revision list at /client/revisions — statuses are Ready to enter, Entered — awaiting validation, and Validated.

2. A session report

Open a revision and you get the itemized changes: the exact table, the exact cell, the old value, the new value, and why. You tick each one off as you enter it, then upload the validation log. No vague advice — numbers you can type in.

Sample data

Client Portal

Revision 4

WOT fuel correction + timing pull at 220 kPa · from session-04_wot-pulls.csv

Changes to enter
4/11 entered
TableCellOld → NewWhyEntered
Main Fuel (VE)4,800 RPM · 220 kPa88.4 → 92.3Pull 3 logged 11.9:1 against an 11.4:1 target — the leanest point in the session. +4.4% VE puts the cell on target.
Main Fuel (VE)5,200 RPM · 220 kPa90.1 → 93.7Same pull, 11.85:1 measured. +4.0% VE — the table's shape is right, its magnitude is short where the turbos come fully on.
Main Fuel (VE)5,600 RPM · 220 kPa91.6 → 94.411.75:1 measured across all three pulls. +3.1% VE onto target.
Main Fuel (VE)6,400 RPM · 220 kPa89.2 → 86.5Richer than commanded at 11.05:1 — costing a little power without buying safety. −3.0% onto target; still well inside the 11.6:1 lean ceiling.
Ignition Angle5,600 RPM · 220 kPa19.5° → 18.5°Three knock events on cylinders 5 and 6 in this window, peaking 0.42 V over the noise floor, all on the third pull once IAT passed 45 °C. −1.0° at the cell that knocked.
Ignition Angle6,000 RPM · 220 kPa20.0° → 19.0°The knock window carried into this cell. Matching the 1.0° pull keeps the curve smooth rather than putting a notch in it.
Ignition Angle6,400 RPM · 220 kPa20.5° → 19.5°Precautionary 1.0° so the top of the curve stays consistent with the two cells below it. We revisit this once we have an IAT-matched log.
+ 4 more rows in the full revision.
Validation log

Drive the same capture set as your last session and upload the log so we can confirm the changes did what they should.

Drop a log file here, or browse
Revision detail at /client/revisions/[id] — the same rows we store per change, with a tick box each and the validation-log upload underneath.

The written deliverable that accompanies this revision — verdict, safety-gate results, and all eleven change rows — is published in full at the sample session report.

3. Metrics over time

The same measurements taken the same way on every logged session, so progress is a trend line rather than a feeling. Boost climbing while knock events fall is the shape of a tune going the right way.

Sample data

Client Portal

Metrics over time

Every logged session, measured the same way. This is how you can tell the tune is going somewhere.

Peak boost

17.0 psi

Target: 20 psi program ceiling

Peak boost by session, Jun 29 to Jul 27
Jun 29Jul 27

Climbing in approved steps — never more than one step per validated log.

Knock events

3 events

Target: 0 above threshold

Knock events by session, Jun 29 to Jul 27
Jun 29Jul 27

Falling while boost rises — the point of the exercise.

Leanest WOT air/fuel

11.9:1

Target: 11.4:1 target · 11.6:1 ceiling

Leanest WOT air/fuel by session, Jun 29 to Jul 27
Jun 29Jul 27

Approaching target from the safe side. Still 0.3 outside the ceiling — corrected in Revision 4.

AFR spread across the pull

0.45 AFR

Target: ≤ 0.30 AFR

AFR spread across the pull by session, Jun 29 to Jul 27
Jun 29Jul 27

How flat the mixture holds from spool to limiter — the real measure of a dialled-in fuel table.

Session by session
Every metric plotted above, as numbers, one column per logged session.
MetricJun 29Jul 6Jul 13Jul 20Jul 27
Peak boost (psi)11.812.014.215.417.0
Knock events (per session)149643
Leanest WOT air/fuel (:1)12.612.412.112.011.9
AFR spread across the pull (AFR)1.100.900.700.550.45
Metrics view — one chart per measure, plus the underlying numbers, because a line you can't check isn't evidence.

This is the documentation trail every engagement gets.

Start with an intake and we'll tell you honestly whether your car is ready for it.

See remote tuning