01
Start with the data path
A local application processes the video on the operator’s computer. A cloud service requires the source to be transferred to external infrastructure. That difference affects approvals, contracts, retention and incident scope.
Local processing is especially attractive when the organisation already controls Windows endpoints and wants to avoid another video repository.
02
Cost behaves differently
Cloud tools commonly align cost with usage, storage or processed minutes. Local software typically has a licence cost while the customer supplies compute. High or unpredictable footage volume can therefore change the economic result.
- Compare active operator time.
- Add vendor minute and storage charges.
- Include workstation capability.
- Account for procurement and data-transfer review.
03
Neither model removes quality assurance
Detection errors, reflections and non-face identifiers can occur regardless of where compute runs. Human review remains the control that turns model output into an approved disclosure.
Run a representative pilot and document the complete workflow before selecting a vendor.
Apply the workflow
Review real footage locally.
CensorFlow detects and tracks visible faces on your Windows PC, then lets a person correct and approve the result before export.