Club identity
Logo, accent color, favicon, login imagery, and the email header. Member-facing pages lead with the academy.
White label
Each academy is a separate tenant. The interface is tokenized so the club can apply its identity without breaking the operating system.
Logo, accent color, favicon, login imagery, and the email header. Member-facing pages lead with the academy.
Location names, support details, domain, sender identity, weapons, and the words the front desk uses.
Spacing, type scale, accessibility, states, layout, and how a module behaves. Those stay BladeOS.
Provisioning
Opening a club creates the module structure and a blank database. Rosters, class history, Stripe customers, leads, and video libraries are never copied from another academy.
“Powered by BladeOS.ai” stays discreet on the member login, the club footer, and system email. Staff operations can keep the BladeOS navigation so training is the same in every club.
In the demo you can set
Reset returns the tenant to zero records.
What does not move between clubs
| Record | New club |
|---|---|
| Members and households | Empty |
| Membership plans and prices | Empty |
| Classes, bookings, private lessons | Empty |
| Coaches and staff profiles | Empty |
| Invoices, expenses, transfers | Empty |
| Leads, campaigns, WhatsApp templates | Empty |
| Check-ins and video library | Empty |
| Shop catalog and discount codes | Empty |