How a digital signage network is built: CMS, players, content delivery and monitoring
Quick answer: DigitalSignage.com's architecture has four layers: SignStudio, the CMS, hosted in the cloud or on your own mediaSERVER (a one-time $895); DigitalSignage.com SignPlayer on each screen, which downloads every asset into a local cache and plays from it; content delivery over outbound HTTPS on port 443 only, with a real-time socket that falls back to HTTP polling behind strict firewalls; and monitoring from the Screens dashboard with status, snapshots, restart and reboot. No inbound ports, no static IP, and the same design from 1 screen to 1,000. The first 3 screens are free forever, then $3 per screen per month.
Last updated October 22, 2026. Sources: our network requirements, network and bandwidth planning, remote monitoring, failover and redundancy and security best practices pages, the cloud vs on-premise guide, the SignPlayer system requirements page and the what-happens-offline guide.
The four layers
| Layer | What it does | Where it runs | DigitalSignage.com component |
|---|---|---|---|
| Content management | Stores media, builds scenes and campaigns, schedules, holds the screen list | Vendor cloud, or a server on your network | SignStudio, in a browser; mediaSERVER for on-premise |
| Players | Download assigned content, cache it, play it on schedule, report status | Behind every screen | SignPlayer on Windows, Mac, Android and Android TV, Chrome OS, Raspberry Pi, iPad, or the web player in a browser |
| Content delivery | Moves assets and commands between the two over the network | Internet, or your LAN | Outbound HTTPS on port 443 to *.signage.me; LAN only with mediaSERVER |
| Monitoring | Shows which screens are online, what they are playing, and lets you act | In the CMS | The Screens dashboard: status, last check-in, snapshot, Restart Player, Reboot Device, scheduled restarts |
A video wall, a menu board and a 1,000-screen retail network differ in count, not in shape.
Cloud CMS or on-premise server
| Cloud SignStudio | mediaSERVER on-premise | |
|---|---|---|
| Where the CMS lives | DigitalSignage.com's cloud | A server you run inside your firewall |
| Price | First 3 screens free forever, then $3 per screen per month; Enterprise per screen in the public calculator | One-time $895 for the server, plus per-player licenses sold separately |
| Updates, backups, security of the server | The vendor's job | Your IT team's job |
| Internet at the site | Needed for publishing, status and new content; playback itself comes from the cache | Not needed; players talk to the server over the LAN |
| Air-gapped sites | Players can be updated by USB with the Sneaker Net updater | Fully isolated operation |
| Who it suits | Most networks | Policy that keeps content on the network, sites with no reliable internet, very large fleets |
The decision framework is in cloud vs on-premise; the short version is cloud unless policy or connectivity says otherwise.
How content moves from the editor to the screen
- An editor builds a scene in SignStudio and publishes a campaign to one or more screens.
- Each player holds a real-time socket connection to SignStudio and is told there is new content. Behind a firewall that blocks the socket, the player falls back to HTTP polling, so no static IP and no port forwarding are needed.
- The player downloads every asset assigned to the screen over HTTPS on port 443 into its own application data folder. On the Raspberry Pi the cached files are integrity-checked.
- The player plays from that local cache on the schedule, using its own clock, so dayparts change on time even if the connection is down. Keep the clock synced over NTP on port 123.
- The player reports its status to SignStudio: online or offline, last check-in, player version, what is playing.
- If the internet drops, the screen keeps playing cached content; only live items fetched as they play, such as web pages, RSS, weather and streams, pause.
- When the connection returns, the player reconnects on its own, syncs any changes published meanwhile and reports in again.
Ports, firewall and proxies
| Port | Protocol | Purpose | Required |
|---|---|---|---|
| 443 | TCP outbound | HTTPS to *.signage.me: SignStudio, registration, content, status | Yes |
| 53 | UDP and TCP outbound | DNS | Yes |
| 123 | UDP outbound | NTP time sync, which schedules depend on | Recommended |
| 80 | TCP outbound | HTTP redirect to HTTPS | Recommended |
| Any inbound | None |
HTTP, HTTPS, transparent and authenticated proxies are supported; SOCKS5 on Windows only. If the firewall needs exact hostnames rather than a wildcard, ask support for the current list for your account.
Bandwidth per screen and per site
| Content on the screen | Peak per player | Downloaded per day |
|---|---|---|
| Images only | 5 Mbps | 50 to 200 MB |
| Images and video mixed | 10 to 20 Mbps | 200 to 500 MB |
| 1080p video-heavy | 25 to 50 Mbps | 500 MB to 2 GB |
| 4K video | 50 to 100 Mbps | 1 to 5 GB |
| Live streaming | 5 to 25 Mbps continuous | Depends on hours |
Peak is during a content sync, not during playback. For planning a site, our bandwidth guide uses about 5 Mbps average per display with 50 percent headroom and recommends 50 Mbps for 1 to 10 displays, 100 Mbps for 11 to 50, 250 Mbps for 51 to 200 and 500 Mbps for 201 to 500. Schedule large updates off-peak and let the caches do the rest.
Network design at a site
- A dedicated VLAN for signage, with outbound-only rules to the ports above. It isolates player traffic from business systems, simplifies troubleshooting and allows QoS.
- Wired Ethernet for any screen you cannot easily reach. Wi-Fi drops are the most common cause of a screen that went blank overnight; where Wi-Fi is unavoidable use Wi-Fi 5 or 6 at -65 dBm or better.
- Power over Ethernet for Raspberry Pi players: one cable for power and data, and remote power cycling from the switch.
- DNS that resolves external names correctly from the VLAN, with no split-horizon surprises for
*.signage.me. - No SSL inspection on the signage VLAN, or an exception for the service, since certificate errors are a common cause of a player that cannot connect.
Monitoring and proof of play
The Screens dashboard in SignStudio shows every player online or offline with its last check-in, lets you take a snapshot of what is on screen, send Restart Player or Reboot Device where the platform's watchdog supports it, and schedule a nightly restart for all players; alerts cover offline players and low storage. Good practice from our monitoring guide: review uptime weekly per site, route alerts to whoever is on site as well as IT, and target 99.5 percent uptime for customer-facing screens.
Proof of play is a different record: a log of exactly which content ran on which screen and when, used by advertisers and compliance teams. On DigitalSignage.com it is an Enterprise feature; ask support for the current reporting options on your plan.
Failover
| Failure | What keeps the screen playing | What to add for critical screens |
|---|---|---|
| Internet outage | The local cache; keep at least 7 days of content on each player plus fallback content | A second internet connection with automatic failover |
| Player app crash | The platform watchdog: the Watchdog app on Android, the SignService daemon on a Raspberry Pi, start-with-Windows or Shell Launcher, Login Items on a Mac, the kiosk policy on Chrome OS | A hot-standby player with HDMI switching |
| Power cut | Auto power-on in the BIOS or on a commercial player, then the watchdog relaunches the player | A UPS for the player and the display |
| CMS unreachable | Players keep playing the cached schedule | mediaSERVER for sites that must publish without the cloud |
Scaling from 1 to 1,000 screens
| Screens | Internet | Site network | Players | Management | Software per year |
|---|---|---|---|---|---|
| 1 | Any connection; 5 to 50 Mbps peak | Existing Wi-Fi or Ethernet | A stick, a Pi or a spare PC | The Screens dashboard | $0 |
| 3 | Same | Same | Same | Same | $0 |
| 10 | 25 Mbps minimum, 50 recommended | A dedicated VLAN helps; wired where possible | Mixed, by reach | Nightly restart, weekly uptime review | $360 |
| 50 | 50 Mbps minimum, 100 recommended | VLAN, wired, PoE for Pi players, QoS | Commercial players for unreachable screens | Alerts to site staff and IT | $1,800 |
| 100 | 100 Mbps minimum, 250 recommended | Same, per site | Standardized fleet, encoded for the weakest device | Alerts into a ticketing tool through the API | $3,600 |
| 1,000 | 500 Mbps or more per large site; per-site sizing | VLAN and QoS at every site, dual WAN where critical | Standardized, with spares per site | Enterprise features, proof of play, role-based users | Enterprise, priced per screen in the public calculator; or mediaSERVER at a one-time $895 plus player licenses |
The shape does not change with the count. What grows is the discipline around it: wired networks, standard hardware, alerts that reach a person, and a spare player on the shelf.
Frequently asked questions
How a digital signage network is built: CMS, players, content delivery and monitoring
Four layers. A CMS, SignStudio, holds media, scenes, schedules and the screen list, in the cloud or on an on-premise mediaSERVER at a one-time $895. A player behind each screen, DigitalSignage.com SignPlayer, downloads every asset into a local cache and plays from it. Delivery runs over outbound HTTPS on port 443, with a real-time socket that falls back to HTTP polling. The Screens dashboard monitors status, takes snapshots and restarts players. The first 3 screens are free forever, then $3 per screen per month.
What ports does a digital signage network need open?
Outbound only: TCP 443 to *.signage.me for SignStudio, registration, content and status, UDP and TCP 53 for DNS, and UDP 123 for NTP, which schedules depend on; port 80 is recommended for the redirect to HTTPS. No inbound ports and no static IP are required. HTTP, HTTPS, transparent and authenticated proxies are supported, SOCKS5 on Windows only. Ask support if your firewall needs exact hostnames instead of the wildcard.
How much bandwidth does a digital signage network need?
Per player at peak, during a content sync: about 5 Mbps for images, 10 to 20 Mbps for mixed content, 25 to 50 Mbps for 1080p video and 50 to 100 Mbps for 4K, downloading roughly 50 MB to 5 GB a day depending on content. Per site, plan about 5 Mbps average per display with 50 percent headroom: 50 Mbps recommended for 1 to 10 displays, 100 Mbps for 11 to 50, 250 Mbps for 51 to 200. Playback itself comes from the local cache, so the link is busy only during updates.
Should digital signage be on its own VLAN?
Yes. A dedicated VLAN with outbound-only rules to ports 443, 53 and 123 isolates player traffic from business systems, allows QoS for content downloads, simplifies troubleshooting and meets most security reviews, because DigitalSignage.com players need no inbound connections. Add wired Ethernet for screens you cannot reach, PoE for Raspberry Pi players, and keep SSL inspection off the signage VLAN or add an exception for the service.
What happens to a digital signage network when the internet goes down?
Screens keep playing. DigitalSignage.com SignPlayer caches every asset assigned to the screen and plays from the cache on its own clock, so dayparts still change on time. Only live content fetched as it plays, such as web pages, RSS, weather and streams, pauses. SignStudio shows the player offline; when the connection returns the player reconnects, syncs any changes published meanwhile and reports in. Keep at least 7 days of content cached, and consider dual internet connections for critical sites.
How do you monitor a digital signage network?
From the Screens dashboard in SignStudio: every player shows online or offline with its last check-in and version, you can take a snapshot of what is on screen, send Restart Player or Reboot Device where the platform's watchdog supports it, and schedule a nightly restart; alerts cover offline players and low storage. Review uptime weekly per site and target 99.5 percent for customer-facing screens. Proof of play, the log of what actually played where and when, is an Enterprise feature.
Related guides
- Digital signage network requirements
- Network and bandwidth planning
- Cloud vs on-premise digital signage
- Remote monitoring best practices
- Failover and redundancy architectures
- Security best practices
Try it on your own screens, free
DigitalSignage.com, which publishes this guide, runs a permanent free plan: the first 3 screens are free forever (no credit card, no ads, no watermark, no time limit), then from $3 per screen per month on Plus+. Once an account has 4 or more screens, every screen is billed, so 10 screens cost $360 a year; Enterprise is priced per screen in the public price calculator. The free DigitalSignage.com SignPlayer runs on Windows, Mac, Android and Android TV, Chrome OS, Raspberry Pi, iPad or any modern web browser, so the hardware you already own usually works. Start free · 2026 pricing · How 11 vendors compare on price
Maintained by MediaSignage Inc., operator of DigitalSignage.com since 2006. Product behavior on this page comes from our own SignStudio and SignPlayer documentation; where we do not document a step, this page says so instead of guessing. Last reviewed October 22, 2026.