Who built Veluvanto — and why

My name is Tomáš. I've spent over ten years building and securing server infrastructure for large companies. Data protection isn't a buzzword in my world — it's an engineering requirement I deal with every day.

Even so, I kept finding myself in the same situation: an evening, a document I needed, and no idea where it was. A warranty receipt for an appliance I needed to return. An invoice I couldn't reconcile. A lease agreement I just needed to check one number in.

Ten, maybe twenty minutes gone. The kids were already in bed by the time I found it. Not a crisis — just that quiet, grinding frustration of time you didn't mean to spend.

Looking for a tool that didn't exist

I looked for something that already solved this. Document management systems exist, but they're designed for enterprise IT departments — lengthy rollouts, dedicated administrators, budgets that don't fit a person's home office. Not exactly something you set up on a Sunday afternoon.

Cloud storage is the simpler alternative. But it's just that — storage. A folder structure you maintain yourself, with no understanding of what's actually inside your files. And with most providers, you have no real idea which continent your data is sitting on, let alone what legal framework governs it.

So I built it myself

So I built Veluvanto. Because I needed it to exist.

The privacy side of it mattered to me as much as the functionality. I work with sensitive infrastructure for a living, and I wasn't comfortable with the vague assurances most cloud services offer. Veluvanto runs on EU servers, under EU law. The AI reads your document, pulls out the relevant data, and that's the end of it — nothing is stored beyond what you put there, nothing is used to train models.