On-prem media asset management, on your storage.

The phrase, and the team it actually describes

People search for on-prem media asset management, or for a self-hosted MAM, when they already know the shape they want. The files stay on storage the company controls. The catalog runs nearby, on hardware the company controls. Search, proxies, and metadata are available to the people who make the work, without first shipping the masters to a vendor account.

That phrase is a category. Vaultline is a service that builds a custom media-operations system for one in-house team, around the storage that team already has. The team owns the system. Media Nexus is the part that installs on their hardware and indexes the RAID or NAS in place: frame grabs, tagging, transcription, proxies, and searchable playback, pointed at their folders and their naming.

The teams this is written for are creative pods inside companies. They have a real library and nobody whose full job is the library. They need the archive to be usable by the people who already touch the footage.

What stays on your storage

Originals stay where they are. Indexing is a read of the volumes you approve. Media Nexus does not rename, move, or delete those files. The new material, transcripts, tags, frame grabs, and proxies, is produced on hardware you control and kept as part of the system you own. The camera master does not have to be relocated before anyone can search it.

Self-hosted, in this use, means the system is installed for that team rather than offered as a login to a shared application full of other companies' media. On-prem means the same thing when the hardware and the storage are in the team's own environment. A NAS in an office, a RAID on a studio network, a server the company already administers: the index is built against that, not against an upload folder.

Remote people can still be part of the work. Search, organising, and transfer, without moving the physical drives around, are part of why a team builds the system. Remote access is access to the system you own. It is not an automatic offsite replica of every master. If a proxy needs to travel so someone can review it, that is a copy you choose to send. The library itself remains on the storage you named.

What you can do with it that a folder share cannot

A share is excellent at holding files and poor at answering questions. On-prem media asset management, done as an index of that share, adds the questions.

• Find a line that was said, including when the file was never named for it.
• Find a frame someone remembers. Frame grabs and tags cover shots nobody tagged on the day.
• Play the moment back before an editor opens the master.
• Hand someone a proxy, and keep the edit pointed at the original path. The original stays where it is.

The system is configured to the team's folders, naming, and the way work is handed off. It is not a generic library dropped on top of a volume in the hope that the volume will rearrange itself. Relay is a later build Vaultline scopes for a client after the archive, and drive tracking is one of its features. Remote access is part of every Media Nexus. Review, post, full drive census, verified backup, and automation can be built on the archive afterward. The archive is the base. Those later pieces are scoped per team. They are not implied by the words "media asset management" alone.

What this is not

It is not a cloud MAM, and it is not an offsite host for the masters. It is not a plugin that lives only inside one non-linear editor. It is not a login you rent, where the catalog and the files both disappear if the subscription does. Ownership is the point: you own the system, the media never had to move to create it, and nothing about the archive is held hostage to a monthly seat.

It is also not, by itself, a backup. An index of a NAS tells you what that NAS holds. It does not duplicate the NAS. Drive custody, which person has which shuttle or card, and which of those has not been copied anywhere, is Relay, a later build Vaultline scopes after the archive. Drive tracking is one of its features. Teams confuse the two because both answer "where is the footage." One answers it for files on approved storage. The other answers it for the drives still in people's hands.

How a team gets one

The comparison with a hosted catalog that requires an upload is SaaS MAM versus keeping the files on your storage. The practical version of search, once the files are staying put, is how to search footage on a NAS.

You do not have to buy the system blind and then discover whether your codecs, your folder habits, and your RAID behave. The Free Build builds the Archive Pilot on your real media first. Build before you buy is the intake that gathers what configuring that archive requires, before checkout. If you keep the system, you own it. After the Archive Pilot is what that ownership looks like, and where optional Care fits. Why teams ask to see the archive before they pay is the reason the offer is shaped that way.