Reference, network
Network and firewall requirements
What a screen running Adverro needs from your network, written for the person approving the firewall change: the destination, the direction, what travels over it, and what happens when the connection goes.
A screen opens every connection itself, so no inbound rule is needed. It reaches the same four destinations on Samsung Tizen, LG webOS, Android and Windows, and keeps playing from its local cache when the connection drops.

The short version
Outbound only. Nothing inbound.
A screen opens every connection itself, and nothing on the internet needs to reach it, so no inbound rule is required. It connects out to four destinations, the same on Samsung Tizen, LG webOS, Android and Windows.
services.adverro.app | The Adverro service, on Microsoft Azure App Service: TCP 443, HTTPS, encrypted with TLS 1.2 or higher. Schedules to the screen; playback traces, device status and licence validation from it. The screen also takes its time from this service, so no separate time server is called. |
package.adverro.app | The package server the application is installed from, with a separate endpoint for each operating system and version. |
Media storage | Media files are downloaded directly from blob storage, using a time-limited access token the screen requests from services.adverro.app first. The storage address is confirmed at deployment. |
Live view relay | Used only when someone opens the live view of a screen in the platform. The screen connects to a relay (Web PubSub, with ICE servers for the picture) that is allocated for that session, so its address is not fixed. |
What travels over the connection
Four kinds of traffic to the service.
Content and schedules
Playlists and schedules come from the service, and media files straight from storage with the access token the service issues. Everything is held in the local cache. Video in any codec is optimised for each device before it is delivered.
Playback traces
Every play produces a trace, and the traces are sent back to the platform, where proof of play and uptime are calculated. A screen that is offline keeps recording and sends its traces when the connection returns.
Licence validation
There is no separate licence server. The same service validates the screen’s licence continuously, using the screen’s own authentication token, so the licence check adds no destination to the allow-list.
Application updates
Updates to the Adverro application are published centrally and pulled by the screen when it restarts. Panel firmware is a separate matter: it comes from the manufacturer or is managed by you, not by Adverro.
Content that lives elsewhere
Your own sources need a route as well.
Some content is not stored in Adverro at all. A web view zone loads the page you point it at, and a live stream is pulled from its streaming server over HLS or WebRTC. When a schedule includes content like this, the screen fetches it from that address, so the address has to be reachable from the screen’s network too.
This is the part of the allow-list that belongs to you rather than to us: the departures page your operational system publishes, the menu page your pricing system serves, the stream your events team runs. List them when the change request is raised rather than when a zone goes blank.
Networks that cause trouble
Three situations worth designing out.
A guest network with a login page
A captive portal asks for a browser login that a panel cannot complete. The screen appears online to the network and offline to the platform. Put screens on a wired connection or a dedicated VLAN instead.
DNS or proxy changes
When a site’s network changes underneath the screens, usually during unrelated IT work, several devices at one site stop checking in together. The fix is on the network, not the panels, so tell the signage team before the change rather than after.
Everyday connection loss
A Wi-Fi drop, a switch reboot, a DHCP lease that is not renewed or a cable disturbed in a ceiling void. Playback continues from the cache, and most of these clear themselves. The physical ones do not.
Segmentation is welcome
Because every connection is outbound, screens can sit on their own VLAN with no inbound rules at all, separated from the rest of the estate. Nothing in Adverro depends on a screen being reachable from the corporate network.
When the connection goes
What the screen does on its own.
Playback | Continues from the local cache for as long as the screen’s licence token remains valid. |
Scheduled changes | Happen on time while offline, provided the content was downloaded before the connection went. |
Cache size | Limited only by the storage on the panel. |
Status in the platform | Counted as offline after five minutes without a playback trace. Before that it is not yet counted as offline. |
The record | Traces recorded while offline sync back when the connection returns. A screen holds up to 5,000 KB of logs; beyond that the oldest entries are truncated. |
Licence expiry | No grace period. Access stops on the expiry date, and you are notified in advance through the portal and by email. |
For the change request
The checklist to hand your network team.
1. The service | Outbound TCP 443 to services.adverro.app from the network the screens sit on. |
2. The package server | package.adverro.app, so panels can install the application. The exact Custom App URL comes from your account manager. |
3. Media storage | The storage address your product specialist confirms at deployment. |
4. The live view | If your team will use the platform’s live view, the relay domains your product specialist gives you. |
5. Your sources | The addresses of any external content you schedule, for example pages shown in web view zones and live stream servers. |
6. Leave inbound closed | The screens need no inbound rule. |
7. Choose the network | A wired connection or a dedicated VLAN, not a guest network with a login page. |
8. Warn before changes | Let the signage team know before DNS or proxy changes on that network. |
Bring your network team to the demo.
If your screens sit behind a proxy or on a restricted network, an engineer will walk the path from the screen to the service with the people who own it.
Hybrid and on-premise
Screens that talk to a local server.
The checklist above describes a cloud deployment, where every screen reaches one outbound destination. In a hybrid deployment the screens on a site talk to the local server on that site instead, and only the local server needs an outbound path to the cloud platform. In an on-premise deployment nothing needs to leave your network: the screens, the local server and the platform all sit inside it, and the only external traffic is the optional update channel you choose to allow.
The ports and protocols on the screen side are the same in every model, so a network team that has approved a cloud deployment has already approved the screen traffic for hybrid and on-premise. What changes is the destination address, which is supplied with the deployment plan.