Notes from the rooms where AI-native companies get built and funded.
I'm Roderick. A decade making distributed infrastructure reliable, six years running the agency that sold and delivered it — and for the last year I've been in the middle of Zürich's AI-native circuit: 61 events, 31 communities, 467 people logged, from pre-seed founders to the CTOs of the companies they sell to.
This is where I write down what that looks like from the inside — which agent stacks survive production, where inference economics break, and what founders ask for that nobody is building yet.
- AI-native or AI-enabled? The question that decides how a partnership will go
The difference between a company that cannot exist without a model and one that bolted a chatbot onto a working product is not semantic. It predicts the workload, the org, the burn rate and the entire shape of a partnership.
Analysis - Six years of rooms: what DevOpsDays Zürich taught me about networks
I co-founded Switzerland's first DevOpsDays and ran it for three years. The lasting asset wasn't the event — it was learning how a room turns into a network.
Field noteDevOpsDays Zürich - Evals are the release gate enterprise AI is still missing
Every enterprise AI programme I see has a demo that works and no way to prove it still works tomorrow. That's not a model problem — it's a missing release gate.
Analysis - Open vs. closed models is a procurement argument wearing a technical costume
An evening of founders and cloud partners debating how the next generation of startups gets built. My position afterwards — not a report of what was said.
Field noteOpen vs. Closed Models · VentureLust × Snowflake × AWS × DataMax - Kubernetes in 2015, agents in 2026: the same graph, new nouns
The adoption curve for agentic AI is tracking the cloud-native curve almost exactly — including the part where everyone deploys something nobody can operate.
Analysis - What AI-native founders should know before their first serious GPU bill
The moment an AI-native startup stops paying per token and starts paying for capacity is the moment its engineering culture gets tested. Most teams arrive unprepared, and the fix is boring.
Analysis