In the distributed approach, each developer works directly with their own local repository, and changes are shared between repositories as a separate step.
ArX — started as a fork of GNU arch, but has been completely rewritten.
Bazaar — written in Python. Decentralised, and aims to be fast and easy to use. Can losslessly import Arch archives.
Codeville — written in Python, uses an innovative merging algorithm.
Darcs — written in the Haskell language, can keep track of inter-patch dependencies and automatically rearrange and "cherry-pick" them using a "theory of patches".
DCVS, a decentralized CVS-based version control system for distributed software development.
Fossil - distributed revision control, wiki, and bug-tracking bundled into a stand-alone executable.
Git — Designed by Linus Torvalds based on the needs of the Linux kernel project. Decentralised, and aims to be fast, flexible, and robust.
LibreSource — a real virtual office allowing geographically spread teams to work simultaneously on a common project. LibreSource offers advanced functionality for configuration management with its generic synchronisation module So6, resulting from INRIA research works. The creation of development chains, validation processes and quality control processes can be done through the interconnection of synchronisers.
Mercurial — written in Python. Decentralised and aims to be fast, lightweight, portable, and easy to use.
Plastic SCM - distributed using replication and synchronization. Free for open source projects and education.
Client-server model
In the client-server model, developers use a shared single repository.
Local only
Revision Control System (RCS) — A 1980s source code control system that features separate backward deltas for faster access to the trunk tip compared to SCCS and an improved user interface; the former at the cost of slow branch tip access and missing support for included/excluded deltas.
SCCS1970s — Source code control system which is part of UNIX. The original UNIX program, based on interleaved deltas (and, contrary to common misbelief, not separate forward deltas/diffs); by included and excluded revisions, can construct versions as arbitrary sets of revisions (resp. the deltas associated with them).
CVSNT - A cross-platform port of CVS that allows case insensitive file names among other changes.
OpenCVS - Compatible with CVS, with emphasis put on security and source code correctness.
Subversion (also known as svn) — An open source version control tool started in 2000 to be "a compelling replacement for CVS"[1].
Vesta — A build system with a versioning file system and support for distributed repositories. Used at Intel for microprocessor design.
Proprietary
AccuRev — A fast and easy-to-use SCM tool with integrated issue tracking based on "Streams" that efficiently manages parallel and global development. A replication server is also available.
Aldon — A leading provider of application lifecycle management (ALM) solutions that offer process-driven application change management to IT.
DesignSync — Configuration management system from MatrixOne
Evolution — version management from ionForge. remote access, branching models, customizable workflow, with integrations into development, graphic, and modeling tools.
PDMWorks - Data management solution by the makers of SolidWorks with ERP integration and a Windows Explorer-integrated interface.
Perforce — Built around a client-server architecture. Free for use in open source projects.
Polarion ALM - Web portal application that integrates Subversion (software) as basis for revision control of a wide rage of software development artifacts (documents, tasks, change requests, Wiki pages, etc.) in addition to source code.
Project Overlord Asset/Project Management Software — client/server application designed specifically for CG animation/vfx studios. Gives the ability to track assets as well as different project related data such as shots and tasks.
PureCM — Flexible version control tool that supports parallel and distributed development using a stream-based approach to branching and merging. Complete with integrated issue management.
PVCS — Polytron Version Control System originally developed by Don Kinzer at Polytron, first released in 1985.
SourceAnywhere Hosted — A hosted source control solution. Published by Dynamsoft Corporation.
SourceAnywhere Standalone — A SQL-based source control solution designed to be an alternative of Microsoft Visual SourceSafe. It is for developers who are ready to migrate away from VSS for performance, security, scalability, and reliability. SourceAnywhere Standalone is one product of SourceAnywhere product family published by Dynamsoft Corporation.
SourceHaven — Originally based on Subversion, adds an embedded Oracle database backend and a web application for administration
StarTeam, Borland — A robust platform for coordinating and managing the entire software delivery process, StarTeam promotes team communication and collaboration through centralized control of all of a project's digital assets and activities.
Store, Cincom - A source code management and versioning system for Cincom's Visualworks Smalltalk environment.
Surround SCM — Cross platform SCM tool for teams. Features a workflow capability to track what state changes have been made.
Team Coherence — Integrated Version Control and Bug Tracking.
Telelogic Synergy, an integrated change management (bug tracking) and Task-Based configuration management system (SCC compliant)
Vault — A version control tool by SourceGear designed to supplant Microsoft's VSS revision control software.
Version Manager, ebiexperts — A data based Version Control tool able to smart compare Ms-Office, Xml, Pdf and Business Objects & Crystal Reports Reports and Universes.
Visual SourceSafe, Microsoft — A version control tool provided by Microsoft oriented toward small teams.
Visual Studio Team System, Microsoft — a process-based client-server suite of tools for larger development organizations, incorporating work item tracking, reporting, build automation, unit and web testing, and integration with Microsoft Office