Provenance that re-runs the edit.
C2PA / Content Credentials log that an edit happened and a hash of the result. Obsign adds the part the standard leaves open: the operation itself re-runs and reverses, bit-for-bit. It is the rail; we are the re-executable edit layer on top.
C2PA-compatible
We write Content Credentials and add a re-runnable layer -- a proposed assertion, c2pa.reproducible.operation. We extend the ecosystem; we do not replace it.
The edit is reproducible
Most provenance records that an edit occurred. Obsign re-runs the exact edit and recovers the original, so a newsroom can prove not just that an image was changed, but how -- and undo it.
Anyone can verify
A free, client-side verifier confirms integrity, signature, and issuer with nothing uploaded. Your readers can check a credential themselves.
Read any image's credentials
Inspect the Content Credentials on any image, and verify an Obsign receipt -- on your device, nothing uploaded.
C2PA is the standard ecosystem and the rail Obsign rides on. We are standard-aligned and C2PA-compatible, and add re-executable edit provenance; we do not replace Content Credentials. Third-party C2PA viewers trust a signer once its certificate is on the C2PA trust list.
Build it with us
We take a small number of design partners. A 30-minute call, a use-case review, SDK access, and a pilot with honest commercial terms if it's a fit.