Collaborate more efficiently
Unity Plastic SCM is a version control and source code management tool built to improve team collaboration and scalability with any engine. It offers optimized workflows for artists and programmers, as well as superior speed working with large files and binaries.
Work distributed, centralized or both
Developers can work either centralized or distributed with a full branching and merging solution. File-based workflows and an intuitive UI make access more intuitive for artists.
Manage large files with speed
Plastic supports big files, huge repos and projects of any complexity. With faster, WAN-optimized data transfers, your distributed team can collaborate quickly and confidently.
Supports any engine
Unlock new levels of productivity within Unity or use Plastic SCM with any other engine – it just works.
“Plastic can handle large files and repositories. The visual branch manager is excellent; our graphic designers can use it with ease. It’s easy to give an external person limited access to certain projects.”
“Plastic SCM manages art assets particularly well. The speed of pulling and pushing sizable repos is impressive, and the system is considerably faster than our previous solution. The UI is intuitive for both developers and artists.”
“Plastic SCM allowed our entire team, including the less technical members, to create and merge branches. The awesome Plastic SCM UI allows everyone to see what’s happening, merge between branches, and coordinate their check-ins with ease.”
“Where Plastic SCM excels for us is branches and merging. We have done some really, really huge merges over the years – the kind of merges that you would have ended up having to do by hand with other tools. It just works.”
Pricing
Your first three users and 5GB of monthly data storage are free. After that, pricing depends on your monthly active users and total cloud storage. See the table below for full pricing.
For on-prem solutions, please contact sales about Plastic Enterprise edition.
Learn more
Version control for games
Learn how to get started with Plastic SCM, and start tracking changes for your game project in Unity.
Project organization and VCS best practices
Learn the key concepts of version control as well as tips and tricks you can use when setting up your Unity project to help ensure team collaboration is smooth and efficient.
Avoid hidden productivity costs
We’ve collected insights from our product and engineering teams on three of the most common version control pitfalls holding studios back from doing what they do best: creating.
Collaboration at KO_OP
How does a worker-owned cooperative studio get both artists and engineers aligned on a production process? Read how KO_OP redefined their workflow with Plastic SCM.
Manage the growing scope of your project
Read how Sycoforge leveraged Unity tools to manage the growing scope of their project and integrate player feedback for rapid, iterative game development.
Ensuring everyone and everything is in sync
Read how Unknown Worlds chose Unity and Plastic SCM to help bring Subnautica to life.
Frequently asked questions
No, you can combine Plastic with almost any other software in your stack to unlock a powerful VCS. However, the Plastic package for Unity makes using Plastic within the core engine extra intuitive.
To begin using Plastic, you just need to sign up for the service using your Unity account. You can find a helpful guide for getting started in the Unity editor or another engine here. If you have more questions before you get started, please feel free to contact us.
Plastic SCM Cloud Edition is a hosted, multi-tenant, cloud-based Plastic SCM server that organizations can use to store their Plastic SCM repositories in the cloud. Learn more
Plastic SCM Cloud Edition is version control for game development teams working with large repositories and files who only need a Cloud server (and optional local cloned repos). You can push/pull (or directly check in) to a cloud server. Cloud Edition includes a Plastic SCM client and the cloud service.
You’ll need a Plastic Cloud Edition subscription to store your repositories in the Plastic SCM hosted service.
No.
You push your data from your local Plastic SCM server to Plastic Cloud.
Yes, you can check in and merge directly to the cloud.
Yes, you can. You can also configure the files that will be locked on checkout from your Plastic Cloud organization’s dashboard.
You need 5.4.16.719 or higher. Our network API was updated and expanded for Plastic Cloud, so older versions will not work.
Plastic SCM can encrypt your code and data before uploading it to Plastic Cloud. When you request a new Plastic Cloud organization to host your repositories, you can set it as “encrypted”. This means that whenever you upload data to it, Plastic Cloud requires data encryption.
Plastic Cloud only allows SSL connections.
Plastic SCM Cloud Edition includes a free tier with three free active users and 5GB of storage. After the fourth user, you pay monthly per active user. If a user is not active during a month, you are not billed for that user that month. If you exceed 5GB of storage, you pay for extra storage per team, not per user. See pricing for details.
Yes. For licensing purposes, we only count the number of active users, regardless of the number of devices used or the number of servers installed.
No. For licensing purposes, we only count the number of active users, regardless of the number of devices used or the number of servers installed.
No. A user is considered read-only when they do not perform write operations, such as a check in.
Yes. You can activate and deactivate users any time you want. Plastic SCM keeps the history of every user, active or deactivated. A user must be active to access the system.
- Support response in less than 24 hours by email
- Remote support connection to solve more complex problems
- Priority for code “hotfixes” from the development team
Learn more here.
A user is considered active when they do any of the following in a given month:
1. Write to a repository to:
- Check in
- Do a code review
- Create an object like a label, changeset (push or checkin), branch, attribute or repo
2. Upload or download 5MB of data.