Product reference without the duplicated walkthroughs
School is the first-run path. This page is for operations, integrations, and beta verification once someone already knows their role.
Start Here
The shortest path for new beta testers by role.
Owners, commissioners, and operators
Create the league, shape the season, manage staff, and run the operational side of race night.
Drivers, team members, and new joiners
Find leagues, register for seasons, track performance, and handle protests without getting lost in admin tooling.
Stewards, appeals reviewers, and rules officials
Review incidents consistently, understand blind review, and move cases from submission to ruling.
Broadcasters, commentators, and production staff
Stand up overlays quickly, understand tokenized URLs, and verify what your stream team actually needs on race day.
Race directors and operational staff
Own the schedule, results operations, and handoff between league setup and race execution.
Operational Reference
Use these views when you need to confirm how Racey behaves, not just learn the basics.
League creation, season setup, scheduling, roster approvals, announcements, and branding.
Admin workflowResults lifecycle, staff boundaries, and the handoff from league setup to event execution.
Race ops workflowProtests, blind review, rulings, appeals, and the decisions that need tight UX copy.
Steward workflowPermission matrix, plan comparison, workflows, and troubleshooting in one place.
Open cheat sheetIntegrations
The backend is rich; these are the pieces most likely to matter during beta.
API keys, public endpoints, and integration planning for bots or analytics.
API docsTokenized overlay URLs, browser-source setup, and real-time race graphics.
Broadcast setupStripe entry fees, trial gating, and which features are actually plan-limited.
Pricing and billingLeague directory, events, and the first-touch surfaces beta users will judge fastest.
Public directoryWhat to verify before you invite external users
These are the product-quality checks implied by the current codebase and its existing test surface.
A new user should understand where to start in less than 30 seconds.
The public promise needs to match the product surfaces people can actually use.
Beta testers should know where to go when they get stuck.
Keep testers out of dead ends
Reference pages need clear exits when the product, pricing, or integration path still feels ambiguous.
Use when the behavior feels wrong or unclear during beta.
Contact supportReference endpoints, keys, and integration patterns.
API documentationTrack what changed so beta feedback maps to the right build.
Changelog