VaqueroPerformance & Tuning

IRON000
Vaquero Performance & Tuning Race engineering for iRacing

Engineering not opinion

Software that runs while you race, and engineers who read what it records. Built for iRacing, for drivers who are done guessing at setup.

Scroll
01 — Structure Two halves, one loop

Neither half works without the other.

Builds the technology

Racecraft
Lab

Research, software engineering, and machine learning. The models that read an iRacing session the way a race engineer reads one.

Visit Racecraft Lab ↗
Delivers the engineering

Vaquero
Performance

The app you run, the reports you read, and the engineers who work your car, your track, and your championship with you.

See the product →

iRacing gives you the car, the track, and the competition. It does not give you a race engineer.

Real teams put an engineer on every car. In sim racing you are the driver, the crew chief, and the setup shop, usually after work. This is the engineer you were never going to be able to hire — running in the background while you drive, and reporting when you get out.

02 — Services Available now

What we do, plain and simple.

S 01

Session analysis

Every lap you run is parsed corner by corner against your own best reference and against what the car is capable of. You get a ranked list, not a graph to interpret.

S 02

Setup development

Springs, bars, dampers, ride height, wing, diff, gears, tire pressures — specific changes with direction, magnitude, and the order to test them in.

S 03

Driver coaching

Coaching from your own telemetry. Two or three priorities per session, ranked by what each is worth, instead of a list of everything you did wrong.

S 04

Race strategy

Fuel, tires, stint length, and traffic. What to do on the box when the race stops going to plan.

S 05

Endurance & team engineering

Multi-driver stints, driver swaps, and a shared setup direction so four people are not developing four different cars.

S 06

Season planning

Which weeks to attack, which to bank, and what to work on between them. Where your points are actually going.

S 07

Practice programming

What to run and for how long. Most practice is repetition of problems you already solved.

S 08

Incident review

What preceded the contact, in the data, without the protest thread.

A prototype race car under a single work light on a wet workshop floor
The car is only ever as good as what you know about it
04 — Compounding Why week eight beats week one

The engineer gets better at your car the longer you run it.

Week one you
get a report.

Week ten it
knows your car.

Your session history is what makes trend analysis possible — separating a genuinely quicker car from a good night, and showing whether last week's change actually did anything.

The car and track baselines improve the same way. The more laps the platform has seen on a combination, the sharper its recommendations for it — which is why the tenth week is worth more than the first.

Sessions are stored and analysed on our servers, and help improve the models behind the platform. Full terms are set out before you connect an account.

05 — Roadmap Shipped, building, and further out

What runs today, and what is being built.

Running now

After the
session

  • Automatic telemetry capture
  • Corner-by-corner analysis
  • Lap and reference comparison
  • Ranked findings with projected gain
  • Setup file management
  • Setup change recommendations
  • Driver coaching notes
  • Session history and trends
  • Driver profile
  • Team and league dashboards
In development

During the
session

  • Live strategy screen
  • Fuel and stint modelling
  • Tire state estimation
  • In-race pace targets
  • Traffic and pit-window calls
  • Predicted lap simulation
  • Setup assistant
  • Driver-swap handover notes
Further out

In your
ear

  • Real-time coaching
  • Voice engineering assistant
  • Automated crew chief
  • Dynamic setup generation
  • Video synchronisation
  • Weather and track-state modelling

Run one session.

Then read what an engineer would have told you about it.

Install the app, drive the way you normally drive, and get out of the car. The report is waiting. If there is nothing worth finding in your driving, we will tell you that too.

Start a conversation
Session report Practice · 31 laps
T1 Braking 12 m early, then coastingDriver · consistent across 24 laps +0s
T6 Mid-corner understeer on entryBalance · front ARB, one softer +0s
T9 Throttle applied before the apexDriver · costing exit speed onto the straight +0s
ALL Rear tires falling away after lap 9Setup · pressures 2 kPa high for this run length +0s
Projected, this session +0s

Illustrative. Your findings depend on your car, track, and driving.