On-premiseInstalled on your servers

Your data stays with you.

Plyb TV is not a third-party cloud service. It is installed on your own organisation's servers, with your network and your corporate directory.

Your network

Your organisation's server

  • Plyb TV application
  • Database
  • Published content

IdentityLDAP or local users

ManagementFrom the browser

North site

South site

Central site

A single network entry point

Third-party cloudNot involved. Your content, users and screens are managed inside your network.

LicenseYour server validates it against Plyb, outbound only. Plyb never opens a connection into your network.

Diagram: the application, database and content are installed on a server inside the organisation's network, connected to its identity system and to the screens at each site, with a single network entry point. No third-party cloud is involved. The only thing that goes out is license validation, always initiated by the organisation's server.

01Where it lives

What's yours stays inside your network.

The application, database and content are installed on your own infrastructure, connected to your corporate directory (LDAP) or with local users. Your content, users and screen inventory never pass through an external cloud, and everything is managed from the browser, with nothing to install on each computer.

The only thing that goes out to the internet is license validation: your server checks it against Plyb's, always outbound. Our server never initiates a connection to yours.

What gets installed, and where

Web applicationyour server
Databaseyour server
Content filesyour server
User identityyour LDAP or local users, one or the other
Network entry pointsone
Connection to Plyblicense validation only, outbound
On each computernothing, just the browser

02Continuity

What happens if the server stops responding.

Screens keep the last thing you published, so they carry on showing it while the service recovers: content doesn't suddenly disappear.

Management does need the server: while it's down you can't send new commands or change schedules. If your case requires surviving the loss of an entire machine, there's a configuration ready for that, and we'll go through it in the demo.

Server not respondingThe screen keeps its content

Lobby · South site · still showing the last publication

Want the exact technical requirements?

Ask for the technical requirements