Not for sale yet.
ClipVault is a free developer preview with no licensing system in it. Rather than publish a price we have not set, here is exactly what the commercial model will be — and the commitments that come with it.
Why there is no price on this page
Publishing a number we have not committed to would be the first thing on this site you could not rely on. When pricing is set it will appear here, and it will be controlled by the commerce layer — never hardcoded into the application you downloaded.
Free to explore, then a 30-day trial you start yourself.
01
Install it, freeNo account, no payment details, no trial started.
02
Sample libraryEvery screen works against packaged sample media. Still no trial.
03
Connect a real libraryPoint ClipVault at your own folder or drive.
04
Start the 30-day Pro trialAn explicit choice you make. This is what starts the clock.
05
Full access, 30 daysThe whole product, on your own archive.
06
Buy and activateUnlocks the install and index you already have.
What we are binding ourselves to.
These are constraints on how licensing gets built, published before the code exists so they can be held against it.
Your work is never held hostage
Trial expiry will never delete, encrypt or lock your library, index, previews or project boards. An expired installation stays browsable.
Buying never means rescanning
A licence unlocks the installation you already built. Re-indexing a large archive is precisely the cost this product removes; charging you it again would be absurd.
Licensing never reads your library
No filenames, paths, metadata or media content will be transmitted by a licence check — occasional revalidation, never a permanent connection.
Pricing lives in the commerce layer
Not hardcoded in the downloadable client, and not duplicated across pages — so a price can change without shipping a new build or leaving a stale number somewhere.
What is not decided.
- Price, and whether it is perpetual with updates or a subscription.
- Whether there is a free tier below Pro, and where the line sits.
- How many machines one licence covers, and how a transfer works.
- Studio and team licensing for production companies with shared archives.
If you run an archive that would use this, the answers get better when they come from real workflows. Tell DGTL what you need before the pricing is fixed.