Partner Types
Performance Hub partners connect the systems, devices, data pipelines, and delivery teams that help operators run physical locations more consistently.
Most technical integrations start with Partner Console access in a Performance Hub sandbox account. From there, partners generate test keys, configure facility linking, work through the Partner API, validate their workflows, and then move through to production with the Performance Hub team.
Member management systems
Member management and club management platforms usually keep the source of truth for people, plans, bookings, attendance, and access permissions. These integrations help Performance Hub understand who belongs to each facility, what they are entitled to access, and how those facilities are performing.
These partners often integrate with Performance Hub Door/Gate Controller workflows too. Performance Hub makes the door control hardware; the partner platform usually decides whether a person is allowed to enter, then calls the Partner API to trigger the Performance Hub controller.
Typical use cases:
- Sync members, leads, prospects, blocked users, and expired members.
- Sync membership plans, access zones, access hours, and pricing.
- Push check-ins and attendance events for reporting and model accuracy.
- Submit facility report snapshots for operational and financial visibility.
- Trigger Performance Hub Door/Gate Controllers after the partner system authorises access.
Recommended starting points:
Access and entry workflow partners
Access and entry workflow partners connect systems that influence whether someone should be admitted to a facility. This might include booking platforms, class attendance systems, visitor workflows, security providers, or member management systems with their own access rules.
Performance Hub does not expect partners to manufacture or supply the Door/Gate Controller hardware. Performance Hub provides and manages that hardware. Partner systems decide whether access should be granted, then call the Partner API to unlock a Performance Hub controller where the integration is enabled.
Typical use cases:
- List available Door/Gate Controllers for a facility.
- Check controller status before presenting an unlock option.
- Trigger a door or gate unlock after your system authorises access.
- Correlate unlocks with member and check-in IDs for audit trails.
- Connect bookings, appointments, classes, or visitor records to facility entry workflows.
Recommended starting points:
- Partner Console
- Access Control
- List Door/Gate Controllers
- Get Door/Gate Controller status
- Unlock a Door/Gate Controller
BI, reporting, and analytics tools
Reporting and analytics partners help operators read and combine Performance Hub data with financial, membership, occupancy, operational, and external business datasets.
Today, most of this integration work is about reading organisations and facilities, aligning identifiers, and working with reporting data. As Performance Hub expands the Partner API, computer vision and facility intelligence data will become an important part of this partnership type.
Typical use cases:
- Read connected organisations and facilities.
- Read or exchange report snapshots for period-based reporting.
- Align facility identifiers across reporting tools and Performance Hub.
- Support dashboards for multi-site operators and leadership teams.
- Prepare for future access to computer vision, occupancy, and facility intelligence datasets.
Recommended starting points:
Agencies and system integrators
Agencies and system integrators help deploy Performance Hub in the field. Their work is often more operational than API-only: installing and configuring IoT hardware, screens, devices, cameras, edge processors, access devices, and the supporting systems needed to bring a facility online.
Typical use cases:
- Deploy Performance Hub hardware across new or existing facilities.
- Install and configure cameras, screens, IoT devices, and edge hardware.
- Coordinate network, power, mounting, and commissioning requirements.
- Help connect facility systems, partner platforms, and operational workflows.
- Support testing, handover, and go-live readiness with Performance Hub.
Recommended starting points:
Resellers and white-label distributors
Resellers and white-label distributors help bring Performance Hub into new markets, networks, and operating groups.
Typical use cases:
- Coordinate onboarding between Performance Hub, customers, and implementation partners.
- Package Performance Hub with local services, hardware, or operational support.
- Support customer rollout across multiple facilities or regions.
- Help customers discover compatible integrations in Performance Hub.
Recommended starting points:
How partners appear inside Performance Hub
Performance Hub does not currently publish a public partner directory on the docs site. Approved partner integrations appear inside the Performance Hub partner directory in the core Performance Hub platform.
After sandbox testing, go-live checks, and production setup are complete, your configured integration will appear in the Performance Hub partner directory inside the core Performance Hub platform. This keeps the visible directory aligned with integrations that are actually configured and supported in the platform.