ClipVault is not shipping yet.
It is a working developer preview: real scans, real metadata, real visual search — running every day against a 17,000-asset archive. What it does not have yet is an installer, which is the honest reason there is no download button on this page.
Tell us about your archive and we will bring you in as builds become installable. In the meantime the live demo runs the whole workflow in your browser, right now, with no signup.
No account, no payment details, no trial started. Version — · developer preview · macOS —
What you get
A build, the setup steps, and a direct line to the people making it. Early access is free, and it stays free for the whole preview — there is no licensing system in the app to charge you with.
What we ask
That you point it at a real archive and tell us where it struggles. Preview software earns its keep by breaking in front of the people who wrote it.
What it costs you
Nothing, and no risk to your media. ClipVault opens originals read-only and writes its index somewhere else entirely — that guarantee is not a preview caveat, it is the design.
Tell us about your archive.
Two fields are required. The rest helps us bring in the archives that will actually stress the thing — which is how you get a build sooner, not later.
Application received.
Thank you — that is with us. We read every one, and we will be in touch as builds become installable. Nothing else happens in the meantime: no mailing list, no drip sequence, no account was created.
While you wait, the live demo runs the full workflow on a sample archive.
What happens next.
- A person reads it
Not a scoring model and not an autoresponder. The list is small enough that this is still true.
- We match you to a build
Archives that stress a particular part of the pipeline — enormous RAW libraries, multi-drive event archives, mixed codec estates — go out first, because that is where the preview learns most.
- You get setup steps and a direct line
Including the parts that are rough. You will hear what does not work yet before you find it yourself.
- Nothing else happens
No mailing list, no drip sequence, no account. If we have nothing useful to send you, you hear nothing.
Where the build actually is.
Read from the same release manifest the rest of the site uses, so this cannot drift out of step with reality.
Loading release details from the manifest…
Release details unavailable
Known limitations
- Loading from the release manifest…
Why there is no installer
The app today is a window wrapper that runs from a source checkout — it expects a Python environment and a built interface beside it. Packaging that into something self-contained and signed is real work, and it is the milestone standing between this page and a download button. When it lands, this page gets one.
What you will need.
Minimum is what the application needs to run. Recommended is what a large archive needs to run comfortably.
Minimum
| Loading from the release manifest… |
Recommended
| Loading from the release manifest… |
Supported formats
Loading from the release manifest…
Your archive, during a preview.
Read-only is not a preview caveat
ClipVault never deletes, moves, renames or writes into your source media. That is the architecture, and it does not get relaxed because the software is early.
Nothing is uploaded
There is no code path that sends your library anywhere, and no telemetry in the app. A preview build does not phone home about what you scanned.
Your index survives updates
Migrations are versioned and rescans are idempotent, so moving to a newer build refreshes what changed instead of re-indexing everything.
Leaving costs one folder
Delete the app and ~/.clipvault/. Your media is exactly where it was, untouched, because it never moved.