Plastic Cloud extension


Welcome to Plastic Cloud - the Plastic SCM hosted solution.

The purpose of this guide is to help you get up to speed with Plastic Cloud extension and its key concepts.

This guides serves as a walkthrough to get your Plastic repositories (repos) up and running in the cloud.

What is Plastic Cloud

Plastic Cloud is the hosted Plastic SCM server solution.

We have two different Cloud products:

Plastic SCM Team Edition plus Cloud extension
For teams who require an on-premises server (included in Team Edition) and host repositories on the Cloud.
Requirements: Purchase Team Edition and add the Cloud Extension (not Cloud Edition).
This guide documents this version of Plastic Cloud.
Plastic Cloud Edition
This is a different product designed for teams who do not need an on-premises server. The only central location is the Cloud.
Team members can have local clones of the repositories or alternatively work directly connected to the Cloud.
Requirements: Purchase Cloud Edition (not Team + Cloud).

From a user perspective, you will work with Plastic Cloud just as you do with a conventional Plastic SCM server; you will push and pull branches, create repositories, manage permissions, and so on.

Internally, Plastic Cloud uses a fully redesigned Plastic server core. The cloud core runs on several cloud roles instead of just a single computer. This means that it can be horizontally scaled by simply adding more roles (computers).

Plastic Cloud is a multi-tenant and highly scalable solution, capable of handling thousands of different organizations. It makes the best possible use of the underlying cloud infrastructure.

In practice, this means you don't have to worry about server setup or maintenance. We'll handle that for you!


In this guide, we are going to explain how the Cloud extension works.


Who is it for?

There are many scenarios where Plastic Cloud extension fits. Just to mention a few:

  • You are a small team and don't want to handle any infrastructure. You're already running Plastic on your laptops but you don't want to install and administer your own Plastic server. However, you still need a central rendezvous point for the team. Plastic Cloud extension is for you.
  • You are part of a large corporate team working in several locations across the globe. You need a central server but you don't want to depend on your IT group. You can setup a Plastic Cloud organization for you and use it as your hosted central server. You would like to enforce encryption on all the data pushed to the cloud prior to sending it outside your network for maximum security.
  • You are a game development team (or any other team dealing with large repositories and huge files) and you couldn't find a suitable solution with mainstream hosting providers of version control software. Git-based solutions have the well-known 2GB repos limit. If you need more than that, Plastic Cloud is for you.

These are just 3 key scenarios, but there are many more. Some teams asked us to use the Plastic Cloud extension as a live cloud-based backup, and that's certainly an option too.


Create a Plastic Cloud extension organization for your Team Edition

Once you have your Team Edition license, the first thing you need to do to start working with Plastic Cloud extension is to create an organization.

The organization is the way to handle different sets of repositories in the cloud. Inside the organization, you can create as many repositories as you need.

This is how you can create an organization:

  1. Go to your plasticscm.com Cloud dashboard to add the Plastic Cloud extension.

    Or, go to plasticscm.com/cloud and click the Subscribe now! button.

  2. A new page appears where you must enter your subscription and account information plus the following data related to the organization:

    Request a Plastic Cloud organization

    • Organization name - this is the way to identify your repos in the cloud... so choose a cool name.
    • Datacenter - select the data center that is closest to you to improve data transfer speed.
    • Encrypted data - choose if you want your data to be encrypted. Read more about the encrypted data in Plastic Cloud.
  3. The organization will generate and we'll let you know.
  4. You will be able to sign in to the Plastic Cloud :-) and start using it.

Accessing the Plastic Cloud from your Plastic developer GUI

To start working with your cloud organization from Plastic, you must install and configure your Plastic Team Edition.

As a Plastic Team Edition + Cloud extension user, then you must learn how to install and configure your Plastic SCM Team Edition.

When you're ready, you can continue reading this chapter.

