Free remote access tools: what they cover and where they stop

What free actually covers

The free options fall into two groups, and they behave differently. Built-in operating system tools are properly free and unlimited: Quick Assist on Windows for attended help, Remote Desktop on supported Windows editions for full sessions, screen sharing on macOS, VNC and SSH on Linux. There is no licence to breach and no session timer. What you lose is everything around the session: no cross-platform console, no device list, no unattended agent for machines outside your network, no session log, and no traversal of home routers or corporate firewalls without a VPN.

Personal tiers of commercial products are the opposite shape. They give you the polished experience, easy connection through firewalls and often some unattended capability, but they are licensed for personal, non-commercial use, and vendors enforce that with commercial-use detection, session duration limits and device caps. A blocked or truncated session in the middle of a paid repair is the usual way people discover the line.

The five limits that end up costing money

Every team that outgrows free does so for the same reasons, in roughly this order.

• Licensing: personal tiers are not licensed for business support, and detection interrupts work at the worst moment.
• Unattended access: free tools generally need someone present at the far end, which rules out servers, kiosks, tills and out-of-hours work.
• Audit: no operator-attributable session log means you cannot answer who connected to what and when, which fails supplier questionnaires, insurance requirements and any regulated-sector policy.
• Network reach: built-in tools need a VPN or a forwarded port to reach a device outside your network, and port forwarding remote access to the internet is a documented route to compromise.
• Support and reliability: when a critical session will not open, there is nobody to escalate to, and the cost lands on whoever is waiting.

The mistake to avoid entirely

The commonest way free remote access becomes expensive is exposing RDP or VNC directly to the internet, usually by forwarding a port on a router so a machine can be reached from outside. Internet-facing remote access services are scanned continuously and are a well-documented initial access route for ransomware; national guidance from the NCSC and CISA is consistent that they should not be exposed directly.

If you must use built-in tools across networks, put them behind a VPN or a zero-trust access broker rather than a forwarded port, restrict by source where you can, enforce multi-factor authentication on the accounts involved, and keep the systems patched. If that infrastructure does not exist and nobody has time to build it, a licensed tool with outbound-only agents is the cheaper answer, because it removes the exposure rather than managing it.

When free is the right answer

There is no virtue in over-buying. Free is genuinely the right choice in several situations, and saying so makes the rest of this page credible.

Helping a relative with a laptop occasionally: Quick Assist or a personal tier is ideal. A single-site office where every machine is on one LAN and staff are always present: built-in tools plus a VPN you already run may be enough. A one-off migration or a lab where sessions are attended and nothing is billed: free is fine. Evaluating whether remote support helps at all before spending anything: start free, then measure.

The trigger to move is not a feature you covet. It is the third time a job stalls because nobody was at the far end, or the first time somebody asks for a log of who connected to a machine.

Costing the workaround

Put a number on the gap before deciding. Count the hours lost in a typical month to the five limits above: waiting for a user to be available so a session can start, journeys to machines that could have been reached, sessions cut short, time spent maintaining a VPN or jump host purely for support access, and time spent reconstructing what happened after an incident with no session log.

Multiply by a realistic hourly cost. For most teams the total passes the price of a licence somewhere around two hours a month, and any team supporting devices they own passes it comfortably. That calculation, rather than a feature comparison, is what makes the decision straightforward in either direction.