Operations | Monitoring | ITSM | DevOps | Cloud

Introducing the AI Builder Portal - the governed alternative to Lovable and Bolt.new for enterprise. Same one-click builder experience, running on your Kubernetes cluster, under your governance. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

A GPU spec sheet is a confidence trick. It looks like an objective document - numbers, units, comparable rows - but most of the numbers on it don't map cleanly to the performance a real workload will see. Teams that pick GPUs by reading the headline figures usually find out the gap between spec and reality somewhere around the first production run. This is a working guide to reading GPU cloud instance specifications against actual ML workloads. The goal isn't to recommend a card.

The “high cardinality is expensive” sentence has become observability’s version of “in this economy” — said so often that nobody questions whether it’s true. Every vendor pricing page invokes it. Every glossary article repeats it. Every architecture diagram shows aggregation buffers placed before the storage layer.

A company burned $500M in Claude credits because nobody set a limit. Uber exhausted its 2026 AI budget. Microsoft canceled Claude Code licenses. The problem isn't AI - it's the total absence of governance around how people use it.

May has been one of our busiest months yet for Konstruct. Across three releases, 0.5, 0.5.1, and 0.5.2, we've shipped some of the most requested platform-level changes since we launched: a unified model for sharing resources across organizations, native support for AI-driven workflows via MCP, a completely redesigned API keys experience, and a cleanup to how permissions actually work in multi-org environments. Let's walk through what shipped and why it matters.

The video was a product manager who claimed she worked at Netflix. (Her claim, not mine. I have no way of verifying it, and I can’t find the video now.) She was talking about how Netflix now requires every PM to vibe code a working prototype before presenting an idea to engineering. Show, don't spec. Build the thing first. I sat there for about ten seconds being mildly annoyed.

Consolidation is reshaping the experimentation and feature management landscape. Tools are merging, and partnerships are being repackaged as platforms. But marketing a unified experience is not the same as building one. Right now, engineering leaders and product managers are reassessing whether the tools they depend on are built for the long term. It’s irrelevant which vendor has the most products.