Let's see how to access to your cloud server.

  1. Go to the Plastic GUI and open up the Cloud view. You'll see something like this:
    Accessing the Plastic Cloud from your Plastic developer GUI
  2. Just type organization_name@cloud as the server name. In my case, my organization is test. So I should type test@cloud.
  3. Then, click (refresh) (or press the enter key) to access your organization.
  4. You'll be prompted to enter the credentials to access the cloud server:
    Entering the credentials to access the cloud server

    Enter the credentials you used to register at www.plasticscm.com when you purchased your Team Edition license.

    If you choose to remember the credentials for the next time, then a connection profile is created. This way, you won't longer have to enter the credentials.
  5. Then, the list of available repositories appears. Empty! That's because we haven't created any repository in the cloud yet, but we're already connected!
  6. Let's create a repository as we would normally do:
    Creating the first cloud repository
  7. And then our repo list will refresh, this time showing our first cloud repository:
    First cloud repository created

From here on, you will be able to work with this cloud repository normally.

Remark: Check the list of current limitations to learn more about what you can do at this point.

First push to the Cloud

Pushing a branch to the cloud is as simple as pushing it to a regular Plastic SCM server. In my case, I'll do something like:

Push a branch to the cloud

And, my main branch is ready in the Cloud!


Configure the data encryption password from Plastic

When you request a new organization, you can specify that you want to enforce encryption:

Force to encrypt the organization

If that flag is set during the organization creation, Plastic Cloud will only accept encrypted data for this organization.

In this case, your organization uses encrypted data and Plastic will ask you to enter the encryption password to be able to decode the data.

This is how data encryption works:

All data leaving your computer is encrypted prior to being sent to the Cloud. This means it is totally safe and nobody can access it even if the Cloud is compromised. Data is decrypted once downloaded from the Cloud, and only users who know the password will be able to decrypt the data successfully.

Remark: The encryption password must be a well-kept secret in your organization.
Important: If your forget the password, not even we at Plastic SCM can help you recover your data.
Server encryption

Remember that you only have to configure the password once for the organization.

Important: In addition, keep in mind that the password must not be changed. Otherwise, the previously-encrypted data won't be decrypted. So, choose your password wisely.

Learn more about how the encryption works.


Just use organization_name@cloud as the server name everywhere

Just a final tip. Whenever you can use a server name, you can use organization_name@cloud. This means that:

  • You can do something like cm repo list test@cloud from the CLI to list available repos.
  • You can create sync views from your local server to your cloud organization.
  • You can list repos from the GUI and open up its Branch Explorer remotely.
  • You can annotate a file remotely on the cloud server.
  • And much more!

Connecting a workspace to the Cloud

It is possible to directly work with your Cloud repository.

You only have to create a workspace connected to your Cloud repository:

Connect a workspace to cloud

Accessing the Plastic Cloud from Gluon

This chapter explains how to access Plastic Cloud from Gluon, the Plastic SCM version specifically designed for artists and content creators.

To start working with your cloud organization from Gluon, you must install the Plastic client.

Gluon comes as part of the standard Plastic SCM client installer.

If you don't already have the Plastic client installed, then:

  1. Go to our website
  2. Click More installers and other Operating Systems
  3. Choose your operating system
  4. Download the Client installer. You don't need to download the default Full installer which includes the server, which is something most likely you don't need as a Gluon user.
  5. Install Gluon. Installing the client is straightforward and won't take more than 60 seconds. During the installation, you are prompted to select the application that will run when the installation finishes. In our case, Gluon:
    Installing the Plastic client - Select Gluon

Configure Gluon

Since you selected Plastic Gluon to start after the installation finishes, Gluon will start up.

Because Gluon doesn't detect any previous Plastic SCM configuration, the configuration screen will show up:

Gluon configuration

It is very easy to fill in:

  • Server - Just type in the name of your organization followed by @cloud. You will have received an email with the organization that you've been invited to join or the one you've purchased. In my case, I typed test@cloud, since test is the name of my organization.
    You can click Connect to verify that you can correctly connect to your cloud organization.
  • Credentials - Type the email and password you use to login to plasticscm.com.
    You can click Check to verify that you entered the right credentials.
  • Repository - Click Choose... to select the project (a.k.a. repository) that you want to work on. All the repositories in your organization are listed.
  • Workspace - Finally, type the path of the workspace on your computer to host the files you'll be downloading from the cloud.

