story · cambridge, england · 1994 to today
RealVNC was founded in 2002 by the team that created VNC.
VNC began at the Olivetti Research Laboratory in Cambridge in the mid-1990s and was released as open source in 1998. When AT&T closed the Cambridge lab in 2002, members of the original VNC team founded RealVNC Limited to continue the technology commercially.
Explore RealVNC Connect for business remote access. Start a free trial.
A lab in Cambridge
VNC was created at the Olivetti Research Laboratory (ORL) in Cambridge, England, in the mid-1990s.
The team’s answer was to work at the lowest common denominator every device shares: the framebuffer. If you ship pixels and accept keyboard and mouse events, the remote end needs almost no intelligence, and any platform can play either role. That idea became the Remote Framebuffer protocol, RFB, and the software that spoke it became Virtual Network Computing: VNC.
The 1998 open-source release
In 1998 the lab released VNC as open source under the GPL.
Debian’s package history records vnc version 3.3.3r2-19 on April 8, 2002. See the Debian vnc package tracker.
RealVNC’s GitHub account still hosts the GPL-2.0 source of VNC Open 4.1.3, along with the Windows and Java source.
The timeline
| 1994-1997 | VNC developed at ORL in Cambridge; the RFB protocol takes shape. |
|---|---|
| 1998 | VNC released as open source under the GPL; adoption spreads far beyond the lab. |
| 1999 | AT&T acquires ORL in January to create AT&T Laboratories Cambridge. |
| 2001 | TightVNC aims to optimize VNC for slow links. By July its 1.1 release ships a new Tight encoding for low-bandwidth networks. |
| 2002 | In April AT&T announces that the industrially funded part of the Cambridge lab will end. RealVNC’s site describes the company as a new venture founded and staffed by the original AT&T team, with the mission of acting as the focal point for open source VNC. By December, UltraVNC’s site says it used RealVNC as its base and added TightVNC’s cursor handling. |
| 2003 | In May ExpertVNC’s developer announces an install-on-demand version of VNC on the vnc-list mailing list and says he did not alter the RealVNC binaries. See early commercial products that cited VNC. |
| 2004 | TurboVNC begins as a performance-focused companion to VirtualGL, using the TightVNC lineage for responsive 3D and video workloads; TurboVNC source history. |
| 2005 | In April TeamViewer’s About page says the product is based on the VNC project. A December 2005 capture of teamviewer.com/company/ no longer has that line. |
| 2009 | TigerVNC forks from TightVNC to modernize the cross-platform core. |
| 2011 | RFC 6143, written by Tristan Richardson and John Levine of RealVNC Ltd., documents the RFB protocol. |
| 2020s | Wayland reshapes Linux screen capture; wayvnc and portal-based servers carry VNC into the new stack. |
The 2009 open letter founding TigerVNC framed the fork as stewardship: concentrate scattered VNC development, share code and ideas, and keep the cross-platform core moving.
Early commercial products that cited VNC
At least two commercial remote-control products named VNC in their own early pages. The evidence for each is different. For TeamViewer, it is the vendor’s own About page. For ExpertVNC, it is its developer’s mailing-list posts and website, followed by a domain redirect and company announcements. The archive shows what each product said in those early pages. It does not show how much VNC code, if any, later versions kept.
TeamViewer
In April 2005 the About page on teamviewer.com, published by Rossmanith GmbH of Uhingen, said: “TeamViewer is based on the VNC project.” It then pointed readers to UltraVNC, RealVNC, Nullsoft and SourceForge for more on VNC and “other tools that helped us.” A December 2005 capture of teamviewer.com/company/ does not include the sentence. Sources: TeamViewer About page, April 2005 (Internet Archive); teamviewer.com/company/, December 2005 (Internet Archive).
ExpertVNC
In May 2003 Joel Bomgaars announced ExpertVNC on RealVNC’s vnc-list mailing list. He described it as “an enhanced, secure, and firewall-friendly install-on-demand version of VNC”. The June 2003 ExpertVNC home page also called it an install-on-demand version of VNC. Sources: ExpertVNC announcement, May 2003; ExpertVNC home page, June 2003.
In replies on the list, he wrote that RealVNC was released under the GNU GPL, that ExpertVNC’s own scripts and executables were separate files under a separate license, and that he had not altered the RealVNC binaries. Sources: ExpertVNC licensing answer on vnc-list, May 2003; ExpertVNC unaltered-binaries reply on vnc-list, May 2003.
By April 2005, expertvnc.com redirected to networkstreaming.com. A Bomgar page from February 2007 said NetworkStreaming had changed its name to Bomgar. In September 2018 Bomgar announced an agreement to acquire BeyondTrust and said the combined company would operate under the BeyondTrust name. The archive does not show whether ExpertVNC’s code continued into NetworkStreaming’s or Bomgar’s products. Sources: expertvnc.com redirect, April 2005; Bomgar name-change notice, 2007; BeyondTrust press release, September 2018.
The people
Tristan Richardson, Quentin Stafford-Fraser, Kenneth Wood, and Andy Hopper authored the 1998 IEEE Internet Computing paper, Virtual Network Computing (PDF).
RFB’s encoding trade-off
RFC 6143, published in March 2011, describes how RFB encodings trade network bandwidth against client drawing speed and server processing speed. Its raw encoding sends pixel values without compression. See RFC Editor, The Remote Framebuffer Protocol, sections 3 and 7.6.1. For a protocol comparison, see VNC vs RDP.
Where the story goes from here
Explore the projects on the Open Source VNC page or browse the vendor directory.
Open-source VNC suits personal projects and home labs. When your business depends on remote access, RealVNC Connect adds end-to-end encryption, centralized management and commercial support from the team that created VNC.
Last updated on