Why We're Building Vidi
The problem every editor knows
You just got handed 2TB of footage from a three-day shoot. The deadline is Friday. Before you can even start cutting, you need to find the good takes, figure out what was shot where, and somehow remember which clip had that perfect reaction shot you noticed while ingesting.
This is the reality for every video editor, every project, every time.
What “library intelligence” means
We’re not building another media asset manager. We’re not building a search bar bolted onto a file browser. We’re building something that understands your footage the way a great assistant editor would — watching everything, remembering everything, and answering questions in plain English.
“Find the sunset shots from day two where Sarah is talking about the renovation.”
That’s not a search query. That’s how you talk to a human who’s watched all the footage. That’s what we’re building.
Local-first, always
Your footage never leaves your machine. The AI analysis runs through our cloud API, but only extracted frames and audio segments are sent — never your original files. And those are processed in real-time, never stored.
✨ Tip
Vidi works offline for everything except AI analysis. Your library, metadata, and search all run locally.
What’s next
We’re launching with a small founding group of editors who want to shape what Vidi becomes. If you’ve ever lost hours to footage management instead of actual editing, we built this for you.
Search isn’t keyword matching — it’s semantic understanding. You can search for “person walking on beach at sunset” and find clips that match the visual concept, even if nobody tagged them.
Join us
We’re looking for founding members — editors who want to help build the tool they’ve always wanted. Reserve your spot.