I'm Mr. Plastic

Why teams choose Plastic SCM instead of Git

Subversion was the king of version control in terms of adoption in the last decade. For many, it was unthinkable to consider one day it would be gone. Nowadays, Git is the new standard and SVN is long forgotten.

So, why do teams choose Plastic SCM instead of Git? This is the question we answer for teams worldwide on a daily basis.

What makes teams go for Plastic SCM instead of Git?

Large repos and files

Large repos and files

When repos grow really large or projects need to handle big binaries, Git usually falls short. This is one of the key reasons why teams go for Plastic, because they can still implement Git-like workflows but without size limits.

Fine-grained security

Fine-grained security

Security controls and a first-class citizen in Plastic SCM. Every object can be secured with an ACL. This allows companies to enforce best practices and policies that are out of the scope of Git.
Learn more

Centralized development

Centralized development

Local clones are mandatory in Git, by design. In Plastic, you can work distributed (Git-style) but also centralized (SVN-style) and still have all the power of branching and merging. For many companies saving space on each workstation and build server is key.

Game development

Game development

Studios require locking for assets, images, videos, and easy-to-use workflows and tools for artists, while coders still have full branching and merging. Take a look at Gluon and see why Telltale went for Plastic.

And still… full integration with Git

And still... full integration with Git

Plastic SCM speaks the Git protocol. This means you can run Plastic as a GitServer or connect push/pull to any Git service (like GitHub Enterprise) as if it was a Git Client.
Learn more

What else do they like?

On-premise server scalability

On-premise server scalability

Teams with hundreds or even thousands of developers who require an on-premise server need high scalability. Many on-premise Git server solutions are known to scale poorly. That’s why many teams choose Plastic.

Even stronger merging

Even stronger merging

Git's merge engine is awesome. Plastic’s is even better providing full rename tracking which is super useful in refactors.
Find more about our merge engine.

Friendly and powerful toolset

Friendly and powerful toolset

It is all about the tools after all. Plastic comes with side-by-side diff, 3-way merge, code-aware semantic diff, image diffs, high-quality IDE integrations, and easy to use GUIs development by the same core team as a no-no sense solution. Just check out the Branch Explorer. When productivity is at stake, many go for Plastic.

And still… full integration with Git

Count on product experts

Many teams require professional support and that’s something we excel in. We are the product designers, from the bottom up, so we do know each piece of the software and can solve any question you might have. We also listen and rapidly evolve our product adapting it to what our users need. Meet us!

How to learn more

We welcome Git users with a short guide to make them feel at home.
You might also want to attend a webinar.
Take a look at our Gallery to quickly see how Plastic looks and feels.
Read about things that make us unique like Semantic Version Control.

How to migrate Git repos

Quite easy: every Plastic SCM is a Git client by default - just pull from your Git repo.
Optionally, you can use fast-export/import which is also supported.
And, you can even push from Git to a Plastic SCM server enabling the GitServer capability
(available on all Plastic SCM servers).

Get the latest news