Operations | Monitoring | ITSM | DevOps | Cloud

In the last few months we've made some changes to VMs that finally allow installing and running Windows on them. MS Paint on Cycle is finally a reality. To make Windows VMs work, we had to add a few things to the platform to support it. As always with Windows, there are some quirks, gotchas, and pain points. But in the guide below, I'll show you how we solved these issues in our recent platform update, and how to install and run a Windows Server 2025 VM on Cycle with full network connectivity.

In the last few months we've made some changes to VMs that finally allow installing and running Windows on them. MS Paint on Cycle is finally a reality. To make Windows VMs work, we had to add a few things to the platform to support it. As always with Windows, there are some quirks, gotchas, and pain points. But in the guide below, I'll show you how we solved these issues in our recent platform update, and how to install and run a Windows Server 2025 VM on Cycle with full network connectivity.

Managing TLS certificates at scale is one of those operational tasks that starts simple and quickly grows into a sprawling problem. As organizations adopt microservices, multi-tenant architectures, and globally distributed load balancers, the number of domains and subdomains they support can expand dramatically. Each certificate then requires its own lifecycle management: Wildcard certificates offer a powerful solution to this growing complexity.

Managing TLS certificates at scale is one of those operational tasks that starts simple and quickly grows into a sprawling problem. As organizations adopt microservices, multi-tenant architectures, and globally distributed load balancers, the number of domains and subdomains they support can expand dramatically. Each certificate then requires its own lifecycle management: Wildcard certificates offer a powerful solution to this growing complexity.

One of the best parts of my job is helping Cycle users explore self-hosting options on the platform. This time, I had the pleasure of working with Dgraph (now a part of Hypermode). If you haven't heard of it, Dgraph is a distributed, horizontally scalable graph database that gives you a native graph storage/compute engine with distributed ACID transactions (via Raft and snapshot isolation) and first-class GraphQL.

One of the best parts of my job is helping Cycle users explore self-hosting options on the platform. This time, I had the pleasure of working with Dgraph (now a part of Hypermode). If you haven't heard of it, Dgraph is a distributed, horizontally scalable graph database that gives you a native graph storage/compute engine with distributed ACID transactions (via Raft and snapshot isolation) and first-class GraphQL.

With the tech world once again in the midst of a major shift, a new group of contenders has entered the market, offering capabilities the traditional hyperscalers can’t match. Often dubbed "neoclouds", these new providers range from developer-focused platforms to GPU-centric infrastructure clouds. Can these new clouds compete with 100 billion dollar incumbents in a space that's already changing at breakneck speed?

With the tech world once again in the midst of a major shift, a new group of contenders has entered the market, offering capabilities the traditional hyperscalers can’t match. Often dubbed "neoclouds", these new providers range from developer-focused platforms to GPU-centric infrastructure clouds. Can these new clouds compete with 100 billion dollar incumbents in a space that's already changing at breakneck speed?

Outages don't care how many zones you have. Power failures, software updates, and backbone disruptions all have one thing in common: they do not respect architecture diagrams. Redundancy only works if it is designed at the correct layer. Every team believes they are covered, and yet, when something breaks, the failure reveals that what looked like protection was only an illusion.

Outages don't care how many zones you have. Power failures, software updates, and backbone disruptions all have one thing in common: they do not respect architecture diagrams. Redundancy only works if it is designed at the correct layer. Every team believes they are covered, and yet, when something breaks, the failure reveals that what looked like protection was only an illusion.