AI-native
The diagnostic assistant can inspect device state and recommend fixes. It runs an approved command only after the device owner confirms it, while the external MCP service remains read-only.
Connect to remote devices securely over low-latency WebRTC, with AI-assisted diagnostics, per-command confirmation, device authorization, and auditing in one platform. Personal, team, and private deployments share the same product foundation.
The diagnostic assistant can inspect device state and recommend fixes. It runs an approved command only after the device owner confirms it, while the external MCP service remains read-only.
Browser, host and signaling server negotiate to establish low-latency peer-to-peer media and data channels over WebRTC.
Capture screens and system audio with X264, OpenH264, VP8, VP9, and AV1 options for different devices and network conditions.
Mouse, keyboard and shortcut input, clipboard sync, file management and transfer, plus a complete remote terminal for everyday work and troubleshooting.
Manage organizations, members, device access, API tokens, fleet tasks, and audit logs with clear boundaries between personal and shared resources.
Meter AI model usage and TURN relay traffic, with plan allowances, prepaid and postpaid billing, or cost-only reporting for private deployments.
Manager instances behind a load balancer share PostgreSQL and Redis, keeping authentication, sessions, and task state consistent as a deployment grows.
A thin-host, central-brain architecture keeps evidence collection and approved execution on the device while model access, orchestration, policy decisions, and auditing remain centralized.
Understands operational intent and suggests commands in the terminal. Suggestions are inserted for review and never run automatically.
Interactive diagnosis can optionally submit a screenshot to a compatible vision model alongside system evidence. Device owners inspect and confirm each command, while cross-device work uses administrator-defined templates.
Connect multiple model services and models through one gateway. Individuals and organizations can choose their defaults and track usage per model.
AI usage policy controls plus full operation auditing for enterprise compliance and traceability.
A production UMDF / IddCx virtual display driver with an exclusive mode that migrates physical screens to the virtual one.
The system service owns signaling and WebRTC connections while desktop workers focus on capture, encoding, and input, allowing desktop sessions to restart without dropping the browser connection.
Local signaling, remote signaling, Manager, and browser connections each use distinct credentials that cannot be mixed.
The Windows build and media path include the X264, VP8, and VP9 capabilities needed for predictable deployment across environments.
A single binary adapts from a portable single host to distributed services via --startup-mode.
Portable mode: one process runs signaling + desk + WebRTC + capture.
Signaling server only.
Desk server only.
Runs as a Windows service, owns signaling and WebRTC connections, and manages workers for desktop sessions.
Handles capture, encoding, system audio, and input inside the user desktop session without owning the WebRTC peer connection.
No install; control straight from the browser with session-cookie auth.
Controller and host support, plus a SYSTEM service for UAC and logon-screen capture, multiple sessions, and virtual displays.
Controller and host support with ScreenCaptureKit screen and system-audio capture, remote input, and privacy screen.
Controller and host support across X11 and Wayland, with system-audio capture through ALSA or PipeWire.
Both controller and host roles: screen share, input, file management and two-way audio.
Controller only: start remote control anywhere (iOS cannot act as a host).
Onboard devices and dispatch remote tasks at scale with unified authentication, auditing, and policy.
The Windows service mode spans logon screens and sessions for unattended remote access.
A local user can generate a one-time assistance code without creating another account. The session is bounded by device permissions and on-site approval; operations that were not pre-approved require local confirmation, and the connection ends when the code expires or assistance is stopped.
TURN relaying establishes stable connections across complex networks.
Personal and organization views coexist on the same public instance. Private deployments use the same codebase, configured for internal networking, controlled registration, and administrator-issued accounts.
Use the service without hosting a signaling server. Devices connect to the Manager domain, with a streamlined interface for personal use.
Create or join an organization to manage members, authorization, and shared resources. Personal and organization views coexist on the same instance.
Run the same system on an internal network and configure registration, accounts, and connectivity for private use without maintaining a separate branch.