Discord integration
Squads and Discord, in step automatically
Create a squad in Paddock and its Discord channels follow — members, names and access stay in sync while the roster changes.
Channels that manage themselves
Put a squad together for an event and its category and channels appear in your server, named after the squad. Rosters change, squads dissolve, events pass — the channels follow, without anyone gardening them.
Your roles stay yours.
Paddock works with the roles your server already has — it never invents its own. Link a member once and their access follows the roster, from applicant to race driver.
Results where the team hangs out
Race results, event signups and reminders post straight into the right channels. The team reads them where the conversation already is, not in yet another tab.
Why Discord-native
Run your iRacing team from the server it already lives in
Almost every iRacing team already runs on Discord — it is where signups happen, where strategy gets argued, where results land after the race. The problem is that Discord has no idea who is on your roster. So teams keep a second copy of the truth in a spreadsheet, and spend race week reconciling the two: adding channels for a new squad, handing out roles, chasing down who is actually driving.
Paddock closes that gap. Your roster is the source of truth, and your Discord follows it. Put a squad together for an event and its channels appear, named after the squad, with the right people in them. The event passes and the channels clean themselves up. A driver is accepted, and their access moves with them — all using the roles you already set up, never a parallel set Paddock imposes.
The result is one roster instead of two, and a server that stays tidy without anyone tending it. Race results, event reminders and signups post into the channels your team already reads, so the tool disappears into the place the team already talks — which is exactly where iRacing team management should happen.
Frequently asked questions
- Does Paddock create channels in my Discord server?
- Yes — when you build a squad for an event, Paddock creates its category and channels in your server, named after the squad, and cleans them up when the event is over. You connect the server once and stop gardening channels by hand at midnight.
- Will Paddock mess with my existing Discord roles?
- No. Paddock works with the roles your server already has and never invents its own. You link a member once, and their Discord access follows their place on the roster — from applicant to full race driver — using your roles, not ours.
- Where do race results and signups show up?
- In the channels your team already reads. Race results, event signups and reminders post straight into Discord, so the team sees them where the conversation is happening instead of in another tab nobody has open.
- Do drivers need a Paddock login to take part?
- Drivers link their iRacing and Discord identities to Paddock once. After that most of the day-to-day — signups, reminders, results — reaches them in Discord, so running the team does not mean dragging everyone into a new app.
Stop running two rosters
Connect your server once and let the paddock and the Discord agree with each other from then on.