OneAdvanced has just deployed over 50 AI agents on UK-sovereign AWS. The headline is a reminder: where your data lives still matters. For facilities and IT teams weighing digital signage, that question, cloud or self-hosted, isn’t just about geography. It’s about licensing costs, what happens when the network drops, and who ends up fixing it when things go wrong.
Where the screens are doesn’t decide where the data sits
Cloud digital signage platforms typically send every playlist, alert, and usage log to a vendor’s data centre. If that centre is outside the UK, the Information Commissioner’s Office (ICO) still expects a transfer risk assessment under UK GDPR. Self-hosted software runs on your own server, so the data never leaves your control. That’s the simple part.
The complication is that "your own server" can mean a VM in your data centre, a colo cage in Slough, or a UK-based AWS region. OneAdvanced’s deployment shows that sovereignty and cloud aren’t mutually exclusive, if you’re willing to pay for the premium regions and accept that AWS’s shared responsibility model still leaves you patching the OS.
Licensing: per-site versus per-screen
Cloud platforms usually charge per screen. A 50-screen estate can cost £1,200–£1,800 a year in licensing alone. Self-hosted digital signage is licensed per site, so the same 50 screens might cost £600–£900 a year, regardless of how many screens you add. The catch is that the site licence doesn’t cover the server hardware, the backup regime, or the IT time to keep it running.
| Factor | Cloud model | Self-hosted model |
|---|---|---|
| Licence cost | Per screen, recurring | Per site, recurring |
| Hardware cost | None | Server, storage, backup |
| IT overhead | Minimal | OS patches, monitoring, DR |
| Scalability | Add screens, add cost | Add screens, no extra licence |
| Data residency | Depends on vendor’s regions | Your choice |
Offline behaviour: what happens when the WAN fails
Cloud signage relies on a live connection. If the WAN drops, screens either freeze or show a cached loop. Self-hosted software can be configured to keep playing the last received playlist, switch to a local emergency channel, or even pull content from a USB stick. The resilience is higher, but only if someone has set up the fallback rules and tested them.
In practice, most estates see 99.5% uptime on the WAN. The remaining 0.5%, about 44 hours a year, is when the emergency alert needs to work. Cloud platforms typically offer a 99.9% SLA for their service, but that doesn’t cover the last mile. Self-hosted systems can push alerts over a separate 4G dongle or a secondary ISP, but again, someone has to wire it up.
The hidden cost: IT time
Self-hosted digital signage shifts the maintenance burden from the vendor to your team. A typical 50-screen deployment needs:
- A VM with 4 vCPUs, 8 GB RAM, 200 GB storage (£15–£25/month in cloud IaaS, or £1,200–£2,000 for a physical server).
- Monthly OS patches and security updates (1 to 2 hours).
- Quarterly backup restoration tests (2 hours).
- Annual disaster-recovery rehearsal (4 hours).
Over three years, that’s 50 to 60 hours of IT time, plus hardware depreciation. Cloud platforms bundle those tasks into the subscription, so the trade-off is clear: pay the vendor to do it, or pay your team.
Data residency isn’t just about compliance
UK GDPR requires that personal data, including IP addresses and screen-viewing logs, stays within the UK or a country with an adequacy decision. Cloud vendors offer UK regions, but the fine print often reveals that support tickets, billing data, or analytics dashboards still route through the US. Self-hosted software keeps everything on-prem, so there’s no transatlantic hop to audit.
The ICO’s guidance on international transfers (July 2025) makes it plain: if the data leaves the UK, you need a transfer risk assessment. Self-hosting removes that requirement entirely, but it also removes the vendor’s compliance team. You become the data controller for the signage system, which means you’re responsible for the data protection impact assessment and any breach notifications.
When self-hosted makes sense
- You already run an on-prem data centre or a private cloud.
- You have a 24/7 IT team that can handle out-of-hours alerts.
- Your estate is large enough that per-site licensing is cheaper than per-screen.
- You need offline resilience that survives a WAN outage.
- You have strict data residency requirements that cloud vendors can’t fully meet.
When cloud makes sense
- You don’t have the IT bandwidth to patch servers and test backups.
- Your screen count is small or fluctuates seasonally.
- You want the vendor to handle compliance and uptime SLAs.
- You need to deploy quickly, without waiting for hardware procurement.
- Your data residency needs are met by the vendor’s UK regions.
What to do next
- List every screen you want to cover and note whether it’s on a wired or wireless network.
- Check your IT team’s capacity for server maintenance, ask how many hours a month they can allocate.
- Run a three-year cost comparison: cloud per-screen licence versus self-hosted site licence plus hardware and IT time.
- If data residency is a concern, ask cloud vendors for a data-flow map that shows every country their systems touch.
- Test offline behaviour: unplug a screen for 30 minutes and see what it shows. Do the same with a simulated WAN failure.
The choice isn’t binary. Some estates split the difference: cloud for most screens, self-hosted for critical areas like fire exits and control rooms. The point is to know the trade-offs before the network fails.
