The GAINS app

Tune by describing how it drives.

Say what you feel. GAINS turns it into a precise, typed request, checks it against fixed safety rules, and asks you before anything changes. The engine's real-time control never depends on the phone or the network.

iOS prototype · simulated data It doesn't connect to a car yet. Not on the App Store.

Ask GAINS
Simulated
Listening…
Hold to talk
Ask · check · approve · read back

AI suggests.
Fixed rules decide.

Every request, whether it comes from you, the AI or on-ECU learning, is only a proposal. A deterministic policy engine and the ECU itself decide what is allowed. Nothing reaches the engine without passing both.

Language model · untrusted Policy engine · deterministic ECU · re-validates, final say
  1. 01
    Ask

    You say how it feels.

    “Feels flat around four grand under boost. Can you richen it a touch?” Voice or text. Words in, nothing changed yet.

  2. 02
    Intent

    It becomes a typed request.

    The language model (or the offline parser) can only fill a fixed form: what to change, where, how much. Its output is untrusted.

    { goal: "richen_fuel", rpm: [3750, 4500], kPa: [145, 175], size: "small" }
  3. 03
    Plan

    A planner sizes the change.

    Six fuel cells, +3.2 % on average, capped at +4 % per cell, built from the last two pulls that ran lean of target.

  4. 04
    Policy

    Fixed rules decide, not the AI.

    The deterministic policy engine checks the envelope, the change class, your role and the car's state. A request for more timing on the street is refused outright.

    AllowedFuel +3.2 % · inside envelope · apply when stopped
    Refused“Add 4° of timing” while driving · ignition is dyno-only · nothing sent
  5. 05
    Approve

    You approve it, at a stop.

    Changes that need a stop wait until the ECU reports the car is stationary. Then you hold to approve.

    The approve button stays locked.
  6. 06
    Read-back

    The ECU checks again and confirms.

    The ECU re-validates against its own limits, applies it, and reads back what it applied. Undo is one tap.

    Requested
    6 cells · +3.2 % avg
    ECU limit check
    Pass
    Read back
    Waiting for your approval
Ask GAINS
Simulated
Understanding…
Feels flat around four grand under boost. Can you richen it a touch?
Hold to talk
Simulated · your approval does nothing outside this page
Live

Every number that matters.
Lambda against target, always.

Rpm, boost, ignition, knock and coolant, with λ shown against its target so you can see the lean spot the driver felt. About 20 updates a second, drawn at display rate.

GAINSECU2 · simulatedLearning
3GEAR
4,490 rpmShift at 7,200
Lambda · actual vs targetOn target
0.84 λtarget 0.82
Boost167 kPa
Coolant92 °C
Ignition23.9 °
Knock0.0 °
λ actual vs target · last 4 sSimulated data
λ 0.80λ 0.90λ 1.00
λ0.84Target0.82Rpm4,490kPa167

The phone only watches. Fuel, spark and boost control run on the ECU and keep running if the phone, Bluetooth or the network drops.

On-ECU learning

It learns while you drive.
Inside a fence it can't cross.

Fuel learning runs on the ECU, cell by cell, from the onboard wideband. Each cell moves in small steps inside a signed envelope. Ignition stays locked. You decide what gets promoted into the base map.

Fuel map · trims learned (16 × 10 cells)Simulated data
1,0004,0007,000 rpm
Added fuel Removed fuel At the envelope edge Operating point now
16%of the map learned
±4%largest step any cell can take
0°ignition changed by learning: it's locked

Amber outlines mark cells that reached the envelope edge. They stop there and are flagged for review rather than pushed further.

Tuning

Review it like a pro.
Every cell, every reason.

Autotune shows what it has learned and where to drive next. Review lists each change with the evidence behind it. Untick anything you don't want, then hold to apply.

Autotune
Learning
Learned68%
Avg error2.3%
Pending10
Fuel map · VE learningrpm →
RicherLeanerNot visitedNow
Next to learnHold 3,500–4,000 rpm at light boostA steady 20–30 % throttle in 4th fills the biggest gap.
Safety envelope
Max step±4 %Knock events0Lean limitλ 0.90IgnitionLocked
Review 10 changes

Autotune

Review changes
10 of 12
Safety checksPassed · ECU re-checks on apply
Every change stays inside your fuel envelope. Ignition and boost limits aren't touched.
+ 6 more small changes under 1 %
Save as draftUndo last apply

Review · try it: untick a row, then hold to apply

VE along the 150 kPa row · before → afterSimulated data
50607080901k2k3k4k5k6k7k
Before After review Where the driver felt it

A shape, not a promise: the curve shows how the fuel table changes, not a power figure.

Dash and displays

One stream.
Every screen in the car.

Phone, an iPad mini on a dash mount, a dedicated GAINS Dash and Studio on the desktop all read the same data. Watch them move together below.

One simulated stream, shared by every display
GAINSSimulated · ECU2
3Gear
4,490 rpmRPM × 1000Shift 7,200
Coolant92°C
Intake air42°C
Lambda0.84λ
Lambda target0.82λ
04080120160200240Speed119km/h
Boost167kPa
Oil pressure380kPa
Throttle95%

