Type Private Website www.teradici.com | Number of employees 200+ Founded 2004 | |
 | ||
Products PCoIP Protocol, PCoIP Zero Client SOC, PCoIP Workstation 1:1 Host SOC, APEX 2800 Server Offload, PCoIP Management Console Founders Dan Cordingley, Dave Hobbs, Maher Fahmi, Ken Unger Profiles | ||
Teradici is a privately held software company founded in 2004, with head offices in Metropolitan Vancouver, BC and Santa Clara, CA. Teradici initially developed a protocol (PCoIP) for compressing and decompressing images and sound when remotely accessing blade servers, and implemented it in hardware. Later, this technology was expanded to thin clients/zero clients for general Virtual Desktop Infrastructure. Teradici's protocol and/or hardware is used by HP, Dell-Wyse, Amulet Hotkey, Samsung, Amazon Web Services, Fujitsu, and VMware.
Contents
History
Teradici was founded in 2004 by Dan Cordingley, Dave Hobbs, Ken Unger and Maher Fahmi. It operated in stealth mode until 2007 when they announced their first products, a blade server card and a small hockey puck shaped client, utilizing a Teradici-designed chip which implemented the PCoIP protocol. In 2008, VMware announced it was licensing Teradici's PCoIP protocol. Teradici developed a software implementation of PCoIP, which VMware started shipping in VMware View 4.
The Teradici name originated from a previous company the founders were incubating. That company's product involved a 100-gigabit datacenter networking device. One-tenth of a tera is a deci, but "Teradeci" didn't roll off the tongue. "Teradici" was unique, sounded better and the domain name was available at the time.
PCoIP Protocol
PC-over-IP (PCoIP) is a proprietary remote display protocol developed by Teradici. The protocol is available in hardware and in software. In 2008, VMware licensed Teradici's PCoIP protocol, and supports it in VMware Horizon View. In 2013 Amazon licensed the PCoIP protocol for use in AWS Amazon Workspaces.
PCoIP is a UDP based protocol that is host rendered, multi-codec and dynamically adaptive. Images rendered on the server are captured as pixels, compressed and encoded and then sent to the client for decryption and decompression. Depending on the image, different codecs are used to encode the pixels sent since techniques to compress video images differ in effectiveness compared to those for text. The protocol also dynamically adapts its encoding based on the available bandwidth. In low bandwidth environments it utilizes lossy compression where a highly compressed image is quickly delivered, followed by additional data to refine that image, a process termed "build to perceptually lossless". The default is to use lossless compression which is used when there is minimal network congestion or when explicitly configured, as might be required for scenarios where image fidelity is more important than conserving bandwidth, e.g. for medical imaging.