Remote Viewer Remote Support Software

Remote Viewer is a cross-platform remote access and support platform built for IT professionals, businesses, support teams and service providers that need secure, controlled and reliable device support across desktop, mobile and web.

What Is Remote Viewer?

Remote Viewer is a cross-platform remote access and support platform designed to provide secure, controlled and reliable device support across Windows, macOS, Linux, iOS, iPadOS, Android and modern web browsers.

It brings native desktop support, attended mobile screen-sharing apps, browser-based technician access, a company customer portal and a central Broker into one connected remote support ecosystem.

Remote Viewer is built for IT professionals, businesses, support teams, service providers and users who need practical attended or managed remote support without unnecessary complexity.

How Remote Viewer Works

Remote Viewer uses a secure Broker-based architecture to authenticate, route and manage remote support sessions between technicians and customer devices.

  • Devices authenticate and register with the Remote Viewer Broker
  • Technicians connect using one-time support credentials or authorised account access
  • The Broker manages authentication, session state and routing between both sides
  • Remote devices use outbound platform connections instead of requiring direct inbound access to the customer device

This makes Remote Viewer easier to deploy across mixed networks, NAT environments, firewalls and different operating systems without exposing inbound remote-access ports on customer devices.

Security is built into every Remote Viewer session. Connections to the Broker are protected using TLS, while sensitive session commands and data are protected with application-layer end-to-end encryption between the technician viewer and the remote device. Screen media uses encrypted native UDP v2 or WebRTC transport. The Broker authenticates and routes sessions without needing plaintext access to protected session content.

The Remote Viewer Platform

Remote Viewer is not just one app. It is a full remote support platform made up of several connected parts.

Broker Middleware

The Broker is the central authentication, routing, relay and session-state layer. It handles device identity verification, one-time support codes, authorised technician connections, live session state, encrypted control and data routing, WebRTC signalling and native UDP screen relay where required.

Customer Portal

The Customer Portal provides account and company access, device visibility, login and registration flows, email verification, TOTP two-factor authentication, recovery codes, trials, subscription and billing handling, plan entitlements and administrative device management.

Web Viewer

The Web Viewer gives technicians a no-install way to connect from a browser. It supports session dashboards, live screen viewing and control, screen switching, fullscreen and fit-to-screen viewing, chat, clipboard handling, file browsing and transfers, a remote command console and supported desktop actions such as lock and reboot.

Desktop Clients

Remote Viewer includes native desktop support for Windows and macOS, while the Broker also provides dedicated Linux client and data-channel support. Desktop workflows include live screen access and control, session handling, chat, clipboard, files, command access and multi-screen support where the operating system allows them.

Mobile Clients

Remote Viewer also supports iOS, iPadOS and Android. The mobile apps use attended, system-authorised screen sharing: ReplayKit broadcasting on iOS and iPadOS, and MediaProjection on Android. Android can also accept supported remote input when its optional Accessibility service is enabled by the user.

Supported Platforms

  • Windows – Full desktop support architecture with service, app, session helper, native H.264 screen transport and technician components
  • macOS – Native app, daemon and capture-agent support with multi-screen operation for Apple desktop devices
  • Linux – Dedicated Broker client and data-channel protocol support for Linux desktop connections
  • iOS and iPadOS – Attended ReplayKit screen sharing with native UDP v2 first and WebRTC fallback
  • Android – Attended MediaProjection screen sharing with native UDP v2 first, WebRTC fallback and optional Accessibility-based remote input
  • Web browsers – No-install technician access with screens, control, chat, files and commands where the remote platform supports them

What Remote Viewer Can Do

  • Live remote screen viewing and remote input on supported platforms
  • Technician access through native apps or the browser
  • One-time support credentials and authorised account-based connection
  • Broker-authenticated and routed sessions with protected control and data payloads
  • Company-linked device management and plan-based entitlements
  • Online, offline and active-session device visibility
  • Device nicknames, platform details and company assignment
  • Chat and clipboard support during compatible desktop sessions
  • Multi-screen and all-screens support where available
  • Remote file browsing, transfers and command-console features on supported desktop clients
  • Attended mobile screen sharing for iOS, iPadOS and Android, with optional remote input on Android

Security

Remote Viewer is designed around multiple layers of security rather than relying on a single password or connection barrier. Protection is applied to account access, device identity, technician authentication, session establishment, commands, transferred data and screen media.

Encrypted Connections

Connections between Remote Viewer applications, the Customer Portal and the Broker are protected using TLS. This encrypts information while it travels across the internet and protects connections against passive interception and unauthorised alteration.

End-to-End Session Encryption

Sensitive session commands and data are protected with application-layer end-to-end encryption between the technician viewer and the remote device. Remote Viewer establishes session keys using authenticated P-256 elliptic-curve key exchange, derives separate directional keys using HKDF-SHA256 and protects session payloads using authenticated AES-256-GCM encryption.

