How puit.is keeps origin checkable after transformation

Digital provenance often fails after media leaves its original system. Metadata can be stripped, hashes fail after benign changes, and platform claims rarely travel with the file.

Puit.is combines imperceptible watermarking, tamper-evident public anchoring, and confidence-graded verification to preserve a checkable origin link across editing, compression, migration, reposting, and reuse.

Technology for provenance that has to survive real distribution.
Illustration showing how puit.is embeds an imperceptible watermark at the source.

Image before watermarking

Diagram showing how puit.is links provenance to a public record.Illustration of the watermark signal remaining linked to the image after processing.

Image after watermarking

Workflow overview

From creation to later review, puit.is is designed for provenance that can survive real distribution paths.

Embed at source

At or near the point of origin, an imperceptible signal is embedded into the file. It connects the media to a provenance claim without changing normal viewing or use.

Anchor the claim

A cryptographic commitment is linked to a tamper-evident public record, so later verification does not depend on one platform, vendor, archive system, or private database.

Verify later

The signal can be recovered and checked against the record. Results can be confidence-graded rather than purely binary, so verification remains useful after compression, reformatting, migration, reposting, or partial degradation.

Why now

Synthetic media is scaling faster than provenance infrastructure.

At the same time, archives, media institutions, regulators, and public platforms are increasingly required to preserve authenticity, attribution, and continuity across digital workflows.

Puit.is exists because origin is becoming operationally important again.

Core components

Three technical layers make provenance resilient, independently checkable, and practical to deploy.

Watermarking engine

Imperceptible, edit-tolerant embedding designed for distribution paths where metadata can be stripped and exact-file hashes no longer apply.

Conveyor machine outputting verified image prints

Public anchoring layer

Tamper-evident commitments keep provenance checkable across operators, institutions, systems, and time.

Linked cubes leading to a framed image symbol

Verification toolset

Confidence-graded checks help reviewers understand how strongly a file still links back to its claimed origin after transformation.

Open toolbox with hammer and pliers beside a laptop

Reproducible evidence

Runbooks, manifests, per-item results, and integrity hashes support independent re-checks and later review.

Vendor-neutral verification

Checks are designed to work beyond one closed platform, database, archive system, or operator.

Privacy-aware provenance

Origin can be verified without unnecessary exposure of sensitive data.

Designed for auditability, review, and regulatory alignment

Puit.is is built for environments where verification must be reproducible, inspectable, and independent of one vendor stack.

Policy-aware architecture
Designed with European expectations for transparency, auditability, data protection, and digital trust in mind, including GDPR, the EU AI Act, eIDAS 2.0, NIS2, and the DSA.

Comparison with existing approaches

Puit.is does not ask whether media looks manipulated. It preserves the link needed to check where it came from.

Approach
What it gives you
Where it weakens
Why puit.is matters
Detection
A manipulation-risk signal
Reactive, probabilistic, and adversarially fragile
Adds source-linked continuity before later doubt begins
Metadata credentials
Declared provenance in controlled workflows
Often stripped, detached, or lost in distribution
Keeps origin linkage meaningful after transformation
Hash-only anchoring
Proof that an exact file existed
Breaks on benign edits, compression, and format changes
Supports verification beyond exact-file matching
puit.is
Authorship and continuity linked at the source
Designed for graceful degradation
Enables later independent verification across systems and time

Built to evolve without replacing the trust model

Puit.is is designed as a modular provenance stack. Watermarking, anchoring, verification, and deployment can improve as formats, attacks, and institutional workflows change - without rebuilding the entire system.

New formats

Roadmap from images toward audio, video, 3D, and complex heritage objects.

Modular upgrades

Watermarking, anchoring, and verification layers can be strengthened without rebuilding the whole system.

Operational resilience

EU-hosted, reproducible deployment supports auditability, continuity, and institutional scale.