The recorder shouldn’tbe the only copy

Check the upload settings and documentation for the exact camera or recorder model and firmware. Equipment that uploads files over SFTP can connect directly. FTP or explicit FTPS (AUTH TLS) requires Sync Bridge on the customer’s network. Check which clips or snapshots the model can export, then test an upload and download before adding it to your customer’s service.

At your customer’s site, on a Windows or Linux computer or in Docker. The camera connects to that local host; Sync Bridge connects outbound to our SFTP storage over port 22. The host must be running and reachable for transfers. Choose explicit FTPS when supported; plain FTP is unencrypted and belongs on a restricted, trusted local network.

Storage capacity is listed in GB, rather than days of footage. How much footage fits depends on the files your equipment uploads. A retention period and automatic cleanup policy are not specified in the current offer. Confirm the retention requirements for your customer’s site with us before relying on a set number of days.

The current offer does not specify how uploads are handled at the storage limit. Confirm this with us before putting the setup into service. Measure a representative batch of uploads to choose enough capacity, and agree how files will be removed or storage expanded. Do not assume old footage is automatically deleted to make room.

Files cannot reach the remote storage while the site is offline. Sync Bridge works on the remote file system and does not retain a permanent local copy. Any queuing, retry, or resend behavior depends on the camera or recorder. Check its documentation and test an interrupted upload; automatic catch-up is not guaranteed.