Red Hat, Cendio AB and TurboVNC maintainers started this fork because RealVNC had focused on their enterprise non-open VNC and no TightVNC update had appeared since 2006. TigerVNC is fully open-source, with development and discussion done via publicly accessible mailing lists and repositories.
TigerVNC focuses on performance and on remote display functionality. It became the default VNC implementation in Fedora shortly after its creation.
A 2010 reviewer found the TigerVNC product "much faster than Vinagre, but not quite as responsive as Remmina".
^Peter Åstrand (2009-02-27). "Open Letter: Leaving TightVNC, Founding TigerVNC". TightVNC mailing list. Retrieved 2014-02-11. Recently, however, it has became clear that the TightVNC project cannot support this development. [...I]n practice, the TightVNC project was forked four years ago, when the /trunk source tree was created. The core TightVNC team mainly work in other branches. No release of TightVNC has been based on the /trunk source code and no real effort on merging the different branches has been done.