Who has the shuttle drive, and which footage is not backed up?

The question the NAS cannot answer

Search on a shared volume answers a question about files that are already on that volume. A content team spends just as much time on a different question. Who left with the shuttle. Which card from yesterday never landed on the share. Which drive on the shelf has a copy of a shoot that exists nowhere else. The footage is not missing from the universe. It is missing from the place everyone is looking.

That is drive custody. A drive is a physical thing in a person's bag, on a desk, or on a shelf. It has a name, a person who last had it, and a relationship to the files that were supposed to be copied off it. When that record lives in someone's head, the library has a hole the size of a commute.

What Relay records

Relay is a later build Vaultline scopes for a client after the archive, and drive tracking is one of its features. It maps drives and custody. It is a record of the drives still in motion, and search of the NAS remains the other half: searching footage that is already on the volume.

• Which person has the drive.
• Which media on it has been seen on the storage you treat as the archive.
• Which media has not been copied there, while the drive can still be found.

A concrete day looks like this. A shoot comes back as two cards and a shuttle. One card is copied to the NAS that night. The shuttle goes home with an editor because the cut starts in the morning. Weeks later a producer asks for the other camera. The share has half the day. Relay's job is to show that the rest was last with that editor, on that drive, and that it has not been backed up, while the drive is still out in the world. The team can go get it. The record is what makes "go get it" possible.

Backup awareness here means a visible gap, not a promise that a copy exists. If a drive's contents have not been seen on the archive storage, the team can see that they have not. That is the information people need when they are deciding what to chase before a shelf gets cleared or a laptop is wiped. It is not a substitute for the backup system you run on the NAS itself. Indexing a volume, and knowing a shuttle was never copied onto that volume, are different facts. You want both.

Inform, and stop there

Relay informs. It does not hard-block. It does not lock a drive, refuse a copy, or stop a person from leaving the building with media on a disk. A custody record that pretended to be a lock would be a different product, and it would fail the first time someone needed to take a drive to a shoot, a grade, or a home edit. The useful behaviour is a clear account: this person, this drive, these files, backed up or not.

That boundary matters when you are deciding what to trust. Relay will not physically prevent a mistake. It will make the mistake visible, which is what lets a producer or an office manager act while the drive can still be found. If you need a door that will not open, that is access control on the rooms and the accounts you already administer. It is not what this module claims to be.

How it sits next to the archive

Media Nexus indexes approved storage in place. The masters that have made it onto the NAS stay there, and search works against them. Relay watches the gap between "shot" and "on the NAS." Together they describe a library that lives on storage you control and a set of drives that are still in motion. Neither one moves the archive offsite, and neither one is a hosted MAM you upload into. The wider category is on-prem media operations, built on hardware the team owns.

Custody also feeds later work. Review and post go better when the files they expect have actually arrived. A missing shuttle is an editorial problem only after it is a tracking problem. Teams that buy search first and ignore the drives often conclude that search "missed" a shot. The shot was never on the volume that was indexed.

How you get it

Build before you buy configures the archive only. Relay is a later build Vaultline scopes for a client after the archive, and drive tracking is one of its features. The Free Build is the path that builds the Archive Pilot on your real media before you pay to keep it. You can read why the build comes before the invoice, and what you own if you keep the system.

If you are comparing this to a tool that wants every file uploaded before it will show you anything, the difference is the subject. Relay is about drives that have not been uploaded anywhere, including to you. Uploading into a SaaS MAM solves a different problem, and it does not tell you whose bag the shuttle is in.