Mavis C2C is a service for getting content into the cloud directly from Mavis Camera or a Mavis integrated device. Once in the cloud this content is transferred to a partner service such as Amazon S3, MediaSilo and Sony CI Media. This allow teams to start reviewing and editing media instantly.
If you have any questions or are interested in bulk Mavis C2C licensing, please contact Mavis Enterprise Sales.
How does it work?
When using Mavis C2C data is uploaded to Mavis Hub Cloud as secure encrypted chunks. Once an upload is complete the final asset is transferred to a third party partner service. Partner integrations currently supported by Cloud Hub include Amazon S3, MediaSilo and Sony CI Media with more integrations coming soon.
Uploading content to Mavis Cloud Hub means that all partner integrations can take advance of powerful Mavis technologies, which bring the benefits of progressive (real-time) uploads, fast parallel-chunk uploading, automatic retry logic and secure encrypted chunk management.
It also provides remote device management enabling teams to centralise control over where and how assets are delivered from device to partner services.
Mavis C2C High Level Overview
Asset Transfer Architecture
Assets are transferred from a physical device or app as a collection of nondescript chunks. These chunks are generated from either an existing 'complete' asset or from an asset that is currently being generated (e.g. you are still recording). A chunk uploader manages the process of getting the data into the cloud quickly and reliably, including handling retry logic should errors occur.
As each chunk is uploaded it is pre-precessed and cached. This allows for drops in internet connectivity during uploads. The chunked data cache is backed by Amazon S3 with data automatically encrypted at rest. This data is then inaccessible from all services other than the just-in-time file generator.
The just-in-time file generator processes chunked data into a final video asset. This video asset is transferred to a third party using the third party interface and auth.
The final video asset is transient and is never stored by Mavis. All data stored in a chunked data cache is automatically deleted after a maximum of 48 hours. Each Mavis chunked data cache is also located as close to the destination third party service as possible. For example data destined for Sony CI will be stored in a Mavis chunked data cache located in US-East-1 as this is where Sony stores Sony CI asset data. Data destined for an Amazon S3 bucket in Frankfurt (EU-Central-1) will be stored in a Mavis chunked data cache in the same Frankfurt (EU-Central-1) region. This allows enterprise customers to abide by their data commitments, for example EU customers can ensure data is kept within the EU.