Korbyt Vega and BSN.cloud

Why to setup paths exist, and how to enroll a Vega in BSN.cloud

Written By Ed Kinne

Last updated 10 days ago

What is a Korbyt Vega

The Korbyt Vega is a Korbyt-branded BrightSign UH1145
— the exact same hardware and chipset as a standard XT1145, just a different model number under Korbyt's branding—
What makes Vega different in practice is that it leaves the factory pre-loaded with a Korbyt-qualified BrightSign OS build and the Korbyt Player Application already installed, so it can provision straight to Korbyt Anywhere without ever touching bsn.cloud.

What is BSN.cloud

BSN.cloud is BrightSign's own device-management layer — it sits underneath the Korbyt app and controls the OS, firmware, and network stack.
Connecting the device to the BSN.cloud is optional, and a customer can layer it on top of a Vega's factory setup any time they need control at that lower level.
The two systems don't compete: Korbyt manages content, BSN.cloud (when used) manages the hardware it's running on.

Comparing Deployment Options

	Korbyt Only (Factory Default)	Korbyt + BSN.cloud (layered)
What	Vega ships pre-loaded with a Korbyt-qualified OS build and the Korbyt Player Application already installed. It provisions straight to Korbyt Anywhere.	The same Vega is additionally enrolled in BrightSign's own device-management cloud, on top of the pre-loaded Korbyt setup.
Manages	Content, playlists, scheduling, screen health/heartbeat — entirely inside Korbyt Anywhere.	BrightSign OS, firmware channel/version, network config (proxy, static IP/DNS, 802.1x), diagnostics, WiFi — underneath the Korbyt app.
Good Fit When	Standard network, no corporate proxy, customer wants one pane of glass (Korbyt only).	Corporate proxy or restrictive network policy, custom root CA install, firmware pinning, or IT wants BrightSign fleet visibility alongside Korbyt.
Does it Replace Korbyt?	N/A — this is the baseline.	No. BSN.cloud does not remove or disable the Korbyt Player Application. It's an added layer, not a replacement.

Reasons you may want to layer on BSN.cloud

Network-level control — proxy, static IP/DNS, 802.1x — is one common driver, since those settings live below the Korbyt Player Application and aren't exposed in Korbyt Anywhere. But BSN.cloud brings a full set of BrightSign OS-level tools that IT and support teams use alongside Korbyt, including:

Remote reboot — power-cycle a player without a truck roll or someone on-site.
Real-time player health reporting — a useful fallback or cross-check alongside Korbyt's own monitoring.
Network details — live IP, DNS, and connectivity state for troubleshooting.
Logs — pull device and diagnostic logs remotely instead of walking up to the unit.
Remote screenshots — see exactly what's on screen right now without being on-site.
Player and grouped-player management — organize, monitor, and act on players individually or in bulk across a fleet.

How to enroll an already-deployed Vega in BSN.cloud

Create (or confirm) a BSN.cloud network — this is the network the Vega will report into.
Get the Vega's serial number, either from the label on the unit or from its local diagnostic web server (http://<player-ip>, user admin, password = serial number).
In BSN.cloud, go to Network → Device Provisioning → Add Device, and register the Vega by serial number (pre-register it to a Device Setup if you want settings applied on first check-in).
In that Device Setup, configure the network-level settings the customer needs — proxy host/port, static IP/DNS, root CA, etc.
Reboot (or Reprovision from the device's Control tab) so the Vega pulls its new BSN.cloud provisioning record and network config.
Confirm the Korbyt Player Application is still the active autorun app after reprovisioning, and that content is still pulling from Korbyt Anywhere as expected.

Enrolling in BSN.cloud is additive, not a migration.
It does not disable or replace Korbyt on the device — you only needs it control something Korbyt's CMS doesn't expose, most commonly a corporate proxy or custom network policy.