Plastic SCM is a cross-platform commercial distributed version control tool developed by Códice Software Inc. It is available for Microsoft Windows, Mac OS X, Linux, and other operating systems. It includes a command-line tool, native GUIs, diff and merge tool and integration with a number of IDEs. It is a full version control stack not based on Git (although it can communicate with it). Features Plastic SCM is a full version control stack platform. It includes these components: Server Command line client GUIs Diff and merge tools Web GUI Web-based admin interface Some of its features include: Support for heavy branching and merging: According to its creators, Plastic can handle unlimited branching and complex merge scenarios Visual Branch Explorer: A timeline to represent branches, merges and changes in repositories, implemented in all of its GUIs ACL-based security: Every object in the system can be secured with access control lists Built-in 3-way merge and side-by-side diff including language-aware support and history of a specific method or function Directory versioning and support for versioning renames Revision history for branched, renamed, moved, copied, and deleted files Blame/Annotate Centralized operation (SVN/Perforce style) Distributed operation (Git/Mercurial style) Atomic commits—the server assures that changesets are committed in the repository entirely Shelving—users can save and restore work in progress for task switching Support for ASCII, Unicode, binary, symbolic link (on Unix), Mac-specific, and UTF-16 files Support for Mac OS X, Windows and Linux platforms Server-side and client-side event triggers High-latency network support: The network protocol used by Plastic is optimized for high-speed/high-latency networks Gluon: GUI and workflow for non-developers (specially focused on game development) Locking: Binary files and assets that can't be merged can use locking instead of branching/merging Design Plastic is a client/server system although in current terms of version control it can also be defined as a distributed revision control system, due to its ability to have very lightweight servers on the developer computer and push and pull branches between servers (similar to what Git and Mercurial do). Developers work on files in their client workspaces, and check in changed files together in changesets. Storage Plastic SCM has 2 different families of storage for all its data and metadata: Jet: An ad-hoc storage designed for high-performance, released with version 6.0. It is now the default storage. Relational databases: Traditionally Plastic supported storing all data and metadata in relational databases: MySQL, SQL Server, SQLite, SQL Server