Skip to main content
Korbyt Basics

Korbyt Network Architecture Diagrams

Written By Ed Kinne

How your player connects and the specific path the player’s connection will take will differ if your solution is Cloud, Hybrid, or On-Premise

Any Content scheduled to a player that pulls information with an external URL but must be able to access that url (https and http requests) from the player’s location on the network.

This rule also applies to players scheduled with OnTarget content.

Hybrid gives the flexibility of Cloud access and the security of an On-Prem connection to your data

Important things to know about this configuration!

1. The Korbyt Media Player will attempt to make its FIRST connection to the cloud servers to provision and obtain the local server name. It will then switch all communication to the on-prem server. The on-prem server can be manually configured on the Korbyt Media Player configuration pages to prevent having to make this connection.

2. All Korbyt Media Players are pre-configured with external NTP servers to sync time. If this is not allowed, all players will need to be pointed to an internal NTP server to prevent time drift.

3. All players that are scheduled with URLs, but are able to access that URL (https and http requests) from the player’s location on the network. This rule also applies to players scheduled with OnTarget content.

4. The on-prem server must retain communication to the cloud. If changes to a player are made on your tenant while the connection from the on-prem server to the cloud has been severed, the changes will not reflect on the player.

Fully On-Prem solutions require all Korbyt CMS Users to be on the same network as the system

There is NO cloud service with a Fully On-Prem service