For color, DI, finishing and deliverables

See the exact frame.
Deliver the exact spec.

Lens shows you the precise frame in RAW, EXR or DPX right in the browser, Forge conforms it to ProRes or DNxHR on GPU that scales back to zero, and every review copy leaves watermarked. So the frame you sign off is the frame you deliver, and no ungoverned copy floats out of the bay.

The daily friction
I graded to the frame I saw in the browser, then the DPX came back looking nothing like it.
Every client wants a different spec, and I find out I got one wrong when it bounces back a day later.
Review copies are floating around unwatermarked and nobody can tell me who still has them.
What changes for you
01

Grade the frame you actually deliver

Lens previews the exact frame in the browser across camera RAW, EXR and DPX, no restore and no round trip to the bay. Video previews read about 50x lighter than a full fetch in our tests, so scrubbing a 4K master to the one frame you need does not stall your session.

02

Conform to spec, not by hand

Forge runs ProRes and DNxHR conforms, proxies and transcodes across 13 job types on elastic GPU that scales from zero to N and back to zero. The spec is a job you fire, not a queue you babysit, and idle nodes do not sit on the bill overnight.

03

No review copy leaves ungoverned

Every output Forge produces carries visible watermarking on video, image and document, and images carry C2PA Content Credentials with an AI-source assertion. Review copies leave the bay traceable by default, so a leaked frame is never an anonymous one.

04

Every deliverable tracked to its destination

Nexus routes finished deliverables into ShotGrid or 5th Kind with checksum verification and a per-file delivery event stream. You see exactly what landed where, so a wrong-spec or half-delivered master never reaches a client without you knowing first.

Your part of the stack

The pieces that earn their keep for color, di, finishing & deliverables.

Book the ones that fit your team, or the whole platform. Each shares one index.

A day in the life

One deliverable, from source master to signed-off spec

STEP 01

Start from the right master

Gateway searches cloud, on-prem and LTO tape at once and hands back the graded master or plate with its checksum, so the DI starts against the file you meant, not a lookalike copy. Read-only by design, so pulling the source can never change it.

STEP 02

See it, then conform it

Lens previews the exact frame in the browser across RAW, EXR and DPX, so you confirm what you are working with before you commit. Forge conforms it to ProRes or DNxHR across 13 job types on GPU that spins up for the batch and scales back to zero when it drains.

STEP 03

Watermark, route, done

Forge returns review copies with visible watermarking on video, image and document, and C2PA Content Credentials on images. Nexus routes the finished deliverables into ShotGrid or 5th Kind with a per-file delivery event stream, so every copy leaves traceable and lands where it should.

Questions
Can I preview the exact frame in EXR or DPX without pulling it into the bay?

Yes. Lens previews about 140 formats right in the browser, including camera RAW, EXR and DPX, generated on the fly wherever the file lives with no restore and no pre-processing. Video previews read about 50x lighter than a full fetch in our tests, so you can scrub a 4K master to the exact frame without dragging the whole plate off storage or tying up a specialist seat.

How do I conform to ProRes and DNxHR without babysitting a render queue?

Forge runs ProRes and DNxHR conforms, proxies and transcodes across 13 job types on elastic GPU fleets that scale from zero to N and back to zero as the queue rises and drains. The transcodes run unattended, so you fire the spec and get on with the grade instead of watching a farm, and idle nodes do not sit on the bill overnight.

How do I stop review copies from leaking ungoverned?

Every output Forge produces carries visible watermarking on video, image and document, and images additionally carry C2PA Content Credentials with an AI-source assertion. Review copies leave the bay traceable by default rather than as anonymous files, so when a frame turns up somewhere it should not, you can tell where it came from.

How do I know a deliverable actually reached the client in the right spec?

Nexus routes finished deliverables into ShotGrid or 5th Kind with checksum verification on every file and a per-file delivery event stream, so you see exactly what landed where instead of assuming it went through. The fastest way to prove it on your own masters and specs is the four-week pilot: one facility, read-only, findings in your numbers.

Prove it on your own work

Four weeks. Your team's numbers.