About puit.is

Evidence of origin should not depend on one platform.

Synthetic media made convincing manipulation cheap and scalable. We believe evidence of origin and continuity should remain re-checkable across organisations, technologies, and time.

Why puit.is exists

A durable link to provenance has to travel with the media itself, because any record kept only beside a file can be separated from it. It has to be checkable by people who have no reason to trust us. And it has to state what it can show, not whether content is true. Those three constraints are what puit.is is built around.

The team behind puit.is

puit.is is built by an interdisciplinary team spanning product leadership, implementation, visual computing, distributed systems architecture, watermarking, and programme delivery.

Founder / Product & Programme Lead

Thomas Howert

Thomas is a repeat founder and leads product strategy, delivery, partnerships, governance, and fundraising for puit.is. His background spans analytics, enterprise delivery, business development, and data- and AI-driven products.

Implementation & DevOps

Daniele Frisanco

Daniele contributes across services, APIs, integrations, CI/CD, infrastructure, and reproducible evidence workflows. His background spans SaaS and media-pipeline delivery, with a focus on stable, operable systems. He helped deliver the current clean-room implementation within twelve weeks.

Watermarking Research & Benchmarking

Mario von Bassen

Mario is an MSc candidate in Visual Computing at TU Wien. His work focuses on applied watermarking research, benchmark design, robustness evaluation, and evidence structuring under real transformation conditions.

Additional specialist contributions

Architecture and distributed systems

Target architecture, trust boundaries, interfaces, and technical governance, including the path from the current hosted service toward independently operated infrastructure.

Watermarking architecture and quality

Watermark architecture, performance targets, confidence calibration, benchmark readiness, and technical quality gates for the media-bound UID layer.

Programme coordination

Delivery cadence, stakeholder follow-up, reporting, risk tracking, and coordination across technical, operational, and external workstreams.

Additional specialist capabilities are brought in where needed. Individual contributors are named publicly only with their consent.

Current context

External evaluation

Passed EIC Accelerator Step 1 and invited to Step 2 in July 2026. Evaluation is ongoing; puit.is is not EIC-funded. Review the evidence.

Ecosystem and integration work

Presented a provenance integration concept for IIIF workflows at the 2026 IIIF Online Meeting. Contributed a poster and exhibition and took part in the hackathon at the Digital Heritage Summit in Cyprus.

Operating context

puit.is is currently developed and operated by INICS Information Consulting & Solutions Ltd, Cyprus.

The project is being prepared for a broader international and open governance model as it develops toward independently operated, multi-operator infrastructure.

Institutional trust

Built as open provenance infrastructure

puit.is is being developed as open-core provenance infrastructure for media that must remain re-checkable across organisations and platforms. The current beta is operated by INICS. Independently operated verification and multi-operator validation form part of the TRL7 path, followed by TRL8 qualification and production readiness, and ultimately TRL9 operation in live multi-operator environments.

Open verification

Evidence formats and verification outputs are designed to be inspectable and reproducible.

Independent operation

Multi-operator validation is part of the TRL7 path. TRL8 focuses on qualification and production readiness; TRL9 represents proven operation in live multi-operator environments. These later stages are not presented as achieved today.

Governance

The organisational and open-source governance model is being established alongside the transition from beta infrastructure to independently operated deployments.

Test provenance in a real workflow.

Work with us on an integration test, independent validation, or technical collaboration.