Platform overview
High-level overview of what HexitHive is, who it’s for and how the Portal and Player fit together.
Use this page as a launchpad: from here you can jump to the Portal and Player product pages, deep-dive architecture, security, use cases and FAQs. As we add formal docs and API references, they’ll live here too.
If you’re evaluating HexitHive or planning a pilot, start with these.
High-level overview of what HexitHive is, who it’s for and how the Portal and Player fit together.
The HexitHive Portal product page covers tenants, screens, playlists and monitoring for multi-tenant environments.
The Player product page focuses on Raspberry Pi devices, local caching, offline behaviour and heartbeats back to the Portal.
These pages are written for architects, network teams and operations.
Control plane / data plane model, multi-tenant structure, player lifecycle, APIs and offline behaviour.
Tenant isolation, device identity, HTTPS-only APIs and predictable failure modes when networks misbehave.
How MSPs, enterprises and retailers can use HexitHive to run digital signage fleets and “internal TV” channels.
When you’re ready to roll this out or need answers for a security / risk team, these are your next stops.
Short answers to the most common questions about how HexitHive is run, supported and licensed.
Need to discuss architecture, security requirements or a specific pilot scenario? Use the contact form and we’ll continue the conversation.
Formal REST/API and player configuration documentation will be published here as the platform evolves. If you need something specific now, reach out.