Operations | Monitoring | ITSM | DevOps | Cloud

We’ve rolled out a small but useful improvement to the Status Page → General settings. Previously, the Support contact field in the footer only accepted: Based on feedback from our users, the field now also supports phone numbers. Status pages in StatusGator already offer a variety of customization options – including custom branding, layouts, monitor visibility, subscriber settings, and privacy controls.

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.

If you serve LLMs on Kubernetes without inference-aware routing, your load balancer is likely wasting inference capacity. Generic HTTP traffic management blindly routes requests, assuming the backends in your cluster are interchangeable. But your model-serving backends are stateful and unevenly prepared to handle any given request. As a result, requests are often routed to the backend that’s not the one best suited to respond.

The first post in this series explored why traditional observability breaks down in hybrid cloud environments. As infrastructure, applications, and dependencies stretch across on-premises networks and cloud services, isolated monitoring views leave teams with an incomplete understanding of what is happening and why. That challenge raises the next question: what kind of operational model actually works in a hybrid environment?

AI agents can write code faster than any developer. But for most teams, the feedback loop hasn’t kept pace. The agent generates code, pushes it to CI, and minutes later a full pipeline run catches a simple linting error or a failing unit test. By then the agent has moved on. Getting back to a working state means rebuilding context from scratch and burning tokens just to fix something that should never have shipped in the first place.

Moving to a new platform shouldn't mean weeks of migration work before you see any value. Qovery now lets you connect your ArgoCD server and manage your existing applications directly alongside your Terraform modules, lifecycle jobs, and Qovery-native services, from a single control plane. Alessandro leads product at Qovery. He drives the changelog, roadmap, and product strategy - turning customer feedback into platform capabilities.

Modern data platforms are evolving rapidly, and Google Cloud BigQuery has become a core part of analytics, AI, and large-scale reporting architectures. Teams (including Harness) rely on BigQuery to process and analyze massive datasets, but managing schema changes in a secure, repeatable way can still be challenging.

Releasing new software used to be a big deal. You would set aside a Saturday night, wake up the on-call engineer, push the code, and hope that nothing broke before Monday morning. Then came feature flags, which changed everything without anyone noticing. Feature flags let you separate deployment from release, so you can send code to production in a dormant state and turn it on for users when you're ready. No more 1 a.m. maintenance windows.