VediramWe build the tools we wanted back when we ran other people’s IT.
Vediram is a small company in Lausanne: a founder and a couple of people, working on Windows software for organisations that have to answer for what runs on their machines.
We spent years on the other side of that work: deploying, operating and defending Microsoft 365 estates inside real organisations, and being the ones asked what happened when something went wrong. That is where the company comes from, and it is still who we write software for.
Software arrives with no way to control it
A department buys something. It gets installed on a few thousand machines. Then someone asks the obvious questions: who can use it, what can it reach, what did it do. There is no way to answer, because nobody built one. The vendor shipped the feature and left the governance to whoever has to run it.
We watched that happen enough times to stop treating it as bad luck. It is how the market works: the cost of the missing controls never lands on the people who decided not to build them. It lands on the enterprise, months later, usually at the worst moment.
So we build the half nobody ships.
Control exists so you can say yes
Most governance software is built to forbid. We think that is a failure of imagination. The point of knowing exactly what a piece of software can reach is that you can then let people use it, deliberately, with the blast radius drawn in advance, instead of blocking it outright because the only alternative is blindness.
Which follows from something simpler: the person at the keyboard is not the adversary. They are trying to get their work done with the tools they were given. Software that treats them as the threat gets routed around, and the organisation ends up with less visibility than before, not more.
And we would rather make small software that does one thing properly than a platform that does twenty things adequately. The suites get bought; the focused tools get used.
The same problem, three desks
It reaches the security lead first, as a question they are under pressure to answer yes to and no honest way to. It reaches the administrator as a blanket restriction they have to enforce and defend, and as the ticket they cannot close because nothing recorded what happened. It reaches the person just trying to work as a tool that is blocked, or broken, for reasons decided several floors above them.
We have sat at all three desks. Everything we build is judged on whether it makes that chain shorter.
Slow underneath, close to the people using it
The foundations take as long as they take. Enforcement that holds is unglamorous work. There is no demo in it, and it is the only part that matters when someone leans on it. We would rather spend a season getting that right than ship something that looks finished and gives way under a real environment.
Above that line we move fast, because we are small enough to talk to the people using our software directly. No account managers in between, no roadmap committee. If something is wrong in your environment, you tell us and it changes in weeks.
Lausanne
We are on the shore of Lake Geneva, and the place has rubbed off on the company. Swiss engineering culture rewards a long horizon and a quiet one: build the thing precisely, keep what you were told to yourself, do not confuse noise with progress.
It suits us. We are not in a hurry to be famous, and our customers are not looking for a vendor who is.
Julien Nury
Founder
“I got tired of explaining to people why the software they had just bought could not be governed, so I started building the part that was missing.”
Come and build it with us
We work with a small number of design partners: organisations that tell us plainly what is wrong in their environment and get a direct line to the people writing the code, real influence over what gets built, and early access when it ships. If any of this sounds like your problem, write to us.
We respond within two business days. No commitment required.