And you're done! Click Apply to start using Gluon.


Start using Gluon

Once you configure Gluon, it shows up displaying your recently created workspace:

Explore the workspace

Initially, your workspace will be totally empty because you haven't downloaded any files from the Cloud yet.

Just click Configure to browse to your project (or repository if you prefer) and select what you want to download to your disk to start working on it.

In my case, I just selected a couple of files to be downloaded. However, you can choose to download the entire directory tree or just parts of it:

Configuration mode

Then, simply click Apply and the download will start.

To learn more about Gluon, just visit the Gluon guide.

Configure the data encryption password from Gluon

When you request a new organization, you can specify that you want to enforce encryption:

Force to encrypt the organization

If that flag is set during organization creation, Plastic Cloud will only accept encrypted data for this organization.

In this case, your organization uses encrypted data and Gluon will ask you to enter the encryption password to be able to decode the data.

This is how data encryption works:

All data leaving your computer is encrypted prior to being sent to the Cloud. This means it is totally safe and nobody can access it even if the Cloud is compromised. Data is decrypted once downloaded from the Cloud, and only users who know the password will be able to decrypt the data successfully.

Remark: The encryption password must be a well-kept secret in your organization.
Important: If you forget the password, not even we at Plastic SCM can help you recover your data.
Server encryption

Remember that you only have to configure the password once for the organization.

Important: In addition, keep in mind that the password must not be changed. Otherwise, the previously-encrypted data won't be decrypted. So, choose your password wisely.

Learn more about how the encryption works.


Regular vs Cloud repositories

As you have seen above, all that you need to do to access a Plastic Cloud repository is to use the combination organization_name@cloud as server name.

A regular local repo in your machine is named as: repo@local.

At Plastic Cloud, this repo is named as: repo@organization_name@cloud.

The @cloud part is just a shortcut to tell Plastic to connect to Plastic Cloud. In fact, you can do something like this:

Plastic cloud vs Local repos

And, as you can see, fantasywarrior3d@cloud is equivalent to fantasywarrior3d@cloud.plasticscm.com.

It's important to remark that you won't find any differences when switching between local and cloud repositories, other than the server location.

Encrypt all data uploaded to Cloud

When you request a new organization, you can specify that you want to enforce encryption. If that flag is set during the organization creation, Plastic Cloud will only accept encrypted data for this organization.


The motivation for encryption

Code is a very sensitive asset, so some teams will be extremely worried about protecting it as much as they can.

Even though Plastic Cloud runs on Azure and hence is protected by a well-known provider, we thought it would be a good idea to offer users the choice to encrypt the data when sending it to the cloud.


How does encryption work?

Encryption is quite simple and in fact it is supported by the standard Plastic SCM servers too.

Encrypted data


How to set up encryption

When you create the organization as "encrypted", Plastic Cloud rejects non-encrypted data. There's a header in the data to notify that, but the server doesn't know how to decrypt it.

Both Plastic and Gluon clients need to be configured to handle encrypted data and will ask you to enter the encryption password.

Remark: Be very careful with the password (or pass phrase) since it is the key to encrypting/decrypting your data. If you lose it, we won't be able to recover your data; it is simply not possible!
Remark: Don't panic! You'll have your data on your own server too. You are just pushing it to the Plastic Cloud, so in the unlikely event of a lost password you'll have a local copy of your repo. But, of course, once you decide to go to production using Plastic Cloud, you had better not lose it!

What is going on under the hood is the following:

A new file cryptedservers.conf is created on your Plastic SCM server directory with the following content:

encrypted_test@cloud e33a805b-0ce5-4047-81da-3c95c3c7b2a9.key

