Network topology for digital signage defines how media players connect to the CMS and to each other (if at all). SpinetiX uses a centralized hub-and-spoke model: the CMS distributes content to all players via HTTP/HTTPS. No peer-to-peer, no mesh, no distributed sync complexity. This design is intentionally simple — because simplicity means fewer failure points, easier firewalling, and predictable behavior at any scale.
When Topology Decisions Matter
- New deployments — defining the CMS-to-player communication path before pulling cables
- Multi-site expansion — adding locations requires defining how remote sites connect to the CMS
- Security reviews — your firewall team needs to understand the traffic flow and trust boundaries
- Video wall installations — synchronized multi-player displays have additional topology requirements
Supported Topologies
1. Single-Site Star (Hub-and-Spoke)
The most common topology. One CMS server (Elementi or Arya Cloud) connects to all players on the local network. Players pull content via HTTP/HTTPS. Administration happens from the CMS workstation or browser. Ideal for: single building, campus, or retail location with all screens on one LAN.
2. Multi-Site via Cloud (Arya)
Each site's players connect outbound to Arya Cloud on port 443. No VPN tunnels needed. Content is managed centrally in the cloud; each site downloads its assigned content independently. Ideal for: multi-city or multi-country deployments where VPN infrastructure is impractical or unavailable.
3. Multi-Site via VPN (Elementi)
Remote sites connect to the central Elementi server via corporate VPN or MPLS. Players at each site download content through the VPN tunnel. Requires sufficient WAN bandwidth for content distribution across sites. Ideal for: organizations with existing VPN infrastructure that need on-premises data residency.
4. Distributed (Multi-Elementi)
Each site runs its own Elementi instance with local content management. Central coordination via shared templates and data sources. Ideal for: organizations with autonomous regional offices, each with their own content teams and IT infrastructure.
5. Air-Gapped (Isolated)
Completely disconnected from the internet. Elementi server and players on a physically isolated network. Content loaded via secure media transfer or one-way data diode. Ideal for: defense, classified environments, critical infrastructure, and organizations with the strictest security requirements.
6. Video Wall (Synchronized)
Multiple SpinetiX players render portions of a single large canvas. Players synchronize via a local network protocol (frame-perfect sync on the same subnet). Each player connects to the CMS independently for content updates. Ideal for: large-format displays, lobby walls, command center dashboards, stadium boards.
Key Parameters
| Topology | CMS Location | Internet Required | Best For |
|---|---|---|---|
| Single-site star | On-premises | Optional | Single building / campus |
| Multi-site cloud | Arya Cloud | Yes (port 443) | Multi-city, no VPN |
| Multi-site VPN | Central on-premises | No | Existing VPN infrastructure |
| Distributed | Per-site on-premises | No | Autonomous regional offices |
| Air-gapped | Isolated on-premises | No | Defense, classified, critical infra |
| Video wall | Any of the above | Varies | Large-format multi-player sync |
Common Mistakes in Topology Design
- Using peer-to-peer for content distribution. P2P creates security blind spots (player-to-player traffic is hard to firewall) and sync conflicts. Centralized distribution is simpler, more secure, and scales better.
- Not accounting for WAN bandwidth. Multi-site VPN topology means all content flows through the WAN link. Calculate: content size × number of remote players × sync frequency. If bandwidth is limited, consider Arya Cloud (each site downloads independently) or distributed Elementi.
- Forgetting about video wall sync requirements. Video wall players must be on the same subnet for frame-perfect sync. Putting them on different VLANs or across routers adds latency that breaks synchronization.
- Over-complicating the topology. Start with the simplest topology that works. Single-site star covers 80% of deployments. Only add complexity (VPN, distributed, hybrid) when single-site isn't sufficient. Reference architecture guide →