Gems in a box products are completely on-premises, and have their infrastructure sized according to the content load going to be archived. For small loads it is possible to design a small project, while for larger loads it is necessary to have a bigger and more robust infrastructure.

Although the system is aimed at managing video collections, it is possible to manage any type of file such as: photos, audios, documents, engineering plans, graphic projects, games, etc. Each type of item has its own specific set of metadata, in the case of photos there are fields for photographers and credits whereas for videos there are fields for cameraman and reporter.

A load is considered small when it does not exceed 24TB of archived content annually. An average load ranges from 30TB up to 200TB of archived content annually, corresponding to 1TB of archived content per day. For higher loads, the projects are customized and require studies and assessment of the flows that are desired to be systematized.

The infrastructure is designed according to the operational need, in such a way you will avoid financial losses with oversized infrastructures that become idle, and operational bottlenecks with undersized infrastructures.

We need to choose the best operational infrastructure. Take the example, if you are carrying a few things, one bag may be enough, but to load large volumes it may be more appropriate to use a pallet or even a truck.

Anyway, if you design the infrastructure in the wrong way, it will compromise its efficiency, as well as waste time and money.