What Does It Actually Cost to Anonymize 1,000 Hours of Footage? Manual vs Cloud API vs On-Premise

TL;DR: For 1,000 hours of recorded video, manual redaction typically lands between EUR 120,000 and EUR 240,000 in operator time, a per minute cloud API between EUR 6,000 and EUR 30,000 before transfer and review costs, and on-premise software such as Gallio PRO between EUR 8,000 and EUR 17,000 all in. This breakdown is for security managers, records officers and compliance leads who have to defend a budget line.

Why cost per hour is the only comparable unit

Vendors quote in incompatible units. Manual work is quoted in people, cloud services in minutes of media, licensed software in seats or months. The only way to compare them is to convert everything to cost per processed hour of footage, and to include the human review that all three models require.

The worked example below uses 1,000 hours of recorded CCTV or body worn camera video, a loaded operator rate of EUR 30 per hour, and a 36 month horizon. Substitute your own rate and volume. The structure of the answer does not change.

Model 1: manual redaction in house

Teams that redact by hand in a video editing suite typically report 4 to 8 hours of operator time per hour of footage, depending on crowd density, number of moving objects and how many camera angles have to stay consistent.

At 5 hours of work per hour of footage, 1,000 hours of video becomes 5,000 operator hours. At EUR 30 loaded, that is EUR 150,000, and the realistic band is EUR 120,000 to EUR 240,000. It also consumes roughly three full time equivalents for a year, which is usually the harder number to get approved.

Manual work has one genuine advantage: judgement. It has two structural weaknesses. Output quality drifts with operator fatigue, and there is no consistent record of what was redacted across a batch. Our comparison of manual versus automated video anonymization covers where each approach holds up.

Model 2: cloud API billed per minute

Cloud redaction services bill per minute of processed media, commonly in the range of EUR 0.10 to EUR 0.50 per minute depending on resolution and tier. One thousand hours is 60,000 minutes, so the processing line alone is EUR 6,000 to EUR 30,000.

Three costs sit underneath that headline and are usually missing from the first quote:

• Transfer. One thousand hours of 1080p footage is roughly 2 to 5 TB, and 4K multiplies that. Upload time, bandwidth and egress charges are real and recurring.
• Vendor governance. Sending identifiable footage to a third party makes them a processor under GDPR Article 28(3), which requires a written processor agreement. If the service or its subprocessors sit outside the EEA, Chapter V, Articles 44 to 49 applies and you need a documented transfer mechanism.
• Re-runs. Every failed batch is billed again.

The deeper security trade off is covered in on-premise versus cloud anonymization.

Model 3: on-premise licence

On-premise software moves the cost from variable to fixed. A Gallio PRO Standard licence is EUR 89 per month, or EUR 1,068 per year with the annual discount, and volume does not change that figure. Gallio PRO states that local processing works out around six times cheaper than cloud processing at comparable volumes.

Add hardware. A workstation with a GPU suitable for accelerated processing costs roughly EUR 2,000 to EUR 4,000, amortized over three years at about EUR 700 to EUR 1,300 per year. GPU acceleration delivers up to ten times faster processing than CPU only.

Then add the review pass, which no model escapes. Spot checking automated output and correcting missed objects in the built in editor typically runs 0.2 to 0.5 hours per hour of footage, so 200 to 500 hours at EUR 30, or EUR 6,000 to EUR 15,000.

The 1,000 hour comparison

Line item	Manual	Cloud API	On-premise
Processing	EUR 120,000 to 240,000	EUR 6,000 to 30,000	EUR 1,068 per year
Hardware	Existing workstation	None	EUR 700 to 1,300 per year
Transfer and egress	None	EUR 500 to 5,000	None
QA and correction	Included above	EUR 6,000 to 15,000	EUR 6,000 to 15,000
Vendor governance	None	DPA, transfer assessment	One time security review
Indicative total	EUR 120,000 to 240,000	EUR 12,500 to 50,000	EUR 8,000 to 17,000
Cost per hour	EUR 120 to 240	EUR 12 to 50	EUR 8 to 17

Four line items most budgets miss

1. Storage of originals. Under GDPR Article 5(1)(e), storage limitation applies to the unredacted source as much as the export. Retention and secure deletion of originals is a cost in every model.
2. The second pass. Missed detections are found in review, not in processing. Budget for correction time or the number is fiction.
3. Objects nothing detects automatically. Faces and license plates are automated. Name badges, screens, documents, tattoos and logos are manual work in any tool, so count the frames where they appear.
4. The compliance tail. GDPR Article 32(1) requires you to demonstrate appropriate technical measures, and Article 83(5) sets the ceiling for failing to at EUR 20 million or 4 percent of global annual turnover. We covered this against implementation cost in the cost of a GDPR violation versus the cost of anonymization.

How to build your own number in six steps

1. Measure real volume. Pull the last twelve months of export requests and convert them to hours of footage per month. Most teams overestimate by a wide margin.
2. Time one honest manual job. Take a representative ten minute clip, redact it properly, and multiply. That ratio is your manual baseline.
3. Get the cloud quote in writing. Ask for per minute price, egress, storage, minimum commitment and the subprocessor list in one document.
4. Benchmark on your own hardware. Run your own footage through the free Gallio PRO demo, which is unlimited and watermarked at up to 720p, and time it. That gives you throughput rather than a brochure figure.
5. Add the review pass to all three columns. Comparing automated processing against manual work without including QA is the single most common error in these business cases.
6. Divide and project over 36 months. Compare cost per processed hour, then compare cumulative cost. Variable pricing and fixed pricing cross over faster than most teams expect.

When each model still wins

Manual work wins below roughly 20 hours of footage per year, where no tool repays its setup. Cloud wins when volume is genuinely unpredictable, footage is already stored with that provider and the data is low sensitivity. On-premise wins on everything else, and it wins decisively when the footage cannot leave your infrastructure at all.

Gallio PRO runs entirely on your own machine or server, stores no detection logs and no personal data, and supports JPG and PNG images plus MP4 and MOV video. It is available as a desktop application for Windows, macOS and Linux, as a Docker container and with a REST API. Automatic detection covers faces and license plates, with a built in manual editor for everything else, and it processes recorded files rather than live streams. For high volume batches, see Gallio PRO video anonymization.

FAQ

How much does it cost to blur faces in one hour of video?

Roughly EUR 120 to EUR 240 per hour if redacted manually, EUR 12 to EUR 50 per hour through a cloud API once transfer and review are included, and EUR 8 to EUR 17 per hour with on-premise software at 1,000 hour volumes.

Is cloud video anonymization cheaper than on-premise software?

Only at low volume. Cloud pricing is variable and scales with every minute processed, while a licence is fixed. At 1,000 hours a year the fixed model is usually cheaper, and the gap widens with volume.

How long does manual redaction take per hour of footage?

Teams typically report 4 to 8 hours of operator time per hour of video, depending on crowd density, number of moving objects and how many camera angles must stay consistent.

Do I still need a person reviewing automated output?

Yes. Budget 0.2 to 0.5 hours of review per hour of footage for spot checks and for redacting objects that are not detected automatically, such as badges, screens and documents.

Does sending footage to a cloud anonymization service require a DPA?

Yes. The provider acts as a processor, so GDPR Article 28(3) requires a written processor agreement, and transfers outside the EEA additionally require a mechanism under Chapter V, Articles 44 to 49.