Provenance, at the heart of your CMS.
ProvSeal integrates locally with your CMS: media are verified on import, their provenance is kept during editing, and the published version is signed with your identity.
How it works for you.
What ProvSeal records at each step of your workflow.
Import
A media file arrives in the media library. Its provenance is read immediately.
manifest readingVerification
The status is shown to your teams: Trusted, Not recognised, Invalid or No information.
trust statusIntegration
The media file is cropped, captioned, inserted. The steps add up without breaking the chain.
ingredient · c2pa.editedPublishing
The published version is signed with the publisher’s identity.
c2pa.publishedWhat ProvSeal changes in your CMS
What changes, concretely, in your day-to-day work.
- See the status from import.Your teams know where a media file comes from before they use it.
- Publish without breaking the chain.The CMS’s resizing and cropping are declared instead of erasing provenance.
- A local integration.Media are not sent to a third-party service: the integration runs on your infrastructure.
What C2PA does not prove
Transparency is part of the standard. Knowing its limits matters as much as knowing what it can do.
- The truth of what the image shows
- That a human is the author
- Copyright ownership
- Automatic AI detection
Questions
that matter.
Straight answers to the questions we hear most.
Which CMSs are compatible?
The local integration is scoped to your CMS during the pilot program.
Do the variants generated by the CMS keep their provenance?
That is the goal of the integration: declaring transformations instead of letting them erase the manifest.
Does it require custom development?
It depends on your CMS and your workflows; we define it together during the pilot.
Other use cases
Every profession has its steps. ProvSeal records them all.
Test it on your production.
ProvSeal Enterprise is in beta. For 30 days, we install it with you and adapt it to your profession.