For visual effects studios
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.
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.
No cryptography to run
Keys are held in hardware and managed for the studio, so nobody on the pipeline team is standing up infrastructure to make this work.
Recognised outside the studio
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 format support
Native support for the formats, and the metadata inside them.
C2PA has no native support for these formats. We do — full metadata extraction, content hashing and sidecar manifest generation for each.
.EXR
OpenEXR
Resolution, channels, layers, compression, chromaticities
.ABC
Alembic
Frame range, object hierarchy, geometry types, animation
.USD
Universal Scene Description
Layers, prims, time codes, stage metadata, references
.FBX
Filmbox
Node hierarchy, animation stacks, meshes, materials
Architecture
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
Where the work lives
- VFX files on local storage
- noosphere-vfx agent
- Sidecar manifests written beside the files
Across the boundary
Only SHA-256 hashes
- No pixels
- No geometry
- No animation data
- Nothing an NDA would cover
Noosphere
Provenance service
- HSM-backed key custody
- Attestation policy per show or team
- Trust graph evaluation
Features
Enterprise-ready from day one.
Attaches to submission
Provenance is captured when work is submitted, so artists carry on as they are. Nobody adds a step, and nothing depends on remembering one.
Built for sequence scale
Whole sequences are handled in one operation, with related files linked rather than treated as strangers.
Verifiable credentials
Attach union memberships, studio certifications and project roles. Prove not just what was made, but who made it and under what authority.
High-security environments
Where a shared platform is not an option, dedicated deployment and isolation options are handled directly with our team.
Install
Set it up once, and it follows the work.
Drops into the pipeline you already run
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.
# One line per shot, or one trigger for the whole depot
noosphere attest shot.1001.exr
noosphere attest --sequence "shots/ep01_sh040/*.exr"
Version control
Attaches to the submission step
Local agent
Runs inside the facility
REST API
Language agnostic
CLI
Scriptable in any pipeline
Prove your pixels without slowing delivery.
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.