Parsec streams a computer’s screen with the host GPU’s hardware encoder, which makes it a common choice for remote access to 3D, video and design workstations. The short answer for work use: the free plan and the Individuals (Warp) plan are licensed for personal, non-commercial use only, so a company needs Parsec for Teams or Enterprise. Parsec cannot be self-hosted. The closest option is the High Performance Relay (HPR), a relay server your team runs itself, available only with Enterprise. Facts below were checked on 19 November 2026 against Parsec’s pricing page, changelog and support documentation. Latency, image quality and behaviour on your network are not tested yet.
Parsec for work at a glance
| Item | What the official pages say (checked 19 Nov 2026) |
|---|---|
| Latest app build | 150-105c (8 October 2026), a macOS host fix for H.264 quality on some decoders. Later changelog entries (28 October, 18 November) are Teams console and relay updates. |
| Licence | Shareware (conditionally free). Free and Individuals plans: personal, non-commercial use only. Commercial use: Teams or Enterprise. |
| Hosts | Windows 10/11 (64-bit), Windows Server 2016, macOS 10.15 or later. No Linux hosting. |
| Clients | Windows, macOS, Ubuntu 22.04 desktop, Android, web client in Chromium-based browsers. No iOS or iPadOS, and Safari is not supported. |
| Host hardware | A GPU with a hardware video encoder, with the display connected to that GPU. H.264 minimum: Intel HD 4200, NVIDIA GTX 650 or AMD Radeon HD 7750 class, 4 GB RAM. |
| Network | Encrypted peer-to-peer UDP for the stream, TCP 443 to Parsec’s API, UDP 3478 to Parsec’s STUN servers. Not supported behind double NAT or CGNAT. |
| Accounts | Host and client both sign in to a Parsec account; there is no offline mode. |
| Self-hosting | No self-hosted Parsec server. Enterprise can run its own relay (HPR) on Linux. |
What each plan allows at work
Parsec’s pricing page has four plans: Personal Use (free), Individuals (Warp), Teams and Enterprise. The licensing note under the plan table is the part that matters for IT: the free and Individuals plans cover personal, non-commercial use only, including when you make your own computer available to other people.
What the paid tiers add:
- Individuals (Warp): up to 3 streamed monitors, 4:4:4 colour mode, virtual monitors, privacy mode, Wacom tablet pressure and tilt.
- Teams: everything above, plus an admin panel, SAML single sign-on, team-managed computers and groups, permission rules, guest access for external users and audit logs for the last 7 days.
- Enterprise: adds the Teams API, the High Performance Relay, role-based admin access, SCIM provisioning and full audit logs through the API.
The 18 November 2026 changelog entry added a Teams setting, “Allow Hosting on Personal Machines” (App Rules, Security Settings, Super Admins only). When it is off, only managed Team Machines can host, so every host is visible in the admin console. It is on by default.
How a Parsec connection works
Parsec’s connectivity reference describes three kinds of traffic. The app talks to Parsec’s backend over TCP 443 (kessel-api.parsec.app and kessel-ws.parsec.app, plus build and CDN hosts). It contacts Parsec’s STUN servers (stun.parsec.app and stun6.parsec.app) on UDP 3478 to discover public addresses. The video stream then flows peer-to-peer over encrypted UDP between host and client, on ports that are random by default.
Requirements that often trip corporate networks:
- DNS must resolve parsec.app and its subdomains, AWS S3 and CloudFront.
- Firewalls must not decrypt the TLS traffic with SSL inspection.
- Neither host nor client may sit behind double NAT or carrier-grade NAT.
When NAT traversal fails, you can pin the host to a fixed UDP range and forward it. Our Parsec program page covers the setting, network_server_start_port=8000, and the matching UDP 8000-8010 forward, one port per simultaneous guest.
Parsec states its bandwidth needs plainly. For 1080p at 60 fps it recommends 30 Mbps upload on the host over Ethernet, and 30 Mbps download with a ping under 15 ms on the client. For two or more guests on one host it recommends at least 50 Mbps. These are the vendor’s stated requirements, not our measurements.
Is there a self-hosted Parsec? The High Performance Relay
Parsec does not offer an on-premises version of its service: accounts, sign-in and connection brokering always go through Parsec’s API. What Enterprise customers get is the High Performance Relay (HPR), a Linux service you run yourself. It relays many concurrent sessions through one public IP and port, so hosts behind strict firewalls no longer depend on UPnP or public STUN.
HPR v2.0 prerequisites from Parsec’s technical reference:
- Hardware: at least 2 CPU cores, 4 GB RAM and a 1 Gbps NIC. TPM 2.0 is recommended for encrypting the relay secret.
- OS: systemd 250 or newer, which means Ubuntu 24.04 LTS+, Debian 12+, RHEL/Rocky/AlmaLinux 9+, Amazon Linux 2023 or Fedora 36+. Ubuntu 22.04, Debian 11 and EL8 are not supported.
- Network: a public IP with NAT to the relay’s static private IP, public listener on UDP 5000, private STUN listener on UDP 4900, and outbound TCP 443 to kessel-api.parsec.app.
- Placement: two relays per site, in a DMZ close to hosts and clients.
You create the relay in the Teams admin panel, put your Team ID, public IP and encrypted secret into its systemd service, then point hosts at the relay through App Rules. HPR v2.0.2 (18 November 2026) wants 8 MB UDP socket buffers and logs a warning at startup if net.core.rmem_max and net.core.wmem_max are lower:
sudo sysctl -w net.core.rmem_max=8388608
sudo sysctl -w net.core.wmem_max=8388608Parsec vs self-hosted and business alternatives
| Tool | Licence | Self-hosted | Linux host | Fits best |
|---|---|---|---|---|
| Parsec | Shareware; work use needs Teams/Enterprise | Relay only (Enterprise HPR) | No | GPU workstations, colour and pen work, managed teams |
| RustDesk 1.4.9 with RustDesk Server | Free, AGPL-3.0 (Server Pro is paid) | Yes, ID and relay server | Yes | Remote support and unattended access on your own server |
| Sunshine host + Moonlight client | Free, GPL-3.0 | Yes, no account service | Yes (also Windows, macOS, FreeBSD) | Self-hosted game-style streaming from your own machine |
| Splashtop | Shareware; Personal is free only on a home LAN | No (cloud-brokered) | See program page | Business remote access and attended support |
| Chrome Remote Desktop | Free | No (Google account) | Yes, Debian/Ubuntu | Occasional access to a few machines |
Sunshine describes itself on GitHub as a “self-hosted game stream host for Moonlight”. Its latest release is v2026.914.233613 (15 September 2026), and Moonlight’s PC client is at v6.2.0 (4 October 2026). Neither has team management, SSO or audit logs. For a wider self-hosted overview see self-hosted remote access.
Rolling Parsec out to a team
- Confirm the licence first: any work use means Teams or Enterprise seats.
- Check each host: a supported GPU with a hardware encoder, the monitor (or a virtual display) attached to that GPU, current graphics drivers. On hybrid-GPU laptops, error -14003 means the dedicated GPU is not wired to the display, so use the integrated GPU.
- Install hosts with the Per Computer option so Parsec runs at the Windows login screen and can capture UAC prompts.
- Open the firewall paths listed above, and exempt Parsec traffic from SSL inspection.
- In the admin panel, assign Team Computers to users or groups, set App Rules, and decide on “Allow Hosting on Personal Machines”.
Hardening steps that apply to every remote tool are in our remote access security checklist.
Limitations
- No hosting on Linux, and no client for iPhone or iPad.
- No offline or fully on-premises mode: sign-in and brokering need Parsec’s API.
- The host needs a capable GPU, so Parsec is a poor fit for helping users on old office PCs.
- Double NAT and CGNAT are unsupported; without HPR, strict networks may block sessions.
Who Parsec suits, and who it does not
Good fit: studios and design teams that need full-frame-rate access to Windows or macOS workstations or cloud GPU machines, pen-tablet and colour work, and admins who want SSO, assignments and audit logs without running servers.
Poor fit: help desks supporting mixed, low-spec PCs; teams that must host on Linux; organisations that require a fully self-hosted stack. For those, compare RustDesk with its server and the options in our free remote desktop software guide.
FAQ
Is Parsec free for work?
No. Parsec’s pricing page licenses the free and Individuals (Warp) plans for personal, non-commercial use only. Commercial use requires a Teams or Enterprise plan.
Can Parsec be self-hosted?
Not fully. Accounts and connection brokering always run through Parsec’s service. Enterprise customers can run the High Performance Relay on their own Linux server, which keeps relayed traffic and STUN on infrastructure they control.
Is Parsec open source?
No. Parsec is a proprietary product of Unity Technologies, and use is subject to the Unity Terms of Service. Sunshine (host) and Moonlight (client) are GPL-3.0 projects that people often compare with it.
Can Parsec host on Linux?
No. Parsec’s compatibility page says hosting is available only on Windows and macOS. Linux is client-only, packaged for Ubuntu 22.04 desktop.
Does Parsec work on iPhone or iPad?
No. Parsec states that iOS and iPadOS are not supported, including the web client in Safari. Android and Chromium-based browsers are supported as clients.
Last updated: 19 November 2026 · CtrlRemote editorial team. Licence, version and platform details are checked against each developer's official documentation.