Wallboard cloud
Wallboard runs the whole stack. That covers monitoring and backups as well as updates. EU customers’ core data stays in the EU. US data stays in the US.
Deployment options
Cloud and on-premise digital signage servers.
Some teams want signage software they never patch. A hospital may need every file and log kept inside its own network. Wallboard runs in its own cloud, in a private instance that Wallboard hosts for you, on your Kubernetes cluster or servers, or in an isolated network. Users and screens work with the same application in every model.
Four ways to run Wallboard.
Private instance hosted by Wallboard
A dedicated Kubernetes cluster for your organization alone. Wallboard runs all of it, database failover, backups, restore testing and recovery included.
Your cluster or servers
Install from Wallboard’s Helm charts on managed Kubernetes in your AWS or Azure account, or on your own hardware with single-node K3s.
Isolated network
Run Wallboard without normal internet access. Images and charts are prepared ahead of time for the restricted environment. So are updates.
What your infrastructure team gets.
The same application
Content and scheduling work the same in every model. Channels and playback too. Players never need to know where the server runs.
A self-upgrading install
The on-premise bootstrap chart installs Traefik and cert-manager alongside Wallboard and a monitoring stack. Then it keeps all of them up to date.
TLS from the start
On-premise installs serve Wallboard over TLS by default. Certificates come from cert-manager, which issues and renews them.
Monitoring included
Prometheus and Loki ship with the on-premise install, with Grafana on top, so you can watch server health and logs from day one.
Backups you control
Scheduled backup jobs come with the install and can copy data offsite to S3-compatible storage.
Help when you want it
Wallboard can install, configure, migrate or manage your on-premise deployment under a statement of work.
Who looks after what.
- In Wallboard cloud, Wallboard runs hosting and updates, monitoring, daily backups kept for 90 days, and database encryption at rest.
- In a private instance hosted by Wallboard, Wallboard runs the dedicated cluster and its databases, plus monitoring, backups, restore testing and disaster recovery. Wallboard coordinates upgrades with you.
- On your own cluster or servers, your team owns the infrastructure and encryption at rest, plus backups and disaster recovery. You install updates, or Wallboard does so under a managed services agreement. Stay no more than one major release behind.
- Support for on-premise installs works through remote access to your environment. Wallboard makes no uptime commitment for infrastructure it does not run.
On-premise requirements at a glance.
- Managed Kubernetes is the recommended setup, with at least 3 worker nodes of 4 vCPU and 8 GB RAM each.
- A single-node install for up to 500 devices needs 4 vCPU, 16 GB RAM and 250 GB SSD. Above 500 devices, plan for 8 vCPU, 32 GB RAM and 500 GB SSD.
- The CPU must support x86-64-v2 with AVX.
- Recommended operating systems are Rocky Linux 9, RHEL 9, Ubuntu 24.04 or Debian 12. The minimum is Rocky Linux 8, RHEL 8, Ubuntu 22.04 or Debian 11.
- The network needs inbound TCP 80 and 443, optional UDP 123 for time sync, and outbound access to license.wallboard.info unless you run isolated.
- The databases are MySQL 8.4 or 8.0 and TimescaleDB, with Valkey 8 or Redis 7.2.
License telemetry.
On-premise installs send license key status, version information and counts of devices and users, and in an air-gapped network you send equivalent reports on request instead. Telemetry carries none of your content.
Ask for requirementsTell us where Wallboard has to run.
Share your security policies and your team’s Kubernetes experience. We’ll recommend a deployment model and send the full requirements.