What is SzeneraOS, and why does it run on its own?

SzeneraOS is the operating system on the Player Lite and the Player Pro. It has exactly one job: to show your content. A device like this runs for months without attention, and that is how it differs from any ordinary computer.

A system with a single job#

No desktop, no sign-in window, no office software. After power-on, the picture appears, without a mouse pointer and without a window that someone would have to click away. For each connected TV or monitor, the player opens a window of its own with its own content. On site, there is no interface in which someone could change anything: You decide in the portal what runs.

You cannot install your own software, because the device is closed. Whatever else you want to show, you embed as a web page. SzeneraOS exists only on our devices, and you use your own hardware as a web display in the browser.

The journey of a device, from the power outlet to retirement#

A player always passes through the same stations. Only two of them happen at a computer: pairing at the beginning and, at the end, re-pairing or removing.

Everything between pairing and retirement is done by the device itself.

Why nobody gets in from outside#

The player calls out, not the other way round. The device builds the connection to the platform itself. None is opened from outside, and its firewall discards incoming requests. It accepts maintenance only from the network at the installation site.

Every device identifies itself with a certificate of its own, which is created on the device at the first startup and never leaves it. Every 12 hours, the player checks its remaining validity and replaces it 14 days before expiry. Everything new that comes onto the device is signed: system updates as well as the bundles of the apps. What does not pass the check is not even unpacked.

Why it keeps running without supervision#

Content, schedule, images, and videos are on the device before they play for the first time. If the connection drops, your portal notices, but the display does not: The last valid state stays up, and as soon as the network is back, the player catches up on what has changed. Every 30 seconds, it sends a check-in.

If the display software crashes, it restarts within seconds. If crashes pile up, a watchdog restarts the whole device. If the system is so stuck that even the watchdog reports nothing, a separate component in the hardware switches it off and on again. A new system version is never written over the running one but into the second, currently unused half. It gets exactly one trial start and up to five minutes to prove itself. If it fails to prove itself, the old one runs again at the next start. You do not have to do anything for this.

It does not happen secretly: Every restart appears in the operations log, and through remote maintenance, you can get a screenshot of the running picture at any time.

What follows#

• There is nothing to set up and nothing to follow up on at the device. What you control, you control in the portal.
• A network outage is not an emergency. Only when a device reports offline for hours is the trip to the installation site worthwhile.
• A replacement device is paired in a minute: Content, schedules, and settings are in the platform, not on the memory card.
• Whoever holds the player holds the memory card. A display in a public space should be mounted out of reach.

Related#

• Player Lite
• How does a player keep itself running?
• How does a player update itself?