Managed Bare Metal with Cycle

Cycle is a provider-agnostic platform for simplifying container orchestration for DevOps teams. It acts as a unified control plane that allows teams to manage their infrastructure and deploy containers, functions, and virtual machines across multiple cloud providers, on-premises servers, or bare metal hardware, all without needing a dedicated operations team.

This includes deploying on Cherry Servers bare metal through a native integration, with Cycle acting as a managed Kubernetes alternative for teams needing greater infrastructure ownership and reduced operational complexity. You can find more information about the Cycle Platform on their website here.

Cycle's control plane is the software layer that sits on top of whatever infrastructure you give it (bare metal, cloud, on-prem, or a mix) and handles everything you'd otherwise need Kubernetes and other third-party tools for, including provisioning, container orchestration, networking, storage, load balancing, and observability, all built in natively rather than bolted on. You bring the hardware (e.g. Cherry Servers bare metal); Cycle's control plane runs and manages everything above it.

Cycle's EU control plane a fully separate, geographically isolated version of Cycle's control plane, built specifically for organizations with Europe data sovereignty requirements. Key points:

Fully segmented — it runs on a completely separate set of infrastructure providers from Cycle's US/North American control plane, with no shared servers, network, or data between the two.

Built only on European-owned hosting providers — this is what puts it outside the reach of the US Cloud Act, since the underlying infrastructure providers, such as Cherry Servers, themselves aren't US companies.

Lower latency for European teams — since workloads and orchestration both stay in-region, rather than routing through infrastructure elsewhere.

Timezone-aware updates — control plane maintenance/updates are scheduled with European timezones in mind, rather than defaulting to US hours.

In short: the standard control plane is Cycle's core product (the orchestration layer itself), while the EU control plane is isolated, built so European customers can keep both their workloads and their orchestration layer entirely within Europe.

The Cycle Platform is a provider-agnostic SaaS/PaaS solution providing the automation layer for application deployment, networking, storage, updates, and infrastructure operations, while Cherry Servers provides the underlying dedicated bare metal infrastructure, giving teams cloud-like simplicity with full infrastructure ownership and control.

Cycle manages everything above the hardware including provisioning, container orchestration, networking, and storage. Teams can deploy, orchestrate, and manage workloads across bare metal, public cloud, or a mix of both, with a managed platform without giving up control.

No — Cycle removes the need for Kubernetes altogether. Instead of managing a Kubernetes cluster, Cycle acts as a unified control plane that handles container orchestration, networking, storage, and scaling natively, so there's no cluster to maintain, no version upgrades, and no control plane overhead.

Cycle significantly reduces Kubernetes operational complexity while still providing the flexibility of Kubernetes.

We accept the following payment methods: credit/debit cards, PayPal, 12+ cryptocurrencies, bank transfers, Apple Pay, Alipay, Google Pay.

Deploy on Cherry Servers infrastructure across Europe, North America, and Asia-Pacific, provisioned through the Cherry Servers integration within Cycle's portal. Here you can find the full documentation on how to configure Cherry Servers bare metal through Cycle.