Assets with a known history.
ProvSeal verifies the provenance of assets as they are ingested into your DAM, keeps it across renditions and signs the versions you distribute. Without a single file leaving your infrastructure.
MASTER_0412.tif✓ verified on ingestHow it works for you.
What ProvSeal records at each step of your workflow.
Ingest
Every asset is verified as it enters the DAM. Its status is recorded.
manifest reading · statusQualification
Teams know which assets carry reliable provenance before they use them.
Trusted · not recognised · invalidRenditions
Formats, crops and versions inherit the provenance of the original asset.
ingredient · c2pa.editedDistribution
Distributed versions are signed with the organisation’s identity.
c2pa.publishedWhat ProvSeal changes in your DAM
What changes, concretely, in your day-to-day work.
- Qualify assets on the way in.Know what is proven before using it in a campaign.
- Keep provenance across renditions.Derived versions reference the original asset instead of starting from scratch.
- Nothing leaves the DAM.Verification and signing happen locally, 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 DAMs are compatible?
The local integration is scoped to your DAM during the pilot program.
Can an existing collection be processed?
Yes, in batches: verification shows which assets already carry provenance.
Are assets without provenance excluded?
No. They are simply identified as “No information”, which says nothing about their authenticity.
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.