Somewhere in your cloud, your SAN and your tape library…

Your next hit is already in your archive. You just can't find it.

Asset Foundry finds every file you own, shows it to you instantly, and puts it back to work: in the DAMs, tools and pipelines you already run. Keep everything. Search once.

Scroll
Act I · The problem

You already paid for this work.
You're about to pay for it again.

Wings, plates, props, sets: made, approved, perfect. Then the show wraps, the drives go dark, and next season someone re-makes what nobody could find. That's not an archive problem. It's a bill that comes back every year.

0%
of everything you've made sits unseen and unused†
$0
of finished work stranded across the industry†
0
files at a single studio, scattered past finding†

† industry estimates. Four weeks with us replaces these with your numbers.

Act II · The answer

Keep everything you own.
Add the layer that makes it work.

Asset Foundry is not another DAM, and it replaces nothing. It reads your storage where it lives, cloud, on-prem, even tape, and quietly does what no single system could: one search, instant previews, files connected to the story they came from.

Your DAM stays the creative front door ShotGrid stays the system of record Your storage stays exactly where it is Read-only to start · nothing migrated
One question finds the file. No re-make. No scavenger hunt.
The cast · Six services, one index

Book one.
Or run the whole crew.

Each deploys solo beside your stack and earns its keep alone. Together they share one memory, one index, one pipeline.

The trailer · One ask reaches the whole studio

One ask reaches the whole studio.

Asset Foundry speaks MCP, the open agent-connector standard. That means one agent platform, like Claude, can orchestrate the entire Foundry: search the catalog, run the pipeline, create on-model, all inside your permissions and logged end to end. Your people ask in plain language. The platform does the legwork.

BEAT 01

Ask the studio

One question in chat: which shots used the hero prop, and is it cleared? The Foundry joins ShotGrid with the script, finds the versions and the rights, and answers with previews. No re-make.

BEAT 02

Run the pipeline

Next ask: ingest and process last night's delivery. The Foundry converts, watermarks and files every shot: checksummed, tagged and tracked all the way to its destination.

BEAT 03

Create on-model

From chat or your creative app: generate the concept pass. Your production context grounds the generation, so images, video and 3D come back accurate to your world, watermarked and audited.

The proof

Studios don't buy promises.
They buy receipts.

Deployed at Warner Bros. across multiple petabytes of production storage.
Runs in your AWS or on-prem. In production deployments, content stays in your environment.SOC 2 Type II aligned. Designed for MPA content-security best practices.Visible watermarking on video, image and document outputs. C2PA Content Credentials on images, with an AI-source assertion.Single sign-on, role-based access, and a full audit trail.Read-only to start. Your DAMs, ShotGrid and storage stay authoritative.
The offer

Four weeks. One production.
Your numbers, not ours.

Pick one production; a wrapped one is perfect. Hand us its ShotGrid export or its screenplay, and it becomes the brain: a queryable map of scenes, shots, cast and versions. The fastest path runs from our cloud on archival data you choose: read-only, single-tenant, deleted and verified at wrap. Or run it in your environment from day one. At the end you keep the context graph, the searchable index and a findings report: time to find, duplicates reclaimed, re-make candidates found, in your numbers, not ours.

Week 1

The brain

Your ShotGrid export or script becomes a queryable context brain: scenes, shots, cast and versions in one graph.

Week 2

The index

We index the production's archive, read-only: checksums on every file, previews for camera RAW, EXR and even legacy 3D, duplicates surfaced. Baseline measured.

Week 3

The pipeline

A test ingestion pipeline runs against the brain: files classified, tagged and routed by context, writing only to a sandbox you name. Sources untouched.

Week 4

The second unit

Agents go on top over MCP: questions that join ShotGrid and the script, on-model generation tests, the pipeline on demand. We walk the findings report with your team.

Nothing to install Sources stay read-only Archival data you choose Deleted & verified at wrap You keep everything we build
Questions

Asked and answered.

What is a media asset orchestration platform?

A media asset orchestration platform is the layer between a studio's storage and its production systems: it indexes files where they live, makes them searchable and previewable, and routes them to the right destination with the right metadata. Asset Foundry by Fortify Media is one example: it indexes cloud, on-prem and LTO tape in place and feeds order into the DAMs and databases a studio already uses. It complements a DAM rather than replacing it.

How do studios find archived footage across different storage systems?

Most studios search each system separately: the DAM, the SAN, cloud buckets and tape catalogs, which is why finished assets get re-made instead of reused. Platforms like Asset Foundry solve this with one search surface across cloud, on-prem and LTO tape, with checksums and metadata on every result and previews for ~140 file formats. One question finds the file wherever it lives, tape included.

Is Asset Foundry a replacement for our DAM or for ShotGrid?

No. Asset Foundry is deliberately the layer between: your DAM stays the creative front door and ShotGrid stays the system of record. The Foundry indexes your storage in place, connects files to their production story, and writes approved metadata back, so the systems you already own stay authoritative and finally work together.

Can AI agents like Claude search a studio's asset library?

Yes, when the library speaks MCP, the open agent-connector standard. Asset Foundry exposes its services over MCP, so an agent platform like Claude can search the catalog, answer questions that join ShotGrid with the script, run processing pipelines, and generate on-model content, all inside the studio's permissions with a full audit trail.

How can a studio use generative AI without losing control of its content?

Keep generation inside a governed platform: run it in your own cloud or on-prem, pin it to local models or providers you approve, and mark every output. Asset Foundry takes this approach, with 60+ generative models behind one API, grounded in your production context, visible watermarking on outputs, C2PA Content Credentials on images, and every job audited.

What file formats can a studio preview without specialist tools?

With Asset Foundry, ~140 formats preview in the browser with no pre-processing: camera RAW, EXR and DPX, broadcast video, audio, multi-page PDF, and 3D models rendered as turntables. Previews generate on the fly wherever the file lives, on S3, Box, NFS, SMB or LTO tape, so dead formats stop being black boxes.

How long does it take to see results from a platform like Asset Foundry?

Asset Foundry's standard pilot is four weeks on one production: week one turns your ShotGrid data or script into a context brain, week two indexes the archive read-only, week three runs a test ingestion pipeline, and week four puts agents on top and delivers a findings report in your numbers. The fastest path runs from Fortify's cloud on archival data you choose, so there is nothing to deploy before starting.

Roll credits

Name the production.
We bring the plan.