In plain language — what each part is for, and why it's there. Screenshots are real captures from the live app.
A camera points at the TV and streams its picture to you with very low latency — so you see exactly what's on screen, wherever you are. To save bandwidth it only streams while someone is actually watching, with a short warm-up window so re-opening is instant.

A web remote sends key presses, volume and navigation straight to the TV over its LAN. Power is one smart button: it turns the TV off over the network, and wakes a sleeping TV with a Wake-on-LAN pulse — the button even reads the real on/standby state and relabels itself.

For developers: full Chrome DevTools for the web app running on the TV — inspect elements, watch the console and network — deep-linked straight to the right set, embedded in the page.
While you watch, the box can record the session locally — together with a synchronised track of every key you pressed. Later you can scrub the video, see exactly what was pressed when, and even replay those exact key presses onto a live TV — turning a recording into a repeatable test. You can also export a clip with the key labels burned into the picture.

The home screen: a glanceable summary of your devices, your favourites, recent recordings, and usage charts (activity, session lengths, busiest TVs) — plus a live bandwidth gauge for the operator.

Real logins with roles, two-factor authentication for everyone and 30-day trusted devices. Teams scope who can see which TVs; presence and hand-over stop two people fighting over one set; every meaningful action is written to an audit log.

When a TV or its box stops responding, a smart plug on its socket can power-cycle it remotely. Discovered on the network, controlled by the box, gated to admins and audited.
A superadmin can scan a site's network from the box to find cameras, TVs and plugs — each picked up with its MAC address. Because devices are tracked by MAC, a TV or camera that gets a new IP overnight is followed automatically, with no manual fixing.
Get a Tizen app onto the (selected) Samsung TVs without a laptop or Tizen Studio. A superadmin uploads the
site's signing certificates once (kept encrypted on the box, never in the cloud); the box then signs a
.wgt and pushes it straight onto the TV over the network — install and launch in a click, with
each step reported. It even re-signs another company's app with your certificate so it installs, and reads
the TV's DUID for you. Proven end-to-end on a real Samsung TV.
Recordings are kept within a per-user quota with a system disk reserve. When space runs low, the oldest un-starred clips are evicted automatically — starred ones are never touched, and every eviction is logged.

Point an AI client — Claude, or anything that speaks the Model Context Protocol — at your sets. It can read their state, health, recordings and stats, and drive the TV: press remote keys, switch power, replay a recorded scenario. Each agent acts with the rights of the user who connected it — never more — and every action is audited as that person. A thin, stateless server forwards your token to the relay, which stays the single authority; it holds no standing credential of its own. How MCP works →
See these on the real screens in the app walkthrough, the technical design in architecture, or the deep dive on the MCP API.