Skip to content

UnyDesk Introduction

UnyDesk is the remote access architecture of the platform. It gives users and operators a controlled way to reach a machine through a browser session, a host runtime and a broker API.

The product is organized around three public roles:

  • Host: the machine that exposes access
  • Viewer: the browser-side user opening the session
  • Broker: the UnyDesk service that authenticates, routes and synchronizes the session

UnyDesk is intentionally separate from TRINITY and UnyPort. TRINITY handles customer lifecycle and service entry points. UnyPort handles local supervision and operations. UnyDesk handles interactive remote access.

What UnyDesk solves

UnyDesk is used when the user needs to:

  • Download or run a host package
  • Claim or trust a host
  • Create a remote session
  • Route the viewer to the right host
  • Exchange signaling between browser and host
  • Continue the session when the best realtime path is not available

Public architecture in one view

Browser viewer
  -> UnyDesk broker
  -> trusted or claimed host
  -> session signaling
  -> WebRTC or fallback screen path

The broker remains the stable coordination point. The media path can be direct when possible, but session state, routing and fallback behavior remain visible through UnyDesk.

Documentation path

Read this section in this order:

  • Presentation For the product view
  • Architecture For the runtime model
  • Manual For the practical user path
  • Host distribution For downloads and packages
  • Session broker For session lifecycle and signaling
  • Security and operations For public operating boundaries