Sustainability

Every delivery ships
with a signed CO₂e
certificate.

Every Studio Munich production ships with a cryptographically signed CO₂e record bound to the client's VoiceIDVault consent protocol. Audit-ready. Tamper-evident. Independently verifiable — no Studio Munich involvement required.

99.9992%Less CO₂e than a full physical shoot
SHA-256Cryptographic hash bound to each certificate
0 kgFreight, set construction, or crew travel
Audit-readyEvery certificate is independently verifiable

How It Works

The CO₂e calculation is derived from the crew roles displaced by AI — not estimated from industry averages.

RolePhysical shootStudioMunich
Director of PhotographyFlight + hotel + day rateReplaced by FLUX pipeline
Photographer€800–2,400/dayReplaced by FLUX generation
Lighting crew (2–4 people)Equipment transport + setupEliminated — scene is synthetic
Art DirectorTravel + day rateReplaced by MIRE mood brief
Stylist + assistantsTransport + day rate × 2Replaced by DXF garment physics
Set constructionMaterials + transportEliminated — environment is synthetic
Hair & Make-upProducts + travel + day rateReplaced by AI talent pipeline
Production ManagerCoordination overheadReplaced by autonomous pipeline

Hybrid mode calculates CO₂e for the physical crew actually deployed — and attests which roles were replaced by AI. Full AI mode has near-zero physical footprint.

Certificate Anatomy

Every field in the certificate is bound to the production record — and the whole payload is SHA-256 hashed at delivery.

FieldDescription
Job IDUUID linking to the production record
ClientConsent record + signed brief reference
Production ModeFull AI / Hybrid / Physical — determines crew footprint
Crew DeployedList of physical roles used (Hybrid mode only)
AI Roles ActivatedWhich physical roles were replaced by AI
Estimated CO₂e SavedCalculated from displaced crew travel + energy
Asset CountNumber of delivered images, videos, documents
Delivery TimestampISO 8601 — moment of final asset delivery
SHA-256 HashHash of the full certificate payload — tamper-evident
Signed ByStudioMunich pipeline attestation key

Example hash

sha256:a3f8d2e1b4c9071f6e2d4a8b3c1e9f07d5b2a4c8e1f3d6b9a2c4e7f1d3b6a9c2

VoiceIDVault Consent Binding

Bound to the Consent Record

Every certificate is cryptographically bound to the client's VoiceIDVault consent ID.

The binding chain begins with the client's signed VoiceIDVault consent record. That consent generates a consent_id — a stable, tamper-evident reference to the talent, scope, and usage rights granted for the production.

When the production completes, the certificate payload includes the consent_id as a required field. The SHA-256 hash is computed across the entire payload — meaning the hash is mathematically derived from the consent record itself.

The certificate cannot be detached from the production. The production cannot be detached from the consent. Any attempt to alter any link in the chain invalidates the hash. Procurement and ESG auditors get a single, verifiable artefact that proves not only what was made — but that it was made with explicit, recorded consent.

Example bound IDs

Certificate ID:cert_a3f8d2e1b4
Production ID:prod_7e2d4a8b3c
Consent ID:vid_consent_9f07d5b2
Bound at:2026-04-12T14:30:18Z
Signed by:attestation-key-prod-eu-1

Independent Verification

Your auditors can verify it themselves.

The certificate payload is a JSON document. The SHA-256 hash is computed deterministically from that payload. Any auditor with the certificate file can recompute the hash and confirm it hasn't been altered since delivery. No StudioMunich involvement required.

01

Receive certificate

Delivered with every production as a signed JSON file

02

Inspect the payload

All fields are human-readable — no proprietary format

03

Recompute the hash

SHA-256 the payload. Compare to the attached hash.

04

Match confirmed

Hash match = document is original. No alterations possible.

Public Verification Endpoint

Verify Any Certificate — From Anywhere

Procurement and ESG teams can verify a Studio Munich CO₂e certificate against the public attestation endpoint without contacting us. Paste the certificate ID. The endpoint returns the attestation key, the SHA-256 hash, and the bound consent record.

Endpoint

GET https://verify.studiomunich.digital/{certificate-id}

How procurement teams use it

  1. 01

    Vendor delivers certificate as part of project handover.

  2. 02

    Procurement queries the verification endpoint with the certificate ID.

  3. 03

    Endpoint returns attestation chain. Cross-reference against vendor invoice.

Download the procurement integration guide (PDF)

Equip your ESG report with audit-grade evidence.

Every production on StudioMunich — from a single catalog shot to a full campaign — ships with a CO₂e certificate. No extra steps. No extra cost.

VoiceCosmos — Design Director

Tap to speak

Studio Munich Assistant
VoiceCosmos
Studio Assistant
Back to top