Find us at
· June 17–20 · Paris Expo Porte de Versailles
Book a meeting on
· June 17–20 · Paris Expo Porte de Versailles
A neutral, verifiable trust layer for machine-to-machine decisions.
· June 17–20 · Paris Expo Porte de Versailles
Modern systems make automated trust decisions everywhere — AI agents calling APIs, automated approvals, credential verification, content provenance checks, software supply-chain governance. Both inside organizations and across them.
But the logic behind those decisions is fragmented across code, configs, ad-hoc integrations, private policy documents, and platform-specific permissions. Existing systems may record parts of a decision, but rarely provide a consistent way to resolve who is trusted, under which policy, and whether that trust is still valid.
The result is familiar: stale revocations, unverifiable approvals, policy drift, and audit evidence that external parties struggle to confirm.
Agent authority is fragmented Spread across code, config, credentials, and tool permissions — hard to resolve, hard to verify, hard to revoke.
Trust updates don't propagate Policy, trust, and revocation changes move through ecosystem-specific mechanisms — relying parties risk operating on stale state.
Cross-org approvals are unverifiable Approvals live in emails and private systems — hard to know who had authority, under which policy, and whether it was still valid at the time.
Provenance ≠ governance Provenance verifies origin and history. Governance decides whether that source is acceptable under your policy today.
Audit evidence is siloed Decisions get logged, but the evidence is stuck in private systems — hard to verify which policy governed it or whether the record is unchanged.
VDR is a trust metadata registry. It stores and serves trust records — you are in control of your policy engine.
Identifiers, policies, schemas, delegations, revocation state, and supporting evidence — versioned, tamper-evident, independently verifiable.
Built for sub-50ms global resolution. Agents, APIs, and verifiers fetch current trust metadata without private integrations or manual sync.
Updates create new versions while previous versions remain resolvable — relying parties can determine which trust state applied at decision time.
Records are backed by cryptographic evidence — anyone can verify integrity, history, and active versions without relying only on operator assertions.
We are positioning VDR across three strategic use cases. Each addressing environments where trusted metadata is essential yet insufficiently supported today.
As enterprises deploy agents that call tools, APIs, and other agents across organizational boundaries, a new question emerges: what is this agent trusted to do, under whose authority, and is that authority still valid? VDR helps resolve agent identity, policy, authority, and revocation state at decision time.
Content provenance helps verify where content came from and whether its signed history is intact. But receivers still need governance: which sources, certificate chains, device classes, and revocation rules are acceptable for this workflow today? VDR connects provenance checks to receiver-specific trust policy.
Automated workflows receive approvals from people, systems, or partner organizations — but the receiver still needs to know who issued the approval, under what authority, and whether that authority was valid at the time. VDR makes approvals verifiable, revocable, and auditable across organizational boundaries.
We are shaping VDR around real operational problems and looking for design partners willing to describe their trust and governance pain in depth.
Design partners get early access, direct roadmap input, and the opportunity to shape VDR before it is productized. No commitment required — we are looking for honest conversations about real operational problems.
Request a conversation20+ years building security-critical platforms at tier-1 scale across cloud infrastructure, media security, key management, and low-latency systems. We are now applying that experience to VDR — trust metadata infrastructure for AI systems, governed automation, and cross-organizational trust.
Co-founded KeyOS, a content security platform built for premium media workflows, major live events, and strict reliability requirements.
Led KMS Platform work for European cloud infrastructure: zero-trust architecture, HSM-backed key management, lifecycle operations, encryption, and auditability.
Co-founded BitRipple, focused on loss-tolerant, low-latency transport for real-time and edge systems where reliability is non-negotiable.
We are there to meet organizations dealing with real operational pain around AI governance, digital identity, content authenticity, policy, revocation, or verifiable approvals. If that sounds like your world, let's talk.
Or email directly · contact@fineworklabs.com
20-minute conversations, not sales pitches.