Anthias VS concerto

I used ScreenlyOSE Anthias + BalenaCloud on about 7 Pi devices to manage a small-scale DSS rollout. BalenaCloud allowed fleet-wide updates, etc. and a rudimentary VPN tunnel to connect to each Pi. It might scale to 4,000, but you'll spend a lot of time babysitting that.

There’s also screenly which is open source and has a paid version if you want more advanced features: https://anthias.screenly.io/

Anthias is the free version of Screenly: https://anthias.screenly.io/

We used to use the Open Source Edition of Screenly. If you're okay with managing each display separately by IP it might be a workable option, though time consuming. Paid version offers a centralized CMS, but I haven't tried it.

My higher education institution has bought every generation of these for Digital Signage since 2014. We use an open-source (abandonware?) Ruby project called Concerto[1] to generate webpages, and the Chrome OS Kiosk Mode[2] feature to boot these things straight to chrome-less full-screen web browsers that load Concerto webpages. It's a nice setup, but I do worry about the future support of both of those pillars.

1. https://github.com/concerto/concerto

2. https://chromeenterprise.google/os/kiosk-and-digital-signage...

You could take a look at Concerto. A group of RPI students developed it to use as their campus signage system. I’ve deployed it twice before and it’s a pretty flexible system, you can add images, announcements, sync with an iCal. You can even add multiple users with different permissions (high school staff can only manage the high school sign).