Assets stay in the facility
Frames, geometry and scene data never leave the network. Only hashes cross the boundary, which is what makes this workable on an unreleased show.
Studios want VFX labs to prove their pixels.
Evidence of what went into a delivery: which elements were licensed, which were generated and by whom — declared as part of the provenance, without assets ever leaving the facility.
Frames, geometry and scene data never leave the network. Only hashes cross the boundary, which is what makes this workable on an unreleased show.
Keys are held in hardware and managed for the studio, so nobody on the pipeline team is standing up infrastructure to make this work.
The provenance a client or a platform reads is the same open standard the rest of the industry is adopting, not a studio-specific format.
Native support for the formats, and the metadata inside them.
C2PA does not cover these formats natively. We do — full metadata extraction, content hashing and sidecar manifest generation for each.
.EXR
Resolution, channels, layers, compression, chromaticities
.ABC
Frame range, object hierarchy, geometry types, animation
.USD
Layers, prims, time codes, stage metadata, references
.FBX
Node hierarchy, animation stacks, meshes, materials
A lightweight agent, and a hard network boundary.
The agent runs inside your network. Files stay local, the record is written in the cloud, and the only thing that crosses is a hash.
Your network
Across the boundary
Noosphere
Enterprise-ready from day one.
Provenance is captured when work is submitted, so artists carry on as they are. Nobody adds a step, and nothing depends on remembering one.
Whole sequences are handled in one operation, with related files linked rather than treated as strangers.
Attach union memberships, studio certifications and project roles. Prove not just what was made, but who made it and under what authority.
Where a shared platform is not an option, dedicated deployment and isolation options are handled directly with our team.
Set it up once, and it follows the work.
The agent runs inside the facility, hooks into the submission step the studio already uses, and writes provenance alongside the files. It can be driven from the command line or from the pipeline code that already moves the work.
Version control
Attaches to the submission step
Local agent
Runs inside the facility
REST API
Language agnostic
CLI
Scriptable in any pipeline
Tell us how your pipeline is put together and where the work travels, and we will show you what attesting it looks like in practice.