Operations | Monitoring | ITSM | DevOps | Cloud

OpenVPN got faster. OpenVPN with Data Channel Offload (DCO) now matches WireGuard’s throughput on the same hardware: up to 680 Mbps on both protocols on a GL.iNet Flint 3 router. Those figures come from OpenVPN’s own benchmarks, not independent tests, but they line up with what VyOS and IPFire have reported. For years the short answer to “why not OpenVPN?” was “it’s slow.” That answer no longer holds.

A good developer experience is about more than getting a container image running quickly. It's the peace of mind that comes from a platform that remains stable, behaves predictably and shows you what's happening when something goes wrong. That's the standard we hold Cycle to. We care about this because developer time is one of the most valuable things an engineering team has. Every hour spent wiring up networks or hand-rolling rollback scripts is an hour that didn't go into the product.

Let's Encrypt is cutting its certificate lifetimes in half, from 90 days down to 45 days by 2028. If your team still has a calendar reminder that says "renew the certs," this is the nudge to finally retire it. The change isn't purely a Let's Encrypt decision. It's part of an industry-wide shift driven by the CA/Browser Forum, and every publicly trusted certificate authority is heading the same direction.

When it comes to multi-tenancy isolation, most platforms only support one approach, and you have to make it work for every customer. Usually that means either all tenants share the same infrastructure and rely on the application to keep them apart, or every customer gets a separate stack that your ops team has to deploy, patch, and monitor on its own. Both approaches work. The trouble is that they're rigid.

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.