Why we built Vanday
Every small creative team hits the same wall.
You start with a folder. Then a folder of folders. Then a shared drive with FINAL, FINAL_v2, and FINAL_actually_use_this. Somewhere in there is the exact shot you need for tomorrow’s post — you just can’t find it, and the person who can is on vacation.
The tools meant to solve this — digital asset managers, or “DAMs” — were mostly built for large enterprises. They assume you have someone whose job is to tag and organize everything, a procurement cycle to buy the software, and an IT team to run it. For a five-person studio, that’s the wrong shape entirely.
The boring bits should be automatic
We built Vanday on a simple bet: the organizing work that nobody wants to do should happen on its own.
- Auto-tagging. Upload an image and Vanday looks at it, describes what’s in it, and tags it — so search actually works without anyone labeling a thing.
- Smart cropping. It finds the subject of a photo (the face, the product, the focal point) so a crop never lops off someone’s head.
- One search away. Type what you remember — “the rooftop shot from the spring campaign” — and get it back, instead of scrolling through thumbnails.
The goal is that your library gets more organized as you use it, not less.
Built for teams, not institutions
Vanday is priced and shaped for small teams. Viewers — clients, freelancers, the whole agency — are always free. You invite who you need, share what you want, and skip the parts that only make sense at a thousand-person company.
What’s next
We’re in open beta right now, and it’s free while we’re there. This blog is where we’ll share what we’re learning — about asset management, about building a small software product, and about the workflows that help creative teams spend more time making things and less time hunting for them.
If that sounds useful, try the beta. We’d love to hear what you think.