Operations | Monitoring | ITSM | DevOps | Cloud

Liftoff, a mobile advertising company, processes 1.5 trillion bid requests every month. Their platform touches 275 million unique devices daily across 150 geographies. At that scale, the proxy layer is a core part of the business. For years, Liftoff relied on a managed enterprise proxy vendor. It worked, until it didn’t.

Modern IT environments do not fail in neat, isolated ways. A network issue in one location can affect a business service somewhere else. A device alert may be the first sign of a larger dependency problem. And when teams are managing infrastructure across data centers, cloud, branches, campuses, and edge environments, the first challenge is often knowing where to look first. The issue is not alert volume alone. It is the missing context between telemetry, service impact, probable cause, and action.

For two years, the enterprise's question about AI was which model to buy. That question is already settling. Frontier capability is becoming abundant - rentable by anyone, swappable in an afternoon, and roughly identical in your hands and your competitor's. An advantage everyone can buy is not an advantage. What can't be bought is the thing underneath it: a system that has learned how your business actually works - the intelligence your enterprise accumulates and no competitor can replicate.

To meet community demand, we have restored the global workload overview in Rancher Manager. After previously removing the feature due to performance constraints, we prioritized user feedback and rebuilt it from the ground up. Powered by a new, optimized API, the updated UI is both highly scalable and resilient.

If you've shipped software in fintech, healthcare, or government, you probably know the specific dread of an upcoming compliance audit. Not because the software isn't secure, but because proving it is requires reconstructing a paper trail for decisions that were made in Jira tickets, Slack threads, and pull request comments over the last six months. The software is fine. The documentation of the software is the problem.

Every detection rule, every threat hunt, every AI agent you deploy rests on one silent assumption: that the data describing an attack actually reached your tools. When it doesn’t, nothing above it can save you, and no one gets an alert that the data was missing. Security teams invest heavily in the sharp end of the stack: detection content, threat intelligence, response playbooks, and increasingly, AI agents to triage and investigate at machine speed.

Harness AI Security provides a unified control plane for AI discovery, risk visibility, and runtime protection, helping organizations operationalize key requirements of the EU AI Act. Instead of relying on manual audits or fragmented tooling, teams get continuous insight into how AI systems are built, exposed, and used, along with the evidence needed to demonstrate compliance.

As of today, I’ve drafted this post upwards of 10 times – it’s old enough that the version I first started working on was called “Reflections on 1 Year of SRE Management” (I’m currently at 2.5 years). But everything I learned during that first year became critical for the next.

Good news for PHP developers: AppSignal monitoring is now available for PHP applications. Our new package brings traces, metrics, and logs from your PHP app into AppSignal, with auto-instrumentation for frameworks like Laravel and Symfony and a foundation built on OpenTelemetry. Already using AppSignal's PHP package and want the latest updates? Migrating is straightforward: remove your current OpenTelemetry setup and follow our new install guide.

CDN and edge spend is easy to lose track of. Fastly bills on its own, off to the side of your cloud invoice – real money, often significant, sitting where none of your cost tooling reaches. So it stays its own island: a lump sum with no easy way to tie it back to the teams, products, and customers driving the traffic.