After the archive is built, do you own the system?

The pilot is a real archive, then a decision

Vaultline builds your Media Nexus archive first, on the storage you already have, against your real media. When the build is done, you use your own volumes, your own projects, and your own naming. Then you decide whether to keep it.

If you walk away, there is no invoice. If you keep it, you own the system. The keep price is $4,669, fixed in writing before the build. What follows is what you own, and what continues only if you want it to.

What you own

You own a media-operations system installed on hardware you control. Media Nexus has indexed the approved storage in place. Originals are still on that storage. The index, the transcripts, the tags, the frame grabs, and the proxies are part of the system you own, not a catalog locked inside a subscription. Nothing is rented, and nothing is held hostage. Stopping a later engagement does not switch the archive off.

A kept archive is $4,669. It includes the archive, configuration, install, orientation, and 90 days of free Care. Remote access is part of every Media Nexus, not a later build. The archive also includes AI tagging, search, semantic search, proxy generation, and collections. Relay is a later build Vaultline scopes for a client after the archive, and drive tracking is one of its features. Full drive census, verified backup, and automation are later builds. After you decide to keep it, you pay $4,669 in the portal, then you sign up for Care, and only then does the install become visible. The 90 free days are that Care signup. If you already bought the paid Media Operations Blueprint, that fee is credited against the keep price. Buying the Blueprint first is not required.

What Care is, and what it is not

Care is optional ongoing care for the system you already own, at $600 per month. After those 90 free days, some teams want Vaultline to keep the install steady: the same system, still on their hardware, still pointed at their storage. Partner, at $1,800 per month, is the deeper relationship: proactive recommendations, roadmap ownership, priority access, and continuous improvement inside the modules you own. You can keep searching, playing, and using the archive with neither. Declining them leaves the system in your hands.

What can be built after the archive

The archive is the base. Remote access is part of every Media Nexus, not a later build. Relay is a later build Vaultline scopes for a client after the archive, and drive tracking is one of its features. On top of the archive, a team can ask for the operational pieces the library still lacks. Full drive census, verified backup, and automation are later builds. Each one is its own scope.

• Review, so approvals have a home other than chat.
• Post, as awareness of NLE projects and exports, so the cut and the archive know about each other.
• A full drive census and verified backup through Relay, a later build, so a drive that was never indexed, and a second copy, are a record. Drive tracking is one of Relay's features.
• Automation, for the steps a person should not be repeating by hand.

If a capability does not exist yet, it can be built. Each of those is its own scope. The pilot does not pretend to be all of them. Teams that treat the pilot as a finished media department will be disappointed, and teams that treat it as a rented login will have misunderstood what they kept. It is the searchable archive of their media, on their hardware, which they can then extend.

What you need in order to reach that decision

Reaching that decision takes four things:

• Read access to the storage you want indexed.
• A Mac to run it on, or help specifying one.
• A short fit call.
• A person who can make the keep-or-walk-away decision.

The intake that configures the archive before any payment is Build before you buy. How search works once the files stay put is searching footage on a NAS. Where the system runs is on-prem media asset management. Why the archive exists before the invoice is the archive built before you pay. The comparison with uploading the library into a hosted tool is SaaS MAM versus keeping the files.

After the pilot, the useful sentence is short. You own the system. Care is optional. The media never had to leave the storage you already had.