Creating an Account
Dev-only today
Race Platform is not yet open for public sign-up. There is no self-service registration flow shipped in v0.1.0. Accounts are provisioned manually for pilot teams via the seed script.
How accounts work
Race Platform is multi-tenant. Every API request is scoped to an
accountId that is derived from the authenticated user's JWT. Two
users from different accounts can never read each other's data.
An account has:
- A unique slug (e.g.
demo-racing) used in the login flow - One or more users with roles (
owner,engineer,viewer) - All of the account's championships, events, sessions, cars, drivers, definitions, custom views, plugins, etc.
Logging in to the local dev stack
After running make seed in a freshly-installed local stack, a
demo account is pre-populated:
| Field | Value |
|---|---|
demo@race.local | |
| Password | demo |
| Account slug | demo-racing |
Open http://localhost:6166 (the Flutter web build) and use those
credentials. You'll land on the dashboard for the seeded IMSA
Sebring sample event.
Provisioning a real account (today)
For pilot teams during the alpha phase:
- The team lead sends a request through the contact channel provided in the pilot agreement.
- We run
tools/provision-account.ts(admin-only, currently one-off) to create the account row, the owner user, and a bcrypt-hashed password. - Credentials are delivered out-of-band.
- The owner can then invite engineers via a (forthcoming) admin surface.
What's coming
- Web sign-up flow with email verification
- Account management website (similar to HH-DM's
hh-dev.comportal) for billing, user invites, and downloads - SSO (Google / Microsoft) for engineering staff
- Self-service password reset
See Whats New for the current roadmap.