Operations | Monitoring | ITSM | DevOps | Cloud

If you've spent any time in an engineering Slack lately, you've probably noticed that AI comes up in just about every conversation. Someone's using an assistant to scaffold a new service. Someone else has an agent triaging alerts overnight. And at least one person is asking whether all of this means the team can finally skip the "platform stuff.".

CVE-2026-74580 is a high-severity Linux kernel bug in vhost, the subsystem that accelerates I/O for virtual machines. It gives a local user a reliable path to root on the host, and in some VM setups it lets a guest write into host memory. The CVE record has existed since August 21, 2026, but the full technical write-up, nicknamed "Vghost", only went public on October 12. It came with working exploit demos for both a local root escalation and a VM escape.

The first update to the MCP server since launch is out now, and the theme this time is servers. Your AI assistant can now change a server’s host-level settings, set up shared file systems for your containers, and show you what’s running on each machine and how much room is left.

Ask a developer who used Heroku what they remember about it and you'll usually get some version of the same answer: you pushed your code and it ran. That feeling is back in the conversation, mostly because AI tools have made building software faster than its ever been. But speed was only half of the Heroku story. The other half, the part teams ran into a year or two later, matters just as much today.

Building and managing hybrid cloud infrastructure is an increasingly common requirement for engineering teams. Some companies want to cut hyperscaler costs. Others have business continuity requirements that mean spreading infrastructure across several providers. Either way, more teams are taking hybrid cloud management into their own hands.

TL;DR - We made a way to use Cycle with AI models for doing things like deploying applications faster and diagnosing complex issues. If you'd like to get started right away with Cycle's Hosted MCP, check out our documentation. Today, we're launching a brand new way to interface with the Cycle Platform, that just a year or two ago would have felt entirely like science fiction. Our first ever AI-oriented tooling, Cycle's Hosted MCP, is live today.

Cycle recently went through a System and Organization Controls (SOC) 2 Type 1 audit and we've got the report. It’s an important step in our continuous commitment to data security and system availability. But are we just checking boxes for the sake of boxes or is there more behind it?

Function containers on Cycle have always been the efficient way to run batch jobs and workloads, with far more customization than traditional FaaS or serverless. What they couldn't do was run themselves. Over the past year, team after team told us the same thing: they wanted these functions on a schedule without standing up and babysitting a cron service. As of this release, Cycle fully supports CRON scheduled function containers.

We're thrilled to announce that we've added Cherry Servers, a European infrastructure provider, as another native integration to the Cycle platform. With this integration, Cycle clients have more choice in where, and how, they deploy their applications as Cherry offers a variety of bare metal server configurations across 7 data centers located around the globe. For a more formal announcement, please see our joint press release with Cherry Servers.

Key Takeaways In modern software delivery the pressure to iterate quickly is real. Kubernetes sparked a revolution in container orchestration, and it remains a huge forward step for many teams. But the truth is, adopting Kubernetes is not a guarantee that you'll suddenly move faster or reduce pain. Managing a Kubernetes cluster at scale requires deep expertise, dedicated operations, and often more overhead than many organizations anticipate. This has led many companies to explore Kubernetes alternatives.