Founder
Hi, I'm Igor.
I'm building VeloSecurity AI — deterministic security infrastructure for AI agents.
Oslo · working across EMEA & AMER
Why I'm building this
Agents need infrastructure, not better prompts
Every wave of cloud, mobile and IoT, I've watched the same pattern: a powerful new compute model ships first, and the security and governance infrastructure shows up years later — at much higher cost.
AI agents are the next wave, and we're repeating the mistake. Most "agent security" today is a prompt asking an LLM to behave. That's not a control plane — it's a wish.
VeloSecurity AI exists to put deterministic policy enforcement — DNS-native identity, CEL evaluators, control-plane / data-plane separation — between agents and the systems they touch. The architecture has to be infrastructure. The infrastructure has to be deterministic.
What I'm shipping
DNS-AID
Infoblox · Patent filed · IETF draft contributor
At Infoblox I lead DNS-AID — an IETF-based standard for DNS-native agent identification and discovery. Built the full reference platform end-to-end: Python core library, CLI, MCP server, FastAPI directory, Next.js frontend, AWS serverless. Governance via DNSSEC, DANE/TLSA, JWS and CEL policy.
VeloSecurity AI builds on this foundation — taking the same deterministic primitives and making them deployable for any enterprise running agents in production.
Background
How I got here
I started in service provider networks — IP/MPLS cores, microwave backhaul, the unsexy plumbing that everything else runs on top of. Then a decade of multi-cloud and SD-WAN at Airbus, VMware, AWS, Aruba and Prosimo (which Palo Alto acquired in 2025) — building the architectures that connect AWS, Azure and GCP for enterprises that can't afford to get it wrong.
Along the way I've influenced over €150M in deal value, presented at VMworld, built and led pre-sales teams across EMEA, and earned the rare distinction of CCDE alongside AWS Professional and Azure Expert. None of that matters on its own. What it adds up to is a pattern: I keep ending up where networking, security and emerging compute models meet.
AI agents are where they meet next. Hence DNS-AID. Hence VeloSecurity AI.
Writing
Selected posts
Connect
Talk to me
If you're running agents in production, evaluating governance, or just want to argue about whether DNS belongs in the AI stack — I'd like to hear from you.