Each tenant has its own screens, playlists, users and limits. Operators only see the tenants they’re allowed to manage, keeping environments clean and auditable.
HexitHive Portal: multi-tenant control plane for digital signage.
The HexitHive Portal is where you manage tenants, screens, playlists and health. It is built for MSPs and IT teams who need a single pane of glass for many customers and locations. For concrete deployments across MSP fleets, branches and NOC walls, see the Use Cases page.
How the HexitHive Portal models your environment
The portal is designed to look the way your real-world footprint looks: tenants, customers, locations and physical screens, all mapped to the digital signage playlists they should be running. For concrete examples across MSP, enterprise and retail environments, see the Use Cases page.
Tenants, customers and screens
HexitHive is multi-tenant from day one. That matters if you’re an MSP or internal central team looking after many business units. For more on tenant isolation, roles and operational practices, see the Security & Reliability page.
- Tenants define the top-level boundary for data, branding, limits and billing.
- Companies / locations group screens by customer, site or cost centre.
- Screens represent the individual Raspberry Pi players installed at each physical display.
- Users & roles (admin, operator, viewer) ensure people only see and change what they are responsible for.
From playlists to published configs
The portal separates editing from deployment. You can adjust playlists and media without immediately changing what the player shows:
- Upload and organise media per tenant.
- Build playlists with durations and rules.
- Assign playlists to screens or screen groups.
- Generate published configs that the players fetch via
/api/player/config.php.
Screens are first-class: last heartbeat, last config push and alert-friendly states such as “online”, “offline” and “stale” mean you can integrate digital signage into your existing monitoring and NOC practices.
Playlist edits can be staged and then pushed. That generates new published configs that players consume, giving you a clean boundary between “draft” and “live on screen”.