.png)
Somewhere in your organisation right now, someone is building something with AI. Maybe it's sanctioned. Maybe it isn't. Maybe it's genuinely useful. Maybe it's a six-week project that's quietly on fire. The honest truth is: most of us are making this up as we go – and the ones who tell you otherwise are probably trying to sell you something.
We are living through one of those rare moments where the rules of the game are being rewritten faster than anyone can read them. AI isn't coming. It's here, it's uneven, and it's landing differently in every organisation depending on who's in the room, what they've tried, and how badly the first attempts went.
That's not a criticism. That's just where we are.
The question isn't whether AI will change how your infrastructure is built, how your team works, or how decisions get made. It will. The question is whether you're navigating that change with good information and real experience behind you – or whether you're mostly reading vendor whitepapers and hoping for the best.
The gap between the pitch and the production environment
There is a version of the AI story that sounds very clean. Efficiency gains. Transformed workflows. Competitive advantage. Lower costs. And sure – some of that is real. But the gap between the demo and the production environment is where careers are made and budgets go to die.
The organisations moving well right now aren't the ones who said yes to everything. They're the ones who asked the right questions early: What does this actually cost to run? Who owns it when it breaks? How does this interact with our identity infrastructure? What happens to our security posture when we hand more surface area to a model we don't fully understand?
These aren't philosophical questions. They're Monday morning questions. And right now, a lot of people are answering them alone – or not at all.
The loneliness of making hard calls in a fast-moving field
Here's something that doesn't get said enough: being responsible for IT infrastructure and security in 2026 is genuinely difficult. The threat landscape has shifted. The tooling is changing. The expectations from leadership are rising. And the margin for error is shrinking.
You can read all the reports you want. You can follow the right people on LinkedIn. But there's a kind of knowledge that only comes from sitting in a room with someone who has actually done the thing – who has made the call, lived with the consequences, and come out the other side with something useful to say.
That's the knowledge that's hard to find. And that's exactly what NIC is built around.
What NIC 2026 is actually about
Nordic Infrastructure Conference has been doing this since 2011. Not trends. Not keynote theatre. Practical, technical, honest conversation between people who build and run things for a living.
NIC 2026 is organised around four areas that we think define the next few years for anyone working in IT:
Automation – not automation as a cost-cutting exercise, but automation in a world where AI is actively changing what humans need to do, what they're good at, and where the handoff between person and system actually belongs.
Identity and security – the threat landscape isn't just more dangerous, it's structurally different. AI-assisted attacks, shifting perimeters, increasingly complex access environments. Getting this right isn't optional.
Cloud infrastructure – the platforms are maturing, but the decisions are getting harder. Build vs. buy, on-prem vs. cloud, cost visibility, operational complexity. The easy answers ran out a while ago.
Leadership and AI governance – perhaps the hardest one. How do you lead a team through this? How do you make good decisions when the ground keeps moving? How do you set policy for tools that are evolving faster than your policy cycle?
These aren't separate tracks. In practice, they bleed into each other constantly – which is why the most valuable conversations at NIC tend to happen between sessions, not during them.
The people in that room
What makes NIC different isn't the agenda. It's who shows up.
NIC attracts people who care more about what works in production than what looks good in a presentation. Practitioners, architects, engineers, and leaders who have been around long enough to be sceptical – and experienced enough to know when something is genuinely worth paying attention to.
This year, one of those people is Jeffrey Snover. Creator of PowerShell. Chief Architect of Windows Server and Azure Stack. Now a fellow at the Berkman Klein Center at Harvard, working on AI governance. A man, in other words, who helped build the infrastructure we all run on – and who is now asking hard questions about what should govern what comes next.
He's one of many. But he's a good example of the kind of voice you'll find at NIC: people who have earned the right to have an opinion, and who are generous enough to share it.
You don't have to have it figured out
If you're coming to NIC 2026 with all the answers, you might be at the wrong conference.
But if you're coming because the questions are getting harder, because the pressure is real, and because you'd rather work through it with a room full of sharp, honest people than keep reading the same recycled takes – you're exactly who this is for.
Nobody has the full picture right now. The best any of us can do is stay curious, stay connected, and make sure we're learning from the right people.
That's what October is for.
.png)
The man who built the modern cloud platform is coming to Oslo
Jeffrey Snover is confirmed as keynote speaker at the Nordic Infrastructure Conference, 13–15 October at Oslo Spektrum. This is news that matters – not just because Snover is one of the most influential figures in the history of modern IT, but because he now sits at the centre of the industry’s most important conversation.
Oslo, June 2026
It’s easy to list what Jeffrey Snover has done. Creator of PowerShell. Chief Architect of Windows Server and Azure Stack. Senior technical roles at Microsoft, Google, IBM and DEC across a career spanning more than 30 years. Over 30 patents.
But what makes him an extraordinary keynote speaker in 2026 isn’t the past – it’s the present.
Having stepped down from Google in January 2026, Snover is now a fellow at the Berkman Klein Center at Harvard, where he works on the governance of artificial intelligence. He helped build the infrastructure the IT world runs on. Now he’s helping define what rules it should follow.
Very few people in this industry can say the same.
He was here in 2013 and he hasn’t forgotten it
Snover gave the keynote at NIC as far back as 2013, the conference’s second year. He isn’t coming back because it’s convenient or expected. He’s coming back because NIC is one of the places he actually wants to be.
“I gave the keynote at the second NIC, in 2013, and the room felt like home – pragmatic, deeply technical, and allergic to marketing. These were my people, my tribe. Coming back wasn’t a decision I needed to think about.” — Jeffrey Snover
That’s not a courtesy phrase. It’s a description of what NIC has been from the start: a conference built on substance over spectacle, where less slides, more demos isn’t a tagline – it’s an actual principle.
What he thinks about the Nordic tech community
Snover is candid about why he values this particular audience. In an industry defined by hype and overpromising, he sees the Nordic technology community as a corrective force – a place where value is measured by what works in production, not what sounds good in a deck.
“Amid widespread AI hype, the Nordic tech community is a crucial touchstone to reality. They build for the long term, question assumptions, and measure value by what functions in production. They provide the needle to the Silicon Valley bullshit bubble.” — Jeffrey Snover
That perspective lands hard in 2026, as AI investment and AI promises pour in from every direction – and IT leaders everywhere are trying to separate signal from noise.
Why this keynote matters right now
NIC 2026 is built around the themes that will determine who succeeds in the years ahead: automation in a world where AI is reshaping what people do, identity and security under a rapidly shifting threat landscape, cloud infrastructure evolving faster than most organisations can absorb – and leadership when the pace of change outstrips the pace of the organisation.
Snover’s keynote sits at the heart of all of it. He isn’t an analyst commenting from the sidelines. He’s one of the people who built the systems we’re talking about – and who is now actively working on the question of what governs what replaces them.
What does that mean in practice for IT professionals and decision-makers? Snover is direct:
“AI is changing both what’s possible and the effort required to reach what’s possible – and those goalposts move every quarter. We need to be honest about that, hold our beliefs loosely, and share best practices for the balance that matters most: delivering results today while continually figuring out how AI can help us deliver them better.” — Jeffrey Snover
This isn’t a philosophical question about the future. It’s an operational reality that is hitting budgets and architecture decisions right now.
.png)
Nobody has it figured out. That's exactly why we're getting together in October.
Somewhere in your organisation right now, someone is building something with AI. Maybe it's sanctioned. Maybe it isn't. Maybe it's genuinely useful. Maybe it's a six-week project that's quietly on fire. The honest truth is: most of us are making this up as we go – and the ones who tell you otherwise are probably trying to sell you something.
We are living through one of those rare moments where the rules of the game are being rewritten faster than anyone can read them. AI isn't coming. It's here, it's uneven, and it's landing differently in every organisation depending on who's in the room, what they've tried, and how badly the first attempts went.
That's not a criticism. That's just where we are.
The question isn't whether AI will change how your infrastructure is built, how your team works, or how decisions get made. It will. The question is whether you're navigating that change with good information and real experience behind you – or whether you're mostly reading vendor whitepapers and hoping for the best.
The gap between the pitch and the production environment
There is a version of the AI story that sounds very clean. Efficiency gains. Transformed workflows. Competitive advantage. Lower costs. And sure – some of that is real. But the gap between the demo and the production environment is where careers are made and budgets go to die.
The organisations moving well right now aren't the ones who said yes to everything. They're the ones who asked the right questions early: What does this actually cost to run? Who owns it when it breaks? How does this interact with our identity infrastructure? What happens to our security posture when we hand more surface area to a model we don't fully understand?
These aren't philosophical questions. They're Monday morning questions. And right now, a lot of people are answering them alone – or not at all.
The loneliness of making hard calls in a fast-moving field
Here's something that doesn't get said enough: being responsible for IT infrastructure and security in 2026 is genuinely difficult. The threat landscape has shifted. The tooling is changing. The expectations from leadership are rising. And the margin for error is shrinking.
You can read all the reports you want. You can follow the right people on LinkedIn. But there's a kind of knowledge that only comes from sitting in a room with someone who has actually done the thing – who has made the call, lived with the consequences, and come out the other side with something useful to say.
That's the knowledge that's hard to find. And that's exactly what NIC is built around.
What NIC 2026 is actually about
Nordic Infrastructure Conference has been doing this since 2011. Not trends. Not keynote theatre. Practical, technical, honest conversation between people who build and run things for a living.
NIC 2026 is organised around four areas that we think define the next few years for anyone working in IT:
Automation – not automation as a cost-cutting exercise, but automation in a world where AI is actively changing what humans need to do, what they're good at, and where the handoff between person and system actually belongs.
Identity and security – the threat landscape isn't just more dangerous, it's structurally different. AI-assisted attacks, shifting perimeters, increasingly complex access environments. Getting this right isn't optional.
Cloud infrastructure – the platforms are maturing, but the decisions are getting harder. Build vs. buy, on-prem vs. cloud, cost visibility, operational complexity. The easy answers ran out a while ago.
Leadership and AI governance – perhaps the hardest one. How do you lead a team through this? How do you make good decisions when the ground keeps moving? How do you set policy for tools that are evolving faster than your policy cycle?
These aren't separate tracks. In practice, they bleed into each other constantly – which is why the most valuable conversations at NIC tend to happen between sessions, not during them.
The people in that room
What makes NIC different isn't the agenda. It's who shows up.
NIC attracts people who care more about what works in production than what looks good in a presentation. Practitioners, architects, engineers, and leaders who have been around long enough to be sceptical – and experienced enough to know when something is genuinely worth paying attention to.
This year, one of those people is Jeffrey Snover. Creator of PowerShell. Chief Architect of Windows Server and Azure Stack. Now a fellow at the Berkman Klein Center at Harvard, working on AI governance. A man, in other words, who helped build the infrastructure we all run on – and who is now asking hard questions about what should govern what comes next.
He's one of many. But he's a good example of the kind of voice you'll find at NIC: people who have earned the right to have an opinion, and who are generous enough to share it.
You don't have to have it figured out
If you're coming to NIC 2026 with all the answers, you might be at the wrong conference.
But if you're coming because the questions are getting harder, because the pressure is real, and because you'd rather work through it with a room full of sharp, honest people than keep reading the same recycled takes – you're exactly who this is for.
Nobody has the full picture right now. The best any of us can do is stay curious, stay connected, and make sure we're learning from the right people.
That's what October is for.