Operations | Monitoring | ITSM | DevOps | Cloud

You’ve almost certainly seen them… In the forest, rummaging through a dumpster, in poorly aging millennial memes. Raccoons are ubiquitous and endlessly entertaining creatures. YouTube and TikTok are full of videos documenting their clever antics and escapades. One such intrepid raccoon gained fame for making their way to the most unlikely places, from liquor stores to karate studios.

For a CTO, "four nines" represents a commitment to keeping production revenue live with less than 0.01% of total downtime per year. As AI workloads move from pilot projects into core production services, the reliability requirements for infrastructure have shifted. AI agents, RAG pipelines, and automated LLM workflows depend on a consistent platform state.

The “works on my machine” era is officially over. Nix is changing the way we think about software by treating packages as functional, immutable values, ensuring that a build works exactly the same way every time, on every machine. But while Nix excels on a local laptop, scaling that level of reproducibility across a global enterprise has historically been a challenge.

AI coding assistants are transforming how developers write software. Tools like Windsurf can generate entire modules, refactor complex code, and fix bugs in seconds. But speed comes with a tradeoff: AI-generated code can introduce subtle bugs, security vulnerabilities, or breaking changes that slip past even experienced developers. That’s where continuous integration comes in. CI acts as a safety net, automatically testing every change before it reaches production.

While Kubernetes enables teams to deliver more value faster, understanding and controlling Kubernetes costs remains challenging. You have disposable, replaceable compute resources constantly coming and going across a range of infrastructure types. Yet at the end of the month, you only get a billing line item for EKS costs and several EC2 instances.

The CertKit Agent 1.6 is out. Three things in this release, all of them coming from the same underlying problem: the shorter certificate lifespans get, the more certificate deployment has to behave like real software deployments.