In my case, it is saying that every data transfer from/to encrypted_test@cloud must be encrypted/decrypted using the key created on file e33a805b-0ce5-4047-81da-3c95c3c7b2a9.key.


Frequently asked questions about encrypted data

What do you encrypt exactly?
We just encrypt file data, not metadata. This means that file names, branch names, labels, user names, and so on, are not encrypted, only file data.
Does it mean that even if Plastic Cloud gets compromised, attackers won't steal my code?
Exactly, that's what it means!
What if we are a team of, let's say, five, and we're all pushing/pulling to the Plastic Cloud?
Then, you all need to configure your keys. Whether you share the cryptedservers.conf file or you share the password. That's up to you!
Optionally, on bigger teams, you can have only one Plastic SCM server in sync with Plastic Cloud, and all the other replicated repos in the internal network just access to it. There are many possible options.
Can I open up a Branch Explorer to Plastic Cloud and diff a cset if the data is encrypted?
Not at this point, but that feature will be available soon. Right now, files will show an empty content because they can't be decrypted on the client.
The goal is to get the credentials from the local server (if configured to do so) to allow this scenario.

Administer your organization

Go to your Cloud dashboard

Once you get the confirmation that your organization is ready, you'll be able to access to your Cloud dashboard by logging into https://www.plasticscm.com/dashboard/cloud.

Once you login, you will enter the organizations management area. There aren't many options at this point so you'll see it is extremely simple to use.

Basically, all that you see is a list of the organizations you belong to.

