Member experience
Everything the member touches — their plan, their training, their progress — sharing one record rather than four disconnected apps.
- Member Management
- Memberships
- Workouts
- Nutrition
- Progress
- Wearables
- Gamification
- Community
The fitness business operating system
One system for the entire fitness business
Members, check-in, classes, billing and reporting sharing one record — scoped per branch, audited by default, and still working at the front desk when the connection drops.
- Members
- Revenue
- Classes
- Trainers
- Check-In
- Analytics
Live command centre
The numbers agree, because they come from the same events
Growth, distribution, revenue and attendance are not four reports assembled from four systems. They are four views of one ledger, so a figure never disagrees with the screen next to it.
- Total members
- 2,480
- Active this month
- 1,912
- Revenue
- ₹18.4L
- Check-ins today
- 640
across every branch
77% of the base
recognised, not billed
live from the desk
Sample figures, shown to illustrate the layout.
The ecosystem
Fifty capabilities, five systems, one platform
Grouping is the point. A feature list communicates volume; a system communicates that the pieces know about each other.
Operations
The front desk and the floor. Check-in, bookings, classes and stock run on the same data the rest of the platform reports on.
- Check-In
- Booking
- Group Classes
- Trainer Management
- POS
- Inventory
- HR
- Documents
Growth
Demand generation wired to the same member record, so a lead becoming a member is a state change rather than a re-entry.
- CRM
- Sales
- Marketing Automation
- E-commerce
- Events
- Corporate Wellness
Business
Money and meaning. Every operational event lands in the ledger, and every report is derived from it rather than re-keyed.
- Billing
- Finance
- Reports
- Analytics
- AI
Platform
What makes it enterprise: tenancy, branches, APIs and the offline path that keeps the desk working when the line drops.
- Multi-Tenant
- Multi-Branch
- APIs
- White Label
- Security
- Observability
- Offline Mode
One event, eight modules
A member arrives and the whole chain moves without anyone re-keying anything.
- Member
- Check-In
- Trainer
- Workout
- Progress
- Membership
- Billing
- CRM
Who runs on it
The same core, configured four different ways
Not four products. One platform where different modules carry the weight depending on what you actually run.
Independent gyms
One site, one desk, one screen. Renewals surface as a worklist before they lapse.
- Members
- Check-In
- Trainers
- Billing
Fitness chains
Every record carries a branch. Central keeps the catalogue; each site runs itself.
- Branches
- Analytics
- Central catalogue
- Roll-up
Studios & trainers
The session is the unit of business, so the pack balance and the payout agree.
- Clients
- Sessions
- Workouts
- Payouts
Corporate wellness
Employers see participation. Individual attendance and health data stay private.
- Seats
- Challenges
- Engagement
- Reporting
Tenancy & trust
Tenants share a platform, never each other’s data
We describe mechanisms rather than badges. There is no uptime SLA on this page and no certification we have not been audited for — your security team can assess the architecture instead.
Per-tenant isolation
Row-level scoping, schema-per-tenant or database-per-tenant, chosen per deployment.
Scope from the token
Organisation and branch come from a verified auth context on the server, never from the request body.
Append-only audit
The audit trail is hash-chained, so a tampered row breaks the chain.
Erasure without rewriting history
Deletion crypto-shreds the key material rather than mutating audit records.
Encryption
In transit and at rest, with keys held outside the application database.
RBAC per branch
Roles are granted per branch and per product, and denied by default.
Ready to run your gym smarter?
Start on the free tier and add modules per branch as you need them, or walk through it with us first.
No card required to start. Pricing is per module, per branch, per month.