Separate encryption keys are used for each session and communication direction. Authentication tags, sequence validation and signed session handshakes help detect altered, replayed or unauthorised session messages.

Protected Screen Media

Screen media is transmitted using encrypted native UDP v2 or encrypted WebRTC transport. Native UDP v2 screen packets use authenticated AES-256-GCM encryption. The Broker can relay these packets when required, but it does not receive the media encryption key and therefore cannot decrypt the protected screen content.

Cryptographic Device Identity

Remote devices and technician applications use persistent P-256 cryptographic identities. Signed authentication challenges allow the Broker and session participants to verify that a connection is being made by the expected device or technician instead of relying only on reusable passwords.

Trusted device fingerprints can be checked during encrypted session establishment. A session is rejected if an identity proof is invalid, revoked or does not match the trusted device identity.

Temporary Support Access

Attended support uses randomly generated six-digit support codes that expire after 15 minutes. A support code is consumed when the authorised session begins and is invalidated after repeated incorrect attempts, reducing the risk created by permanent or repeatedly reusable access credentials.

Broker-issued device and technician session tokens are also short-lived and are stored and compared using protected credential hashes rather than retained as plaintext authentication values.

Account and Portal Protection

The Customer Portal supports authenticator-app two-factor authentication, one-time recovery codes, secure password hashing, login rate limiting, restricted two-factor attempts, protected sessions and anti-forgery validation for sensitive account actions.

These protections help reduce the risk of password guessing, automated login attempts, stolen-password access and unauthorised account changes.

Permission-Based Access

Remote Viewer follows the security and permission model of each operating system. Mobile screen sharing cannot silently begin in the background: iOS and iPadOS require the user to start a ReplayKit broadcast, while Android requires MediaProjection consent. Android remote input additionally requires the user to enable the optional Accessibility service.

Desktop screen capture, remote input and other privileged features remain subject to the permissions and security controls provided by Windows, macOS and Linux.

Reduced Network Exposure

Remote devices establish outbound connections to the Remote Viewer platform. Customers do not need to expose a remote desktop service or open a direct inbound remote-access port on each supported device, helping to reduce the externally reachable attack surface.

How Secure Is Remote Viewer?

Remote Viewer uses modern, established cryptographic protections and layered authentication controls throughout the platform. Its design limits reusable credentials, verifies device identities, encrypts session content and avoids unnecessarily exposing remote devices directly to the internet.

No remote access product can truthfully guarantee that it is impossible to compromise. Remote Viewer is designed to provide strong practical protection when the platform is correctly deployed, accounts are protected with two-factor authentication, devices are kept updated and users only approve support sessions they recognise.

Why Remote Viewer Exists

Many remote access tools are complicated, expensive, restrictive, or designed around one primary platform with other device types treated as secondary.

Remote Viewer was built to be different.

  • Straightforward to use
  • Fast to deploy
  • Practical across desktop, mobile and web
  • Controlled through a Broker-based platform
  • Built around real support workflows

The aim is to keep the product focused: no unnecessary clutter, no over-complicated workflow, and one connected platform for supporting different device types.

What Makes Remote Viewer Different?

  • Broker-controlled architecture – Devices and technicians are authenticated while sessions are routed and managed centrally
  • Cross-platform design – Windows, macOS, Linux, iOS, iPadOS, Android and web access are handled through the same platform
  • Browser technician access – Technicians can use a full browser console without installing a desktop viewer
  • Company-based management – Devices, users, plans, trials, billing and two-factor authentication are managed through the portal
  • Mobile-aware support – iOS, iPadOS and Android use permission-based attended screen sharing, with optional remote input on Android
  • Desktop-focused depth – Windows and macOS provide service or daemon-backed workflows, while Linux has dedicated Broker protocol support
  • Clean user experience – The platform is built around clear technician workflows without unnecessary UI noise

Remote Viewer is developed as one integrated remote access platform, with the Broker, Portal, Web Viewer and native clients designed to work together rather than as disconnected products.

Who Remote Viewer Is For

  • IT professionals
  • Support engineers
  • Helpdesks
  • Managed service providers
  • Businesses managing remote devices
  • Individuals who need reliable remote support
  • Anyone who wants control without unnecessary complexity

The Goal

The goal of Remote Viewer is to provide a clean, secure, powerful and practical remote access platform that works across modern devices while keeping the workflow simple.

  • Works across desktop, mobile and web
  • Keeps access authenticated and routed through the Broker
  • Gives technicians flexible native-app and browser-based ways to connect
  • Gives users and businesses clear visibility of devices, sessions and plan entitlements
  • Keeps remote support straightforward, resilient and secure