Remote Access

Remote Access in Breeze includes interactive desktop control, browser terminal sessions, and managed file transfer, all from a single web interface with nothing to install on the technician side. Unlike most open-source RMMs, Breeze does not bolt on a separate MeshCentral instance for remote control; desktop, terminal, and file transfer all run natively on the same Breeze agent. Every session is permission-gated and MFA-protected.

Remote Desktop and Terminal

Desktop and terminal sessions use WebRTC as the primary transport with signaling handled by the Breeze server. If peer negotiation fails in constrained network conditions, the viewer can fall back to a WebSocket relay mode with reduced capabilities, so a technician keeps a working session even behind restrictive firewalls or symmetric NAT.

Terminal sessions are full PTY sessions rendered in-browser, supporting interactive shell behavior and resize-aware terminal state, the same experience as a local terminal without exposing SSH or RDP to the network.

Session Types and States

Remote Access supports three session types from one console: interactive desktop control, an in-browser PTY terminal, and managed file transfer. Each session moves through five tracked states across its lifecycle, so technicians and auditors can see exactly when a session opened, what it was doing, and when it closed.

File Transfer Workflow

File transfer supports both pull and push operations with status tracking (pending, transferring, completed, failed) and progress visibility. Transfers can be cancelled while active, and the 500 MB per-transfer ceiling keeps a single operation from saturating an endpoint’s link.

Security and Session Governance

Remote access enforces:

• MFA checks before session creation
• role-based permission checks (remote:access)
• audit logging for every session lifecycle transition
• organization and user-level concurrency limits (up to five concurrent sessions per user)

This model keeps remote operations usable for technicians while preserving strong session governance. For workflows that should not require a human at all, the AI operator can run the same actions under the risk engine you control, and privileged credentials stay vaulted behind Privileged Access Management.

How Remote Access Fits the Platform

Remote Access is one lever among many. Most routine work never needs a live session at all: Scripts and Automation handle repetitive fixes across the fleet, and when you do need eyes on a device, you can approve and launch a session from anywhere with the mobile app. Remote Access is there for the exceptions a technician has to drive by hand.