Cloud Shared Workspaces is a DNAfabric synchronization workflow where both media and project/bins are synchronized across two or more creative teams and end points thus enabling remote editors and creatives to work together.

Cloud Shared Workspaces is a “cloud bounced” data sync architecture. Rather than point to point, it creates upload and download sync jobs between end points (shared storage, end user systems etc.) and a cloud cache. These jobs can be automated or run manually as needed. Data is synced up to the cloud cache and in-turn re-downloaded by the different agents. All uploads and downloads are performed directly, to and from the cloud cache using the cloud provider’s HTTPS based protocol.

Cloud Shared Workspaces supports multi-way synchronization between two or more on-premise, remote and cloud deployments.

Data acceleration is achieved through multi-threading, multi-part upload (* when supported by the cloud provider) and multi-processing.

All data transfers are performed using the cloud provider’s secure access keys. Data is encrypted when it leaves the client system, then encrypted in the cloud cache “at rest” and then decrypted during download. These keys can be revoked at any time, essentially guaranteeing that Cloud Shared Workspace jobs too don’t have any access to cloud hosted data.

• Cloud shared workspaces syncs Avid MediaFiles workspaces and Avid projects in an Avid consistent manner thus enabling multiple geo-spread editorial teams to collaborate and share media.
• For Avid MediaFiles workspaces, media files are synced ensuring databases stay consistent and avoids rescans.
• For Avid projects, projects are synced and locked to prevent overwrites and deletions. Snapshots are also maintained (similar to the Unity Attic), to allow for rollbacks.

• Cloud Shared Workspaces syncs Adobe Premiere media workspaces and Adobe Premiere projects in an Adobe consistent manner thus enabling multiple geo-spread editorial teams to collaborate and share media.
• For Adobe media workspaces, media files are auto-synced as the content is ingested, exported and rendered.
• For Adobe projects, projects are synced and locked using Adobe Productions semantics to prevent overwrites and deletions. Snapshots are also to allow for rollbacks.

• Public Cloud Providers: AWS S3, Azure Blob, Google Cloud Object, Wasabi (*), Backblaze B2, Google Drive.
• Private Cloud Providers: S3 compatible e.g. MinIO.

Cloud Shared Workspaces uses the object storage’s HTTP interface to upload and download data thus not requiring any virtual machines or servers to be spun up.

Public cloud providers enable ready scaling without worrying about bandwidth needs. This allows Cloud Shared Workspaces to scale to hundreds of users and petabytes of storage simply via increasing cloud resources.

Consumer sync applications such as Google Drive, Dropbox, OneDrive and Box provide multi-system synchronization. However, key areas where Cloud Shared Workspaces differs are:

• Ability to lock and sync Adobe and Avid media/projects in an application consistent manner.
• WAN acceleration of assets for upload and download.
• Ability to use other cloud providers.

• MAM solutions provide Adobe Premiere embedded panels for remote collaboration and sharing. This is done via providing users with a panel through which they can search, download/checkout, upload/checkin assets and projects.
• This solution works well for remote editors with standalone projects and are not working collaboratively on multiple components including assets, sequences and projects.
• When projects begin to scale to hundreds if not thousands of sequences, bins, managing checkin/checkouts of projects and media can become painstaking and infeasible.
• Cloud Shared Workspaces can manage multiple users collaborating across thousands of assets, sequences across remote systems. This can be done fully automatically without needing any manual processes.