For post production, VFX, editorial and DI

Ingest the whole drop.
Down to the last frame.

Vendor deliveries land whole or not at all, transcodes run on GPU that scales back to zero when the queue empties, and every shot reaches the right DAM with its metadata already attached. Prove it on one show in a four-week pilot, on archival data you choose.

For your team:Marketing & BrandArchive & LibraryPost & VFXProduction TechnologySecurity & ITThe studio tour
The daily friction
✗The vendor drop is 40,000 EXRs over Aspera and I have no idea if all of them actually made it before I conform against it.
✗Half my night is watching the render farm instead of cutting, and an idle node still shows up on the bill.
✗The shot is in, the proxy is made, and ShotGrid still has no idea the metadata exists.
What changes for you
01

A shot lands whole or not at all

Frame sequences assemble atomically with checksum-verified ingest over Aspera or S3. A per-file delivery event stream tells you exactly what arrived, so you never conform against a sequence that is quietly missing frames.

02

No farm to babysit

Elastic GPU fleets scale from zero to N and back to zero as the queue rises and drains. Thirteen job types cover video, image, 3D, audio and documents, so ProRes and DNxHR transcodes, proxies and conforms run without a night-shift babysitter or idle nodes on the bill.

03

Metadata routes itself

Finished shots route into 5th Kind or ShotGrid with their metadata attached, mapped to the MovieLabs 2030 OMC data model. The DAM stays the system of record; the Foundry just makes sure it actually gets told.

04

See the plate without pulling it

Turntables and EXR, DPX and camera RAW previews render in the browser with no plate dragged off storage. Video previews read about 50x lighter than a full fetch in our tests, so scrubbing a fresh delivery does not crawl.

Your part of the stack

The pieces that earn their keep for post production / vfx / editorial / di.

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

Nexus

Checksum-verified vendor ingest that assembles frame sequences atomically over Aspera or S3, streams a per-file delivery event so you can see exactly what landed, and routes finished shots into 5th Kind or ShotGrid. A half-ingested shot never reaches your timeline.

Explore Nexus →

Forge

13 job types across video, image, 3D, audio and documents on elastic GPU fleets that scale from zero to N and back to zero. ProRes and DNxHR transcodes, proxies and conforms, 60+ models, with visible watermarking and C2PA Content Credentials on outputs. No render farm to babysit.

Explore Forge →

Lens

Turntables plus EXR, DPX and camera RAW previews in the browser, no plate pulled off storage. Video previews read about 50x lighter than a full fetch in our tests, so reviewing a vendor drop does not drag the whole bay down.

Explore Lens →

Gateway

A live queue of every ingest, transcode and conform in flight, plus recovery ops with dry-run and undo. When a delivery stalls at 2am you see where it broke and roll it back cleanly, instead of re-running the whole batch and hoping.

Explore Gateway →
A day in the life

One vendor drop, from Aspera to conform, with every frame accounted for.

STEP 01

The delivery lands

A vendor push arrives over Aspera or S3. Nexus verifies checksums file by file, assembles the frame sequence atomically, and emits a per-file delivery event stream. The sequence is either complete or flagged; nothing half-ingested slips through to editorial.

STEP 02

Forge does the heavy lifting

Transcodes, proxies and conforms fire across 13 job types on GPU that spins up for the batch and scales back to zero when it drains. ProRes and DNxHR come out the far side, watermarked and with C2PA on the renders, without a single node babysat.

STEP 03

Everything routes itself

Finished shots route into 5th Kind or ShotGrid with metadata mapped to the MovieLabs 2030 OMC model, while Lens serves EXR and DPX previews for review. The conform starts against a delivery you can trust, not one you have to spot-check by hand.

Questions
What happens if a vendor delivery is missing frames?

Nexus ingests frame sequences atomically with checksum verification on every file, so a sequence lands whole or it is flagged before it reaches editorial. A per-file delivery event stream shows exactly what arrived over Aspera or S3, which means you never quietly conform against a shot that is missing frames.

Do I still have to babysit the render farm?

No. Forge runs 13 job types across video, image, 3D, audio and documents on elastic GPU fleets that scale from zero to N and back to zero as the queue rises and drains. Transcodes, proxies and conforms in ProRes or DNxHR run unattended, and idle nodes do not sit on the bill overnight.

Can I preview EXR and DPX without pulling the full plate?

Yes. Lens renders EXR, DPX and camera RAW previews, plus 3D turntables, in the browser with no plate pulled off storage. Video previews read about 50x lighter than a full fetch in our tests, so scrubbing a fresh vendor drop stays fast even across a large delivery.

Does the metadata actually make it into ShotGrid?

Nexus routes finished shots into 5th Kind or ShotGrid with their metadata attached, mapped to the MovieLabs 2030 OMC data model. The DAM and ShotGrid stay authoritative as the system of record; the Foundry makes sure the shot and its metadata land together instead of the metadata going missing at the handoff.

Prove it on your own work

Four weeks. Your team's numbers.

See the four-week pilot → Back to the studio tour