If you are the administrator of an organization (we'll make you the admin when you request the organization), you'll be able to manage it.

Cloud organizations page

If you click Edit, you'll see something like this:

Edit the Cloud organization description

This is a simple page where you can edit the description of your organization.

You can click the View activity button to open a new page where you can see the usage of your entire cloud organization:

Cloud organization - Activity report

You can also click the Details link to launch a new page with the details by repository:

Cloud organization - Details



Read the following chapter to learn how and what you can manage of your Cloud organization.


Editing lock rules

By clicking the Edit lock rules button in the Cloud dashboard, you can start configuring the exclusive checkout.

The lock rules let you configure exclusive locking for binary files when you perform a checkout.

The exclusive checkout (or locking) is helpful when working with files than cannot be merged like binary files (images, video, audio...).

Using this feature, you can tell Plastic SCM what kinds of files need locking on checkout. If enabled, checking out a file will prevent other users from doing the same thing until you checkin or undo your changes. Any user can be assured that no new revisions of their checked-out files will appear while they're working on them.

The system performs the following operations:

  • Is the file locked? If so, it can't be checked out.
  • If it isn't locked, the file can be potentially locked. Plastic SCM will check whether the file name matches any of the defined lock rules. If the file name matches the rules, the file will be locked.

You can define rules than can be applied to:

  • All repositories (organization rules)
  • To specific repositories. These rules can be file extensions (such as *.xlsx, *.png or *.blend) or specific file names (such as readme.txt).

Edit lock rules

  1. To create / edit lock rules for the organization (all repositories):
    1. Enter the locking rules you want apply. You can click on the Load common lock rules button to load the most typical rules used (the ones related to binary files). You can add more rules or remove some of them.
      Edit lock rules for the organization (all repositories)
    2. To store the lock rules, click the Save button to store the lock rules.
  2. To create / edit lock rules for a specific repository:
    1. For the repository that you want to edit its lock rules, click the Add repository rules button:
      Edit lock rules for the repository
    2. A new empty field will appear under the repository name:
      Edit lock rules for the repository
    3. Enter your own rules or load the suggested common lock rules by clicking Load common lock rules. You can edit them as well.
    4. Click the Save button.

    You can remove all repository rules at any time by clicking the Clear repository rules.


Users and groups in Plastic Cloud

Plastic Cloud uses the same underlying mechanism to handle users and groups just like a regular Plastic SCM server. But, unlike Plastic SCM, instead of retrieving users and groups from LDAP, Active Directory, or a custom defined user/password file, Plastic Cloud works as follows:

  • Users are retrieved from plasticscm.com. You can invite any user to join your organization, and once they sign up to plasticscm.com, they will be valid users.
  • Groups are defined by organization. It is just like a cloud-based groups.conf defined from the organization management area. You can add invited users to the groups you create.

Cloud users and groups

You can define access policies to the cloud server for users and groups. You configure access policies by using the Plastic SCM GUI tool or the command line just like you would do with a regular server. At this point, all that you need to do in the web interface is to define the users, the groups, and its relationships.

You can define users as administrators in the web interface, but it just means that they can access the organization administration area. It doesn't have any influence on the Plastic repositories.

To get a better understanding of Plastic SCM users and groups please refer to our online documentation.


Adding users to the organization

In the Users and groups organization administration area, just click Add new user and you will arrive at this page:

Cloud organization - Add user

You can enter the email of any user you want to invite, even if they are not yet a plasticscm.com user. They will have to sign up to plasticscm.com prior to signing in, but you can already configure your groups counting on them as valid users.

By default, any new user will be automatically added to the built-in group called Developers. Of course, you can delete the group or rename it.


Configuring groups

By default, every new organization comes with two groups: Administrators and Developers. Every new user marked as Administrator will go to the Administrators group, and everyone else to Developers.

You can add new groups, delete the default ones, or rename them.

You can also add users to a group. Just click the edit icon to the right of the group name to access the group configuration area:

Cloud organization - Edit developers group

Here, I'm just editing the pre-configured Developers group.

From here, I can delete users and add new ones and also go to create new groups. I can also rename the group and edit its description.

If I click Add new member, I'll go to the following page:

Cloud organization - Add user to developers group

Here, I can simply type the email of a user that I want to add to the group.


Configuration wrap up

As you have seen, configuring your organization is straightforward. You'll get everything you need done with just a few clicks.

At this time, configuring users and groups is all that you can do in the web interface. Anything else is done, as usual, from the Plastic SCM GUIs or command line interface.


Current limitations and remarks

Remark You need to use Plastic SCM release 5.4.16.719 or higher in order to access Plastic Cloud.
Remark The "default" repo is not created in the Cloud. You'll need to create a repo manually before you can push branches to it.
Limitation At this point, changing the revision type of an item in Plastic Cloud is not available. This is a limitation due to the new storage we're using, which is different from the standard relational databases we use with Plastic SCM.
Limitation Path-based security is still not reliable in the cloud server. It is not key for replication operations and we expect to fix it in the near future to roll out full checkin workflow support.

FAQ

Product

What is Plastic Cloud extension?

Plastic Cloud is an extension to Team Edition. It is the perfect way to synchronize multiple teams running Plastic SCM servers on-premise.

You can host gigabytes of data in your Plastic Cloud repositories without issues. More at plasticscm.com/cloud


What do I need to use Plastic Cloud extension?

You'll need a Plastic Cloud subscription if you wish to store your repositories in the Plastic SCM hosted service, combined with an on-premises Plastic SCM Server (not required if you use Plastic Gluon).

To subscribe to Plastic Cloud, you must have a valid Plastic SCM license.

Examples:

  • Plastic Cloud + your Team Edition license for five users - the entire team will be able to access the Plastic Cloud.
  • Plastic Cloud + Personal Edition - you can use your Plastic SCM Personal Edition for free and then push/pull your changes to the cloud.

Does Plastic Cloud extension require a local (on-premises) Plastic SCM Server?

Short answer: No, if you use Plastic Gluon. Yes, if you are a developer using the regular Plastic SCM.

Let's go for the longer explanation now.

Programmers can achieve a better experience by using a distributed workflow with Plastic SCM. This means they will get better performance by pushing/pulling their branches in local repos to/from Plastic Cloud, instead of doing direct checkin to cloud. To work distributed you need a local server, whether it's central to the team, installed locally for each developer, or a mix of these combinations.

It is still possible to checkin directly to Plastic Cloud. It is the recommended way to work for users of Plastic Gluon, the tool designed for artists in game development, document writers, project managers, and other team members who don't work on code but work on other binary assets and don't need merge operations. Developers can also checkin directly and merge on Plastic Cloud if they need to.


How do I upload my data to Plastic Cloud?

You just need to push your data from your local Plastic SCM server (or your team on-premises server) to Plastic Cloud.

You will push to the Cloud the same way you push to a regular remote Plastic SCM server.

You can setup your sync view to push/pull branches in batches. Remember, your remote repos will be referenced as reponame@organization@cloud. Example: tetris@arcadegarage@cloud. The @cloud part simply tells Plastic SCM to connect to the cloud server instead of specifying a full IP or domain name.


Can I checkin and merge with Plastic Cloud extension?

Yes, direct checkin and merge are available since 5.4.16.792 (Nov-14, 2016). We discouraged direct checkin and merge for developers before, because we thought it was slower and they would be better served by push/pull from their local repos, but we got many requests from customers who preferred this simpler way of working.

We believe that artists in game development, document writers, project managers and other team members who don't work on code but other assets, will largely benefit from Plastic Gluon + Plastic Cloud. They will be able to perform direct checkins and download only the assets or content files they need. Also, exclusive checkout may be configured to ensure only one person is modifying each file at a given time.

We believe code developers can achieve a better experience by using a distributed workflow with Plastic SCM. This means they will be probably better served by pushing/pulling their branches to the Cloud, but they can work centralized too if they prefer. They can also merge using the Cloud server.

Some remarks for developers:

  • Checkins will be slower in the Cloud because data will have to travel through the Internet (and hence through a higher latency network), as opposed to performing checkins locally or to a server on your LAN. This is fine for artists and team members working on documents, but developers who expect super-fast checkins will find it slow. In short, checking in directly to the Cloud for developers is like going back to the old SVN days. Still, we optimize the entire cycle on a continuous basis for developers who prefer to work centralized.
  • However, pushing and pulling branches, while it's certainly also affected by network latency, is something you don't do as frequently. This means that the impact of having a distant server is slower. This is the DVCS style of working: many local checkins and then just a push, the same thing that many developers used to do with Git/GitHub.

In short, you can checkin and merge on Plastic Cloud, but we recommend that developers check the DVCS + Plastic Cloud workflow if they feel they need faster operations.


Can I lock files if I use Plastic Gluon to access Plastic Cloud?

Yes, you can. And, you can configure the files that will be locked on checkout from your Plastic Cloud organization's dashboard.


Which version of Plastic SCM do I need to access Plastic Cloud?

You need 5.4.16.719 or higher. Our network API was updated and expanded for Plastic Cloud, so older versions will not work.


Is my data secured in Plastic Cloud? What is the "data encryption" all about?

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 SCM will ask you to define an encryption key locally on your server (which can be your team's server).

Therefore, it works as follows:

  • Prior to uploading data to Plastic Cloud, the contents of each file are encrypted using the key you have defined.
  • The file contents are always stored encrypted in Plastic Cloud. This means that in the unlikely event that the server is compromised, your data won't be accessible by the attacker. The data is encrypted using a key that belongs to you. Plastic Cloud will never have or require access to this key, so it's unable to decrypt the data.
  • Whenever you or any of your team members download file contents from Plastic Cloud, the data is decrypted at your computers once it's received from the Cloud.

Every team member has to share the same data encryption key to work on the same organization. If everyone used a different one, nobody would be able to decrypt data encrypted by others.

Only file contents are encrypted. File names, directory names, branch names, comments and label names are not.


Is the connection to Plastic Cloud secured?

Yes, Plastic Cloud only allows SSL connections. Plastic knows that every connection to @cloud must be secured.

While a regular Plastic SCM server listens both in TCP and SSL, Plastic Cloud is restricted to SSL to enforce secure communications.

Thus, your server or client connection to the Cloud must be correctly configured to use SSL (which is the default out-of-the-box setting, by the way).


What happens if I accidentally remove a repository in Plastic Cloud?

Don't panic. Your data is still there. Just contact support and we will help you reconnect the repository.

Actually, when a repository is removed, it's just marked as deleted. We wait for a few days before actually erasing the data to give you time to recover accidentally removed repos.


Where is Plastic Cloud hosted?

Plastic Cloud is currently hosted in Microsoft Azure. That means it's built on top of well-proven technology by a trusted provider.

Plastic SCM metadata is stored in a combination of SQL Server Azure plus blob storage. Databases are replicated for high availability and redundancy.

Versioned files are stored in Azure blob storage. Each blob is replicated up to six times in two different physical locations.


What does it mean to choose a datacenter?

In order to speed up the data transfer, you can choose the closest datacenter to you to store your versioned file data.

There are several datacenters around the world, so by choosing the closest one to your team, you will reduce the network latency and hence greatly improve data transfer.


Does Plastic Cloud provide a way to browse repositories online?

Not currently. You can use your Plastic SCM client to list repos, as you would do with a regular remote Plastic SCM server.


Licensing and pricing

How does Plastic Cloud licensing work?

You need a valid Plastic SCM license (more on "licensing" below) to subscribe to Plastic Cloud. The license can be a valid Enterprise, Team, Cloud, or Personal Edition license. You can also use a Trial Edition.

Then, you need a Plastic Cloud subscription, billed on a per-team basis.

  • Plastic Cloud starts at $4.95/month per team for up to 15GB of storage. This level is meant to be used by teams handling small repos (or at least what Plastic SCM considers small :P).
  • The next level is $19.95/month per team for up to 100GB, which is the level specially designed for game development teams, 3D design teams, or teams who need to handle large binaries.
  • After the first 100GB, your subscription will grow by buckets of 50GB, at an additional $7.45/month per team per bucket.

Plastic Cloud will automatically upgrade your subscription to the next size tier without any interruption in the service. You will receive an email with the details of the payment seven days in advance of the next charge.


I'm a Community Edition user, can I use Plastic Cloud?

Yes, Community Edition users who qualify as open source projects and non-profit organizations can subscribe to Plastic Cloud and use their CE licenses to access the service.


I'm a Personal Edition user, can I use Plastic Cloud?

Yes, you can subscribe to Plastic Cloud while using your Personal Edition for free.


I have a Plastic SCM Trial License; can I use it to connect to Plastic Cloud?

Yes, the Trial License is a full featured license and allows you to access Plastic Cloud. In fact, it's a great way to test the entire ecosystem before you buy, since you have 30 days for free to use both products.


What happens if I cancel my subscription?

If you cancel your subscription, you will have a few days (typically one week) to retrieve all your data before we remove your organization to free up space. Upon cancellation, you will receive an email notifying you when the data will be finally erased.


Last updates

June 13, 2019
  • Now, the global Plastic Cloud guide is the new Plastic Cloud Extension guide. This guide is now adapted to explain you how to access the Plastic Cloud from the Plastic and Gluon clients with your Team Edition and Cloud Extension license.
  • May 29, 2019
  • We updated the documentation about how you can access to your Plastic Cloud dashboard and see the activity of your organization and how to administer your organization.
  • June 29, 2017
  • We added a note about the specific ports to use when creating your server profile if you are working in a high security environment.
  • February 7, 2017
  • Learn how to work with Plastic Cloud Edition in your Windows, Linux and Mac OS systems.
  • December 14, 2016
  • Some screenshots in the guide were updated.
  • November 30, 2016
  • We explain the differences between Plastic SCM Team Edition + Cloud extension and Plastic Cloud Edition.
  • November 21, 2016
  • Since release 5.4.16.792, direct checkin and merge are available in Plastic Cloud.
  • January 21, 2016
  • Learn how to access Plastic Cloud from Gluon.
  • If you have more questions about Plastic Cloud, please read the FAQ.
  • December 4, 2015
  • Removed some limitations. We're introducing new features!