Licensing options for the VNC SDK
Devices that use the VNC SDK are sold and supported in a wide variety of ways. Some manufacturers closely track and support their devices in the field, while others have no further engagement once sold.
In order to support these different business models, we offer a range of licensing options designed to, cost-effectively, meet individual requirements. The three options below reflect the most common connection scenarios for VNC SDK, but if these options do not meet your needs, we are always happy to discuss other licensing scenarios.
The VNC SDK has three common connection scenarios
- Cloud-in-a-Box connection
Partners that wish to use their own private cloud infrastructure to establish connections with their devices in the field should choose the Cloud-in-a-Box connection option. With this scenario, the RealVNC cloud infrastructure is installed on a private network and managed entirely by the partner. If you are interested in Cloud-in-a-Box option, you’ll need to get in touch with us to discuss your configuration before we can provide specific license costs.
- Direct TCP connection
Partners that wish to create direct network connections with their devices in the field should choose the Direct TCP connection option. With this scenario, devices are connected peer-to-peer without establishing connections through a cloud infrastructure. If you are interested in the Direct TCP connection option, you’ll need to get in touch with us to discuss your configuration before we can provide specific license costs.
- Brokered connection
Partners that wish to use the RealVNC cloud infrastructure to broker connections with their devices in the field should choose the Brokered connection option. With this scenario, RealVNC will broker a peer-to-peer connection with your devices using our service infrastructure. Below you will find list pricing for the Brokered connection option with “Managed” and “Unmanaged” deployment models. See details below.
Brokered connection licensing for the VNC SDK
In a Managed deployment, the partner maintains an active relationship with the devices deployed in the field. The partner knows where the devices are and typically assists with the ongoing maintenance and service of these devices.
|Concurrent Sessions||£ per Month||Max Devices|
|1 to 2||£150||5,000|
|3 to 5||£250||7,500|
|6 to 9||£400||10,000|
|10 to 15||£600||15,000|
|16 to 20||£800||20,000|
|21 to 30||£1,000||25,000|
|31 to 50||£1,400||50,000|
Unmanaged deployment model
In an Unmanaged deployment, the partner has no further contact with the device once deployed in the field. The end user typically uses the remote access capability integrated into the partner’s device.
|Devices||£ per Month|
|1 to 500||£275|
|501 to 1000||£500|
|1001 to 2000||£1,000|
|2001 to 3000||£2,000|
|3001 to 4000||£3,000|
|4001 to 5000||£4,000|
|5001 to 10000||£5,000|