RealVNC offline licensing is the Enterprise option that licenses RealVNC Server without RealVNC’s cloud service. Every remote device on which RealVNC Server is installed must be licensed.[1] By default this is done online: the server joins the customer’s RealVNC Connect Team, either by signing in at the desk or, where the subscription includes mass deployment, by deploying a cloud connectivity token.[1] Most subscriptions are licensed online, so RealVNC Viewer and RealVNC Server must be connected to the Internet. Only Enterprise subscriptions include offline licensing.[2] Catalog: Every remote device running RealVNC Server must be licensed; Offline licensing is available only with Enterprise.
Editions
| Licensing route | Plans | Connectivity | Renewal |
|---|---|---|---|
| Cloud licensing (Team) | Default for most subscriptions[2] | Cloud; direct (LAN) on Premium and Enterprise[11] | Automatic relicensing[1] |
| Offline licence | Enterprise only[2] | Direct only[2] | Updated licence applied manually to every server[2] |
| Cloud licensing with cloud connections disabled | Enterprise[5] | Direct only, by policy | Automatic, if the server stays online[5] |
| On-Prem Management Console | Enterprise[7] | Self-hosted, no Internet needed[7] | New licence key imported[7] |
Bulk or remote licensing, whether by cloud connectivity token or by offline licence, is available only with an Enterprise subscription.[1]
Metrics
Offline licensing uses the same Managed Device entitlement as cloud licensing: every remote device running RealVNC Server must be licensed.[1] The On-Prem Management Console shows account-level information, such as licensed device capacity and user numbers. Its licence key covers both the licensed time period and the number of provisioned licences.[7] Installing RealVNC Connect Viewer and signing in does not count as a licensed device.[12]
Counting / floors
Obtaining and applying the licence. The offline licence is on the Deployment page of the RealVNC account, under Device Access. It can be downloaded as a file for the License Wizard, or used directly at the command line (vnclicense -add) or through policy.[2] Catalog: Offline licensing.
Version 6 to version 7. RealVNC 7.x moves from the 25-character offline key to an offline licence file or token, obtained from the same Deployment page. An upgraded offline-licensed server honours the 6.x key until that key expires, but shows a message that licensing has changed. Policy templates need new versions. The MSI property for an offline licence changed from LICENSEKEY to OFFLINELICENSE.[3] Catalog: RealVNC 7 honours a 6.x offline key until it expires.
No phone-home. When offline licensing is used for direct connections over a private network such as a LAN or VPN, neither RealVNC Server nor RealVNC Viewer “phone home”.[4] This is one practical difference from cloud licensing, where RealVNC Server checks its entitlement with RealVNC’s cloud every 24 hours.[8] Because offline-licensed servers do not report to RealVNC, the EULA’s audit clause (see RealVNC EULA and subscription terms) is in practice the vendor’s main compliance tool for these estates, and the customer’s own deployment records are the evidence. Catalog: Cloud-licensed servers check entitlement every 24 hours.
Virtualization & partitioning
With offline licensing or Virtual Mode in the subscription, RealVNC Server can run in User Mode or Virtual Mode instead of the default Service Mode. Only direct connectivity is available in these modes.[6] RealVNC counts them on trust. The subscription’s capacity sets how many remote computers may run RealVNC Connect, and the customer should run User Mode on no more than that number of computers. It should also run no more than that number of Virtual Mode instances at once, across one or more Linux computers.[6] Each running virtual desktop therefore uses one unit of device capacity, even when many run on one host. Online relicensing applies to Service Mode only, so User Mode and Virtual Mode servers still need the offline licence applied.[5] Catalog: User Mode and Virtual Mode servers are counted on trust against capacity.
Cloud / BYOL
Renewal. For cloud-licensed servers, RealVNC handles relicensing automatically when the subscription renews.[1] Renewals and trial-to-paid conversions can take up to 24 hours to activate.[8] Offline-licensed servers need the updated licence applied manually on each renewal, or they lose access.[2] Enterprise customers whose servers stay permanently online can avoid this. They add each computer to the team and then disable cloud connections (the AllowCloudRfb parameter). Relicensing then stays automatic while users cannot make cloud connections.[5] Catalog: Offline licences must be re-applied after each renewal.
Lapse. Remote access stops as soon as a subscription expires. If the customer renews within a further 28 days, RealVNC restores the team and connectivity. After 28 days the RealVNC Servers have to be re-joined to a team.[9] Catalog: Access stops at expiry; the team is restored if renewed within 28 days.
On-Prem Management Console. The On-Prem Management Console is the core of RealVNC Connect On-Prem: a self-hosted, browser-based console for an offline deployment that needs no Internet access to set up or run. It is available with Enterprise, and access is arranged through the account manager.[7] It is renewed by importing a new licence key from the RealVNC Connect Portal. At renewal the customer can create an encrypted export file of high-level usage data, which RealVNC uses to size the renewal package and prevent licence abuse. RealVNC says this export does not track activity within sessions.[7] The pricing page lists the console as an add-on for Enterprise.[11] Catalog: On-Prem Management Console is Enterprise only; usage export at renewal.
Viewer for offline use. From RealVNC Connect Viewer 8.4.0, signing in to an account is part of the Viewer. Customers on Premium or Enterprise plans that need offline licensing can download RealVNC Classic Viewer (v7) from the RealVNC Portal.[12]
Programs
Version lifecycle
The current version of RealVNC Connect 7 and 8 receives product support, critical fixes, security updates and non-security updates. The previous two minor public releases receive product support only.[10] Support for RealVNC Connect 6 ended on 2025-03-31, and new RealVNC Connect 6 licence keys are not routinely issued. Support for VNC 5.x ended on 2022-10-03.[10] For offline or air-gapped environments, RealVNC recommends the On-Premise Management Console, which works with Viewer 8.3.0 or later and RealVNC Server 7.15.0 or later.[10] Estates still running offline-licensed version 6 servers are therefore relying on keys that will not be routinely replaced. Catalog: RealVNC Connect 6 is out of support and new 6.x keys are not routinely issued.
Out of scope
- On-Prem Zone and certificate configuration, which are technical rather than licensing topics.
- Enterprise contract terms agreed in writing, which can override the web limits.