Video Surveillance Storage

Bitrate is the input that decides everything and the one most often taken from a datasheet's best case. Resolution, frame rate, codec and — above all — scene complexity move it enormously: a fixed camera watching an empty corridor and one watching a busy loading dock at the same settings can differ by a factor of three or more in what they actually write.

Camera count and retention days are the easy two, but retention deserves a question rather than an assumption: whether the requirement is thirty days for everything, or thirty days for most cameras and ninety for a handful at controlled points. Tiering the retention is often the difference between a straightforward purchase and an unaffordable one.

The fourth is what happens on failure. A surveillance array that loses a drive should keep recording, which means RAID level and hot-spare count are part of the capacity arithmetic rather than an afterthought — and they are why usable capacity is always meaningfully less than the sum of the drives.

Camera hardware, access control and the physical-security estate around it are carried on our dedicated physical-security storefront at security.getuniqcli.com rather than on this catalog. If your project spans both, we will quote the storage here and route the camera side there rather than pretend to inventory we do not hold.

The retention policy itself is yours. How long footage is kept, who may view it, how exports are handled and what the legal-hold process looks like are decisions your organization makes and documents. We configure the array to the retention figure you give us; we do not advise on the policy behind it and we make no compliance promise about it.