Alternatives to Concurrent Versions System

Darcs suits teams wanting distributed, offline, patch-based version control with selective changes and email-based collaboration.

GitUI suits people who prefer keyboard-driven Git work in a terminal and want file-, hunk-, or line-level change controls.

Gitnuro

Gitnuro suits newcomers and experienced users looking for a desktop Git client on Linux, macOS, or Windows.

Unity Version Control

It suits game development teams that need source control for large repositories, binaries or artist workflows.

It suits Android developers who want to add accessibility checks to automated app tests.

GitButler

GitButler suits developers who want to manage parallel or stacked Git branches and edit commits in a desktop client or CLI.

Apache Subversion

It suits teams that want centralized version control with atomic commits, optional locking and server choices based on Apache HTTP Server or svnserve.

Fossil suits software projects that want distributed version control alongside built-in project tools.

BitKeeper may suit teams managing large or commercial software projects that want distributed versioning and native large-file handling.

GitBreeze suits software engineers who want a graphical Git client with commit review and branch comparison while retaining the option to use the command line.

Gitember suits developers who want a visual Git client across desktop platforms, including those who work offline with local repositories.

It suits developers comfortable with Emacs and Git who want daily version-control tasks inside Emacs.

StarTeam may suit distributed development teams needing centralized versioning and integrated change, defect, requirements and project management.

GitQlient suits people who want an offline Git client with repository history, submodule support, and GitHub or GitLab integration.

It suits teams hosting Subversion repositories on Windows, including organizations that need repository search, replication, backup, and access controls.