How CBC/Radio-Canada Deployed End-to-End Content Provenance

CBC/Radio-Canada is one of Canada's most trusted news institutions — and one of the most forward-thinking when it comes to content authenticity. As a founding member of Project Origin and a chair of the IPTC Media Provenance Committee, CBC has been at the center of the C2PA ecosystem since its inception. Their full deployment is a blueprint for what enterprise-scale provenance infrastructure looks like in practice.

The Challenge: A Complex, Multi-System Newsroom

Modern broadcast newsrooms are not simple content pipelines. CBC's operation involves multiple ingest systems, editing platforms, graphics workflows, archiving infrastructure, and distribution channels — all operating simultaneously across English and French language services. Applying consistent provenance metadata across that environment is a significant technical challenge.

The conventional assumption is that this kind of deployment takes months of integration work. CBC's experience proved otherwise.

End-to-End Provenance in Weeks

Working with OpenOrigins, CBC deployed a digital fingerprinting system that generated a provenance record for every piece of content produced by the broadcaster. The key insight was treating provenance as infrastructure rather than a workflow addition — embedding the generation of C2PA manifests into existing ingest and processing pipelines rather than adding manual steps for journalists or editors.

For video specifically, CBC implemented AWS Content Credentials, applying C2PA metadata to fMP4 video files as part of the existing transcoding workflow. The result: every video asset leaving the system carries a signed provenance record with no change to editorial workflow.

What the Deployment Covers

• Images: C2PA-signed images published on cbc.ca, among the first news organization to publish signed visual content at scale
• Video: AWS-integrated content credentials applied during transcoding
• Verified Publisher Status: CBC is listed on the IPTC Origin Verified News Publishers list, giving audiences a way to verify CBC's content authenticity independently

The Broader Significance

CBC's deployment demonstrates three things that matter for any organization considering content provenance infrastructure:

Speed is achievable. End-to-end deployment in weeks, not months, is possible when provenance is treated as an infrastructure layer rather than a process change.

Scale is not a barrier. A complex, multi-system newsroom with simultaneous English and French operations successfully deployed consistent provenance. If CBC can do it, most organizations can.

Verified publisher status is a competitive advantage. Being on the IPTC Verified News Publishers list signals authenticity to platforms, audiences, and regulators in a way that press releases cannot.

What This Means for Your Organization

CBC's model — API-first provenance infrastructure integrated into existing workflows — is the same model Limbo provides for enterprise deployments. The question isn't whether your organization's content pipeline is too complex. It's whether you have the right infrastructure partner.

Talk to us about your deployment.