TeamWare's largest deployment is inside Sun itself, where (bar a few exceptions) at one point it was the only VCS used. TeamWare has been used to manage Sun's largest source trees, including those for the Solaris operating system and the Java system, but as part of the process of converting those code bases to open source communities, they are being moved to newer revision control systems such as Mercurial.
TeamWare features a number of advanced features not found in earlier version control systems like RCS and CVS. In particular, it features a sophisticated hierarchy of source repositories, and allows atomic updates of multiple files, features found in later version-control systems such as Subversion and Perforce. TeamWare allows distributed development by copying a repository to another which might reside on another machine or network. Developers can then commit changes to the local copy of the repository, periodically integrating accumulated changes in the local repository back into the original repository.
TeamWare is implemented as a layer over the older SCCS system, which is used to track changes to individual files. TeamWare works only by a system of files accessed by client programs (interacting without a server) and most distributed users of a repository access it by means of a mounted networked filesystem such as NFS.
Larry McVoy was the designer of TeamWare. The BitKeeper version control system, also designed by McVoy, shares a number of design concepts with the earlier TeamWare. Evan Adams was the architectural lead for TeamWare.