Currently our team is using Plastic Cloud since we have a mix of in-office and remote workers. But as our project grows larger the update / branch switching time grows.

We would like to have an internal office copy of the repository that frequently syncs with the cloud copy but then our external team would be pointing to a different repository which breaks the file locks which are half the reason we are using Plastic over other source control solutions.

We could have our external team VPN into our local network but our local bandwidth is not the most ideal and they would have a worse situation than pointing to Plastic Cloud.

Ideally we should be able to lock a file and have that identified and respected across multiple repositories, which seems like it would be possible if the File Lock database / server was hostable as it's own entity.