We didn’t want to build RemtoteToPC on old legacy technology. Our core tunneling, and monitoring software is our own proprietary technology. We designed it from the ground up to be lean, reliable, fast, efficient, and scalable. User experience, consistency and reliability are very important to us. We work hard and will continue to work hard on making RemoteToPC as excellent as we can.
RemoteToPC uses proprietary ICEngine tunneling technology to negotiate the fastest available 256-BIT AES connection between two peer computers. After approval has been obtained from the HOST computer to accept a connection request from the JOIN computer, an encrypted and secure connection is established between the two peer computers. At that point, the RemoteToPC join side program invokes our remote desktop viewer application.
RemoteToPC also includes our proprietary monitoring technology that allows for a low impact monitoring of system health and metrics to be displayed on our Command Center page for each computer that it is installed on, and also provides the information related to system health alerts.
Our use of Virtual Network Computing (VNC)
RemoteToPC has a host side shell program which uses fork and exec to invoke a VNC program. The Windows version of RemoteToPC currently uses the TightVNC plug-in program, a free GPL-licensed, remote control software package derived from the popular VNC software. The binaries of TightVNC are unmodified and are included in the RemoteToPC installation software. RemoteToPC contains no internal dependencies on TightVNC.
Note that the Terms of Service for RemoteToPC includes two licenses. A separate license for the proprietary RemoteToPC shell program and other binaries and a second license, the GNU GENERAL PUBLIC LICENSE for the distributed binary of VNC. When you install RemoteToPC for Windows you must accept both the RemoteToPC license and the GPL for TightVNC.