Evaluating Stadium Display Software: A Network and Security Guide for School and College IT Directors

The Campus IT Challenge: Balancing Gameday Connectivity with Network Security

When an athletic department plans a gymnasium or stadium upgrade, software approval often depends on a thorough review by the school district or university IT department. Many general-purpose digital signage tools and cloud-based scoreboard apps require continuous outbound internet access, external cloud relay servers, or poorly documented firewall exceptions just to display a live score or connect a scorekeeper’s tablet.

For campus IT directors and network administrators, cloud-dependent stadium display software introduces two major concerns: network security exposure on the school’s wide-area network (WAN) and operational vulnerability if the internet connection drops during a crowded Friday night game.

Evaluating scoreboard control software and LED video board control software through a network-architecture lens helps both athletic directors and IT administrators select a platform that runs reliably on the local area network (LAN) while respecting campus security policies.

What IT Directors Should Look For in Stadium Display Software

Before approving video scoreboard software or sports video display software for campus deployment, IT teams should verify four architectural requirements:

1. 100% Local Gameday Execution: Live scoreboard rendering, hardware console communication, media playback, and mobile scoring remotes should operate entirely on the local computer or isolated venue LAN—so an external internet outage never interrupts a live game.
2. Predictable, Non-Disruptive License Verification: If software uses online license activation, periodic license checks should occur only when the application launches—never in the middle of a live sporting event.
3. Documented Local Ports and Localhost Defaults: Network administrators should not have to run packet captures to discover which TCP or UDP ports an application opens. Any built-in web or API servers should default to local-only access (localhost) unless an operator explicitly enables LAN access.
4. Offline Wireless Options for Isolated Venues: In stadiums or fieldhouses where the IT department prefers not to place scorekeeper phones or tablets on the campus network, the software should support an isolated local Wi-Fi hotspot.

How Fair-Play Fusion Is Engineered for School and Campus Networks

Fair-Play Fusion is LAN-first stadium display software and scoreboard control software that drives jumbotrons, LED ribbon boards, concourse displays, sponsor panels, and scoreboards from a single Windows PC or Apple silicon Mac. Every gameday service runs locally on the host computer:

1. Local Gameday Operation & Startup-Only 60-Day License Check: All scoreboard templates, media files, Proof-of-Play SQLite logs, hardware protocol parsers, and the mobile remote server run locally on the venue computer. Fusion requires internet access only for initial license activation (or starting a 30-day trial) and for a brief license verification at least once every 60 days. Crucially, that 60-day check is evaluated only when Fusion starts—never during a live game.
2. Built-In "Give to IT" & "Help Me Connect" Diagnostics: To save athletic directors and network administrators time, Fusion includes a "Give to IT" button directly on the Connections › Mobile Device Server panel (and on the license activation dialog). With one click, Fusion displays the exact local IP addresses, port numbers, subnet requirements (such as disabling Wi-Fi client isolation on the scorer’s VLAN), and the exact Windows Firewall command needed—paired with a four-step "Help me connect" diagnostic tool that verifies server status, network adapter binding, firewall rules, and local reachability.
3. Encrypted Local HTTPS Mobile Remotes & Localhost-Default APIs: When scorekeepers connect Apple or Android phones or tablets via QR code, traffic remains 100% on the local network (ports 8765 and 8766). Devices complete a one-time Step ① local CA certificate trust (fairplay-fusion.crt, with its SHA fingerprint displayed on screen) to establish encrypted local HTTPS—requiring no public app store downloads and no third-party cloud relays. Additionally, vMix, OBS, and Control API endpoints (port 3000) require a regenerable access token and listen only on the local computer (localhost) by default until an operator explicitly checks "Allow other devices on this network to connect."
4. Built-In Windows Wi-Fi Hotspot & Flexible Deployment Packages: If IT policy prohibits scorekeeper mobile devices from joining the campus Wi-Fi network, Windows operators can start Fusion’s built-in Wi-Fi Hotspot to create a direct local wireless link between the scorer’s table PC and the table crew’s devices. For software deployment, Windows supports both a standard per-machine Setup installer (which automatically configures the Fair-Play Fusion NDI inbound firewall rule) and a self-contained Portable .exe that runs without modifying system firewall rules.

Technical Specifications: Network Ports, Security & Deployment

• Local Gameday Execution: Graphics rendering, serial/UDP hardware scoring, mobile device server, and Proof-of-Play SQLite logging run 100% locally on the host computer.
• Non-Disruptive Licensing: Internet access is required at initial activation and once every 60 days; the license check runs strictly at application startup, never during a game.
• Documented Local Ports ("Give to IT"):
  • Mobile Device Server: TCP 8765 & 8766 (or next free pair; local HTTPS with self-signed CA certificate).
  • vMix / OBS / Control API: TCP 3000 (up to 3010); local-only (localhost) by default unless network access is enabled, protected by an access token.
  • Network Scoreboard Data: UDP 5000 (adjustable 1024–65535).
  • Open Sound Control (OSC): Receives on UDP 9000; sends to user-configured host/port.
  • Timing & Network Scoreboard Bridges: FinishLynx listens on UDP 5800 / TCP 5801; local network scoreboard bridges connect outbound on TCP 1402.
• OS & Deployment Packages: Windows 10 or 11 (64-bit x64 per-machine Setup installer or no-install Portable .exe) and macOS with Apple silicon (M1 or later, Fair-Play-Fusion-arm64.dmg; Intel Macs not supported).

Hypothetical Example: Streamlining a School District IT Security Review

The following is a hypothetical scenario illustrating how an athletic department and district IT team can evaluate stadium display software before deployment.

Imagine a public school district upgrading four high school gymnasiums with new LED video boards and concourse displays. The district’s IT department requires all venue software to pass a network security review and prohibits athletic AV computers from relying on external cloud relays during live events.

During the evaluation, the athletic director launches Fair-Play Fusion on a test laptop, opens the Connections tab, and clicks "Give to IT." That screen provides the district Network Administrator with the complete port table (TCP 8765/8766 for local HTTPS mobile remotes, localhost-default TCP 3000 for streaming overlays, and the outbound license server used only at startup every 60 days), along with the option to use the built-in Windows Wi-Fi Hotspot in gymnasiums that do not have a dedicated AV VLAN. With clear documentation built into the software, the IT department can quickly verify compliance and configure the venue machines.

Review Fair-Play Fusion’s Architecture with Your IT Team

Want to inspect the built-in network diagnostics and "Give to IT" specification sheet firsthand? Visit Fair-Play.com to learn more about Fair-Play scoreboard and display solutions, or contact our team to request a 30-day evaluation copy for your athletic and IT staff.