01
Event planning & entries
We build the season calendar around your series and your drivers' availability, file the entries, pick timeslots per car, and send signup deadlines and reminders before anyone has to ask.
All packages
Your team.
Run like a works program.
We take on whatever parts of running your iRacing team you want off your plate, and nothing you'd rather do yourselves: event planning, entries, setups, strategy, data and race-day management, the way Eclipse Competition runs its own entries. You keep your name, your drivers, your sponsors and your identity.
20+
Endurance race wins
1st
Majors 24h Le Mans · Petit Le Mans · Daytona 24
48h
Service agreement after you pick a package
from $175
Per month · 6-month minimum
01 / What we do
Everything a
works team runs.
Six disciplines · Three packages
02
Setups
Baseline setups per car class from a library built by people working in real-world IndyCar-ladder and sports car engineering, not just sim. Licensed to you for the term; anything you build yourselves stays 100% yours.
All packages · one car class in Paddock · library widens from month 3
03
Strategy & stint planning
We plan fuel, stint lengths, driver order and pit windows in Totality, our own strategy tool, from each driver's real pace and availability, then run the plan live on race day.
Full Operations · Championship
04
Race-day management
A pit wall on the radio: live timing, pit calls, driver swaps, weather and incident handling. Your drivers drive. We run the race.
Special events in Full Operations · every series in Championship
05
Telemetry & debriefs
Lap and sector analysis across your roster through Garage 61, written up as a debrief: the numbers first, then the two or three changes they point to for the next event.
Monthly debrief in Paddock · telemetry review from Full Operations
06
Team systems
The calendar, Discord structure and data sharing we set up in your server in the first two weeks, plus a website template in your colours from Full Operations. The admin work runs itself.
All packages · website template from Full Operations
02 / In practice
What it looks
like on a race week.
Sample work product · 6-hour special event
Weekend run sheet
Event plan · delivered Tue| Session | Time | Owner | Status |
|---|---|---|---|
| PracticeSetup sign-off · 2 drivers | Wed 23:00 UTC7:00 PM ET | Engineer | Done |
| AvailabilitySurvey closes · stints drafted | Thu 02:00 UTC10:00 PM ET | Ops | Done |
| Roster lockPosted to Discord | Fri 00:00 UTC8:00 PM ET | Ops | Today |
| QualifyingDriver A · low fuel | Sat 13:45 UTC9:45 AM ET | Driver A | Pending |
| Race · 6hPit wall live from T-30 | Sat 14:00 UTC10:00 AM ET | Pit wall | Pending |
| DebriefWritten + 20-min call | Sun 18:00 UTC2:00 PM ET | Engineer | Pending |
Every event gets one. Times in UTC and your drivers' local zone, one owner per line, nothing left to "someone will do it."
Stint plan
Totality · 6h · 3 drivers- FUEL52 laps per stint at 2.61 L/lap · 2.4 L margin · 6 stops
- SPLITA 151 laps · B 104 · C 104 — fair share cleared, B/C double-stint by request
- RISKDriver C unavailable after 5H · final stint locked to A
Built from your drivers' real numbers. Availability, best lap and fuel per lap come from a two-minute survey; the plan updates live on race day.
Post-race debrief
Garage 61 · lap delta- PACEB has the raw lap (−0.4s) but loses 11s per stint to traffic management — a coaching item.
- TYRESA's fade from L40 is a pressure call; +0.5 psi fronts for the next long run.
- NEXTPut B in clean air for quali; A takes the opening double stint.
Numbers, then a decision. Every debrief ends in two or three changes for the next event.
Systems, running on their own
Portal · Discord · Calendar- Event posted to the portal · signups openAuto · Mon
- Discord embed live · updates as drivers sign upAuto
- Roster pinged with the signup deadlineAuto · T-2 days
- Availability survey sent to the locked rosterAuto · on lock
- FINAL ROSTER posted · stints on everyone's calendarAuto · on lock
- Race role assigned · auto-removed 2 days afterAuto · race day
- Debrief + G61 laps synced to the event pageAuto · +2h
Nobody chases anybody. This is the same stack Eclipse Competition runs every week, set up in your server in the first two weeks.
03 / Packages
Three tiers.
One onboarding.
USD · 6-month minimum · month to month after
Tier 01New teams · one car
Paddock
$175/ month
For a new team that wants the admin and the baseline done right from the start.
- Season calendar
- Entries
- Baseline setups for one car class
- Monthly debrief
Tier 02 · Most teamsEstablished teams · 1–2 cars
Full Operations
$300/ month
The whole operating system: plans, setups, strategy and a pit wall for the races that matter.
- Everything in Paddock
- Strategy for every event
- Special-event race-day coverage
- Telemetry review
- Website template
Tier 03Multi-car · league championships
Championship
$500+ / month · quoted
For multi-car or league-championship programs that need a named engineer on call.
- Everything in Full Operations
- Every series
- Dedicated engineer contact
- Driver coaching hours
Onboarding: $250, one time. Covers a team audit, setup-library access, systems build-out and your first event plan. Due before work starts.
Not included: iRacing subscriptions, content and event entry fees. Marketing or in-kind services from your side are welcome as add-ons; they don't replace or reduce the fee.
Something bigger? Launching a team from scratch, or running a driver-scouting program for a real-world team, is scoped and quoted separately. Tell us what you're building.
04 / How it starts
Signed to first
event in a month.
Typical timeline
Week 0
Intro call
Your goals, roster, cars and series, and which package fits. Thirty minutes.
Week 0
Sign & pay
You sign the service agreement and pay the onboarding fee and first month.
Week 1
Team audit
We review your drivers, results and current setup and write the plan.
Weeks 1–2
Systems live
We set up the calendar, Discord structure and data sharing in your server.
Weeks 2–4
First event
We run your first event plan end to end, then debrief it with you.
Month 3
Library widens
Your setup access widens beyond your baseline car classes.
05 / Key terms
No surprises
in the contract.
The full service agreement follows once you choose a package
You own your team. We own our methods. Neither side acquires a stake in the other. The service agreement is the long version of the seven points here.
Independence
You own your team, brand, drivers, accounts and sponsors. We own our methods, tools and setup library. Neither side acquires any stake in the other.
Setups are licensed, not transferred
You can use our setups for your entries during the term. Setups you build yourselves are always 100% yours. Ours can't be resold, shared, or kept after the agreement ends.
Payment
Due on the 1st of each month. Access is paused if a payment is more than 15 days late.
Term
Six-month minimum, then month to month with 30 days' notice. Leaving early means the rest of the minimum term is owed.
Non-solicit
Neither side recruits the other's rostered drivers or staff during the term and for six months after. Drivers who approach a team on their own are free to move.
Your data stays yours
Your telemetry stays yours and is never shared with other clients or with Eclipse's own team.
Add-ons & governing law
Marketing or in-kind services from your side are welcome as add-ons. They don't replace or reduce the fee. Governing law: Texas.
Pick your
tier.
We run the rest.
Reply with the package that fits, or book a 30-minute intro call. We send the service agreement within 48 hours, and your first event plan is delivered within two weeks of signing.
- EMAIL · [email protected]
- DISCORD · message an admin on the Eclipse server