Security & reliability

Digital signage that behaves like part of your infrastructure, not a toy.

HexitHive is built for teams who already care about networks, uptime, SLAs and security. Multi-tenant isolation, HTTPS APIs and offline-ready players are built in from day one.

Platform security model

HexitHive is a central control plane with strict tenancy boundaries and role-based access, exposed over standard HTTPS.

Tenant isolation

All configuration – tenants, screens, playlists, media and users – is scoped to a tenant. Operators and admins only see data for the tenants they have access to, keeping customer environments separated inside a single platform.

Role-based access control

The Portal separates responsibilities between global operators, tenant admins, content editors and viewers. That keeps sensitive actions like pairing devices and changing playlists away from casual users.

HTTPS-only API

Players talk to the Portal over HTTPS using a small, documented JSON API. There are no exotic protocols or random inbound ports to open on your firewalls – just outbound HTTPS calls from the player to the Portal.

Device security & network posture

HexitHive Players are designed to live on real networks – branches, stores, offices – without becoming a mystery box.

Outbound-initiated communication

Players only initiate outbound connections to the Portal. There are no inbound connections from the internet to the device, which makes them easier to place behind firewalls and NAT.

Device identity & keys

Each Player has a unique identity and device key issued during pairing. The key ties the device to a specific screen and tenant so you can revoke or rotate access on a per-device basis if a unit is lost, replaced or repurposed.

Minimal exposed services

The player stack is trimmed down to what it actually needs to operate signage. Services not required for display, sync or monitoring are not exposed. Where local APIs exist, they are intended to be reachable only from the device itself.

Content & data handling

Most deployments use HexitHive to distribute static media (images and MP4s). The platform is built around that assumption.

Media-only by default

HexitHive focuses on traditional signage payloads – images and videos – not arbitrary executable content. That simplifies both your threat model and your compliance story.

Per-tenant media separation

Media assets are logically grouped by tenant in the Portal. Players only download the media referenced in their assigned playlist, so one tenant’s content is not sprayed across unrelated devices.

Local caching with controlled lifetime

Players cache media locally so they can keep playing if the network disappears. When content is removed from a playlist and stays unused, it can be cleaned up to reclaim disk space and keep the cache predictable.

Reliability & failure behaviour

HexitHive is built on the assumption that networks are noisy and hardware occasionally misbehaves. The question is not “does it break?” but “how does it fail?”.

Offline playback by design

Because players keep a full copy of their playlist and media locally, a WAN outage does not blank the screen. The device keeps looping the last valid playlist while it waits for connectivity to return.

Heartbeats & monitoring hooks

Regular heartbeats make it clear which players are healthy, which are struggling to sync, and which have gone silent. This information can be surfaced in the Portal UI and fed into external monitoring if required.

Predictable updates

When you publish new content or change a playlist, players update deterministically on their next sync. There’s no race condition between multiple sources of truth – the Portal is the one place you change reality.

Operations, change & governance

HexitHive is meant to sit next to your monitoring, logging and ITSM tooling, not replace it. The goal is to slot into the way you already run infrastructure.

Change control friendly

Because all configuration lives in the Portal, you can treat signage changes like any other infrastructure change: raise a change, prepare the playlist, review, approve, and then publish as a single, auditable action.

Incident communication support

During outages or high-severity incidents you can temporarily switch affected screens to special “incident mode” playlists, giving on-site staff and NOC teams a single version of the truth in real time.

Designed for MSP & enterprise teams

The multi-tenant model, role-based access and API design are all geared towards service providers and in-house ops teams that already have strong practices around security and uptime.