Keep provenance checkable beyond the original workflow.

puit.is embeds an imperceptible Media UID at source, allowing redistributed or transformed media to be linked back to a provenance record backed by a public, tamper-evident UID-derived commitment — even when the original metadata no longer travels with it.

Proof. Protect. Preserve.

Every export, compression, or migration can sever a digital object from its origin. Puit.is adds a provenance layer designed to survive that journey.

A unique identifier is the bridge. The record preserves evidence of origin, attribution, and continuity as media moves across platforms.
The puit.is partner console after an extract and verify run. The generated copy carrying the Media UID, the response the service returned for it, and its confidence value.

Content. Context. Confidence.

Verification should return evidence, not a verdict. puit.is reports what was recovered, how confident the match is, and how far it sits from the stored record.

Repeatable checks you can inspect, rerun and reconcile years later.
A puit.is team member explaining content context and confidence at a desk.

Embed. Extract. Verify.

An imperceptible signal embedded at source, linked to a tamper-evident public record. Designed to remain recoverable after compression, edits, or migration.

Embed at source

Attach provenance before the file starts moving.

Extract later

Recover the signal after edits, compression, migration, or reposting.

Verify later

Returns recovery, match distances and a graded status.

A 128-bit Media UID is written into the pixels; the visible change is not noticeable at 1:1.A Media UID is recovered after a messaging channel re-encodes and renames the image.The recovered Media UID is checked against the evidence record and public commitment.

Built first where continuity matters most.

Archives, museums, rights holders, and public institutions are where digital origin first becomes non-negotiable.

The same need is spreading across media, licensing, and AI-generated content. Puit.is starts with high-consequence provenance and scales from there.
Four custodians each hold their own copy of the same object. Every copy shows the same identifier fragment and resolves to one shared provenance record. The current beta is operated by INICS; independent operation of verification is part of the TRL7 path.