Search footage on the NAS you already have.

The footage is already on the share

In-house content teams rarely start from an empty volume. The library is already on a NAS or a RAID. Editors mount it every day. Premiere and Resolve projects already point at those paths. What fails is finding a shot when the only record is a folder name, a spreadsheet, or the person who was in the room when it was shot.

Uploading that library just so it can be searched treats the archive as if it had no home. A second full copy, in an account the team does not control, is a migration before anyone has answered a question. If the team means to keep mastering on the storage it already runs, search has to run against that storage.

What indexing in place means

Media Nexus is installed on hardware the team controls and pointed at the approved volumes. It reads them, indexes approved storage read-only, and never renames, moves or deletes originals. Transcription and tagging run on hardware the team controls.

The pieces that make footage findable are created beside the masters. Frame grabs give a picture of a moment. Tags record what a pass over those frames decided the picture contains. Transcripts record what was said, with a way back to the timecode. Proxies give a producer a file they can play and hand off without pulling the camera original off the RAID for every check. Searchable playback is how someone confirms the hit before an editor opens the master.

None of that asks the master to change address. The original stays on the volume. The index records where it is.

What you can ask

A folder name answers which card a clip came from. A useful search answers the questions people actually bring to a library.

• A sentence from an interview or a stand-up. Transcript search returns the line and the time.
• A frame someone remembers: a product, a room, a hand. Frame grabs and tags cover shots nobody named on the day.
• A check before the edit. Playback confirms the take, and the result points at the file already on the storage the edit uses.

Proxies keep review light. They are not the archive. The archive is still the files on the storage you approved.

What the edit keeps

Editors keep mounting the same share. The index is a reading of that share. You do not start by exporting a selection, waiting on an upload, and hoping the uploaded copy is the one next month's project will relink to. You start by granting read access to the volumes that are actually the library, and by saying which volumes are scratch and should be left alone.

A result locates a moment and the file that holds it. Opening the master, or handing the existing path to an editor, still uses the storage you already operate. If people off-site later need to search, or to pull a proxy, that is access to the system you own and to the files you choose to expose. That decision is separate from copying every master off the premises so a hosted catalog can see them. On-prem media asset management is that shape in full. A SaaS MAM that uploads media, set against indexing the storage you have, is the tradeoff.

When the shot is not on the NAS

A search of the share only sees the share. A shuttle on an editor's desk, a card that never cleared ingest, a copy that lives on one laptop: none of those become searchable because the NAS was indexed. Those are custody questions. Which person has which drive, and which of those drives has never been backed up, is what Relay is for. Relay is a later build Vaultline scopes for a client after the archive, and drive tracking is one of its features. Indexing the volume and knowing where the other copies are close different gaps. Most teams have both.

The same limit runs the other way. An index does not back the volume up. It tells you what is on the volumes you approved. Protecting those volumes is still a storage decision you make on purpose, on the hardware you already trust. Where those copies sit is how to archive the footage and still find it.

Who it is for, and how a build starts

This is for in-house content and creative teams whose library already lives on storage they control. The pain is the shot only one person can find, footage that exists and still cannot be reused, and a library that gets harder as it grows. It is not aimed first at broadcasters, and it is not a plugin inside one editing application. Editors keep the tools they already cut in.

A build needs three things from the team:

• Read access to the storage you want indexed.
• A computer the team controls for the system to run on. A Mac is enough, and we can help specify one.
• A person who can say which folders are the archive and which are scratch.

The Free Build builds that archive against your real media before you decide whether to keep it. Build before you buy is the intake that configures the archive before any payment. Why the archive is built first is the offer in plain language. What you own if you keep it covers the system afterward, including optional Care.