The cloud version control
scaled up for game development

Forget any limits. Get 100 GB for $19.95 team/month

Subscribe NOW! View Pricing...

What is plastic cloud?

It is a cloud version control server based on the Plastic SCM server core.

It allows you to host your Plastic SCM repositories online and forget about server maintenance and upgrades.

It is the solution for distributed organizations to securely collaborate on their Plastic SCM repositories without having to run their own public servers.

Plastic Cloud adds the ability to create cloud users and groups to define the security and access to the repositories.

What can your team do with Plastic Cloud?

Handle large projects & huge files

Plastic SCM is designed to handle huge files and very large projects, something key in any game development. Large files are not a patch to the original design but a goal from day one.
Your team’s Plastic SCM server can store large files locally, and of course, Plastic Cloud can handle them too.
You can start with 100 GB of cloud space and continue growing in 50GB steps.

Encrypt your data for cloud security

Every game asset and source code file can be encrypted locally before sending it to Plastic Cloud.
This means than even if the cloud storage were compromised, your data would still be safe since you’re the only key holder.

Transfer data faster to the cloud!

In Plastic Cloud you can select the datacenter where your source code and assets are stored. In this way network latency is kept down to the minimum, ensuring you get the maximum data transfer speed.

Use specific tools & workflows for artists

Artists can take advantage of Plastic Gluon, a specific user interface designed for them.
Then they can simply checkin to the cloud, without intermediate repos, without push & pull, just focusing on their designs.
They will also use locking to prevent assets to be wrongly modified in parallel, which is a pain with unmergeable files.

Take advantage of full DVCS for coders

And programmers will benefit from the full Plastic SCM distributed features plus super strong branching and merging.

We know game development involves different roles and abilities, and we have adapted Plastic SCM accordingly.

Store Unity projects in Plastic Cloud

One of the key goals of Plastic Cloud is to simplify collaboration on Unity projects. Big assets, including videos, animations and art, end up collapsing other cloud version control systems. That’s why Plastic Cloud exists.
You can use the Plastic SCM Unity plugin to directly checkin to Plastic Cloud using "Gluon mode". Or you can push/pull from your local Plastic repo to share your changes with your team.

Work in the cloud and... use the best tools

Plastic SCM includes the best version control tools and GUIs you can think of.

The Plastic SCM GUI on Windows

Visit our gallery for more screenshots.
Check other tools to find why we say ours are better ;-)

How do you encrypt all the data that goes to the cloud?

It is very simple:

  • You’ll set up a cryptedservers.conf file on your server (your team server or just your laptops).
  • Each time you have to upload data to the cloud it will be encrypted on your server.
  • Each time you download from the cloud, it will be decrypted on your server.
  • This way even in the event of someone breaking into our cloud servers, your data will be secure since you’ll be the only one with the key to decrypt it.

  • Learn More...

What do you need to use Plastic Cloud?

Besides a Plastic Cloud subscription (which includes the cloud server plus storage) you need a valid Plastic SCM license to use Plastic Cloud. This is because you need the actual client tools (GUIs, integrations with IDEs, merge, and so on) which come with Team, Enterprise, Personal or Community Editions. Find more details in the FAQ.

Then, there are different setups you can use with Plastic Cloud:

  1. Direct checkin to Plastic Cloud with Plastic Gluon.

    Direct checkin will be the workflow typically used by artists in game development and team members who don’t work in code but documents, plans and so on.

    Keys in their daily workflow:
    • They just modify and checkin. They never merge. They lock files to avoid concurrent changes (on files that are unmergeable).
    • They work on a single branch.
    • They use Gluon.

    They can now simply continue using Plastic Gluon and checkin directly to Plastic Cloud.

    Requirements:
    • Plastic Gluon installed.
    • A valid license of Plastic SCM – Team/Enterprise/Personal or Community Edition.
    • A Plastic Cloud subscription.
  2. Distributed developers

    Each developer works on his machine, from his home office. They both belong to the same Plastic Cloud organization and deliver changes to Plastic Cloud through push/pull. Each of them has his own local Plastic SCM repo (or collection of repositories) so that checkins are always local and blazing fast.

    Keys in their daily workflow:
    • They checkin locally and then push when they’re done.
    • They pull each other’s branches from Plastic Cloud and then one of them merges locally.
    • Then he pushes the merged branches back to Plastic Cloud.

    Remark: Plastic Cloud doesn’t allow merges, just checkin or push/pull. That’s why the two developers need their own local repositories (and a tiny Plastic SCM server on their laptops to host them). The reason why direct checkin is not allowed is performance. We don’t want Plastic Cloud to move programmers back to SVN days when each checkin was delayed by slow networks. You checkin locally, and just push to Plastic Cloud.

    Requirements:
    • Plastic SCM licenses for each of them. It can be a Team Edition for business teams or a Community Edition for eligible open source and non-profit organizations.
    • Plastic SCM servers running on the laptops (a simple SQLite backed Plastic server will do).
    • A Plastic Cloud subscription.
  3. Organizations with distributed teams and on-premise Plastic SCM servers.

    The members of each team directly checkin or push/pull to their own team server. Then team servers are synchronized using Plastic Cloud as rendezvous point, instead of requiring one of the servers to be accessible through the internet.

    Keys in their daily workflow:
    • Team members use all the possible combinations: direct checkin to their local server or distributed development with push/pull.
    • There can be distributed developers working from home, doing push/pull to the cloud.
    • The team can use all possible options: Gluon, Plastic on different platforms, centralized, distributed...

    Remark: developers will not use Plastic Cloud as a “regular” Plastic SCM server. Plastic Cloud doesn’t allow merges, just checkin or push/pull. That’s why an on-premise server or a local distributed one is required.

    Requirements:
    • Plastic SCM licenses for the entire team (it can be Team or Enterprise Editions for commercial teams and Community Edition for eligible open source and non-profit organizations).
    • Plastic SCM servers running on the team servers.
    • Plastic SCM server running on the distributed developer laptop (a simple SQLite backed Plastic server will do).
    • A Plastic Cloud subscription.

How do you use the plastic cloud server?

Using the Plastic Cloud server is just like using a regular Plastic server. The only extra step is that we added an extra layer on it: organizations. An organization is a way to group repositories for a given team or company.

Steps to work with Plastic Cloud:

  1. Request an “organization” - a new organization will be created and you’ll be given access to it using your plasticscm.com account. Note: The organization creation will be handled by the Plastic team, but the goal is to let users create their own organizations.
  2. Login and invite team members: login to cloud.plasticscm.com, access your organization and invite other team members.
  3. Create a profile to access the cloud server:

    Please note that we’re using robotmaker@cloud as the server name, where robotmaker is your organization name.

    This is actually the only change to keep in mind while using the cloud server. Normally you use servers like myserver:8087, but in the cloud you use <org_name>@cloud, no need to specify the address or the port.
    By the way, all commands work using organizations at the cloud: you can try

    cm lrep <org_name>@cloud
    to list your repos.

  4. Create a repository as you would do with your regular Plastic server but... in the cloud!
    :-)
  5. Just use it as a regular server: push, pull, configure permissions and so on.
    Read the Plastic Cloud guide for more information