iPad mini · in-car mount · Design · Street, Track and Diagnostics pages, plus Tune and Keypad

GAINSECU2 · simulatedLearning
3GEAR
4,490 rpmShift at 7,200
Lambda · actual vs targetOn target
0.84 λtarget 0.82
Boost167 kPa
Coolant92 °C
Ignition23.9 °
Knock0.0 °

Phone · Prototype

119KM/H
4,490 RPM3
0.84λ · TARGET 0.82
BOOST167WATER92°IAT42°IGN23.9°BATT13.9V

GAINS Dash 5 · Concept

G-METER
119KM/H30.84λ · TARGET 0.82
RPM4,490BOOST167WATER92°IGN23.9°PDM27.9A
LAP · SIMULATED1:32.4−0.27

GAINS Dash 10 · Concept

GAINSStudioSimTransport3 pendingReview & commit
Fuel · VE tableLearned trims shown inside the ±4 % envelope
RPM4,490MAP167 kPaλ0.84 / 0.82CLT92 °CBATT13.9 VPDM27.9 AFAULTS0

Studio on the desktop · Preview · Open the public preview →

GAINS Dash 5 concept render: black glass face with shift lights
Dash 5 · concept render, not a product photo
GAINS Dash 10 concept render: wide bar display with shift lights
Dash 10 · concept render, not a product photo

The Dash is a concept: it would take its data over CAN, listen-only to other ECUs, and be set up from the app. No hardware exists yet.

Keypad and PDM

Switch the extras.
Never the essentials.

A digital keypad for the PDM2: launch, traction, fans, lights, wipers. Each output shows its live current. Critical loads are locked: try the fuel pump.

  • Allowlist only. You choose which accessory outputs the app may switch, per device.
  • Never from the app: fuel pump, ignition, engine-management power, starter, or anything that could cut power while moving.
  • The device stays in charge. Its own current limits and fault protection apply whatever the app asks. Every command is logged.
Keypad
PDM2
GAINS
Critical loads are never switchable from the app. Only allowlisted accessories are.
Live outputs27.9 A
Fuel pump (ECU)12.3 A
Ignition coils (ECU)6.2 A
Fan 19.4 A
Light bar0.0 A
Wipers0.0 A
Simulated data
GAINSSimulated · ECU2
GAINS
Boost target168kPa
PDM2 · live27.9 A
Battery13.9 V
Fans9.4 Light bar0.0 Wipers0.0 Horn0.0 Aux 12 V0.0 Fuel pump12.3 Ignition6.2

Critical loads stay locked. Only allowlisted accessories switch from the app.

The same keypad on the iPad: illuminated keys with live amps per channel. Latched, momentary (hold the horn) and locked keys. Simulated data

Fuel advisor
Read only
Your current ECUGAINS reads your logs and suggests changes. It never writes to this ECU. You apply them in the ECU maker's own software.
Log48 min
Cells seen142
Suggested23
CellNow → newChangeSamples
3,500 · −5 inHg62.0 → 64.1+3.4%212
4,000 · 0 psi71.5 → 73.6+2.9%188
4,500 · 5 psi80.2 → 82.0+2.2%96
2,500 · −12 inHg48.8 → 47.6−2.5%340
5,500 · 10 psi—Hold14
Copy table for your tuning software
Export CSV and report
Simulated data
Advisor mode

Already have an ECU?
Get advice, keep control.

On other ECUs, GAINS is read-only. It studies your logs and suggests table changes. You apply them in the ECU maker's own software.

  1. ReadLogs you export, or a listen-only data stream where the maker publishes one.
  2. SuggestA table of cell changes with sample counts. Thin data is held back.
  3. You applyCopy the table into your tuning software and apply it there yourself.

GAINS never writes to, flashes or reprograms a third-party ECU.

Status

Where it stands.
Honestly.

The app is an iOS prototype. It runs on simulated data and doesn't connect to a car yet.

In the prototype todaysimulated data

  • Ask screen: voice orb and conversation, with typed requests
  • Proposals with policy result and hold to approve
  • Changes that need a stop wait for the stop
  • Live gauges and λ against target
  • On-ECU learning heatmap inside its envelope
  • Autotune, review and before/after curves
  • Garage, Street and Dyno modes gated by ECU state
  • Device allowlist: critical loads never switchable

Plannednot built yet

  • Bluetooth and Wi-Fi connection to GAINS ECUs
  • Keypad and PDM2 control on real hardware
  • iPad mini dash layouts
  • GAINS Dash 5 and Dash 10
  • Advisor mode for other ECUs (read only)
  • On-device speech recognition
  • AI coach (output always treated as untrusted)
  • Data logging, session recording and sync
  • Setup and commissioning wizard
  • Android and Track mode
App: prototypeiPad: designDash: conceptStudio: previewNo performance or validation claims

Drive it. Describe it. Approve it.

Join the waitlist for the first GAINS ECUs and the app that comes with them.

All screens on this page show synthetic data from a built-in simulator. The app is an iOS prototype and is not available yet; the iPad layouts are designs, the GAINS Dash is a concept and Studio is a public preview.