# Infrastructure | Cycle.io

Canonical URL: https://cycle.io/platform/infrastructure

## A fully-managed platform on servers you own.

We built Cycle to be the platform we wanted: one that simplified deployments, networking, and monitoring, without giving up ownership or control.

-   [Connect a Server](https://signup.cycle.io/)

Control Plane

Peer Server

DOWNLOADING CYCLE OS...STARTING...DOWNLOADING CYCLE OS...BOOTING...CONNECTING...JOINED CLUSTER

### Connect any infrastructure

Bare metal, virtual machines, or a mix of both. Cycle abstracts the underlying hardware, giving you a single, unified control plane to manage hybrid infrastructure across any provider.

##### Bare Metal

Provision raw physical compute at one of our infrastructure partners, or connect a server you already own. Cycle was built to consume raw compute and deliver a cloud-like experience.

Supported Providers:

Vultr

Cherry Servers

& More

##### Virtual Machines

Bring your own VMs from any major public cloud or private hypervisor. Cycle standardizes the underlying instance and networks, stripping away provider quirks so your cluster behaves identically everywhere.

Supported Providers:

Vultr

Amazon Web Services

Google Cloud Platform

& More

### We simplify Day-Two operations.

Deploying a server, or a dozen servers, is easy. But ensuring they're always up to date with security patches, while also avoiding configuration drift between each other? That's less fun, and a distraction for builders.

##### Infrastructure Standardization

Cycle abstracts the underlying hardware and cloud APIs to give you a unified interface across any provider. By standardizing the OS, kernel, and network layer, we completely eliminate the need for provider-specific Terraform modules or Ansible playbooks.

Control Plane

Stack v0.0.0Stack v1.0.4Stack v1.1.0Stack v1.1.1Stack v1.2.0Stack v1.3.0Stack v2.0.0

Stack v0.0.0Stack v1.0.4Stack v1.1.0Stack v1.1.1Stack v1.2.0Stack v1.3.0Stack v2.0.0

##### Automatic Updates

Cycle handles platform upgrades through automatic rolling updates. New system services are pushed directly to your nodes and restarted in the background. Your underlying containers keep running without interruption, ensuring zero downtime for your applications.

Rolling Cluster Update

fpczkz-vultr-ord.s.8ac23ffc7a9...ffc7a9

Updated

qofhdp-gcp-us-east4.s.8ac23ffc7a9...ffc7a9

Upgrading...

gkzkts-homelab.s.8ac23ffc7a9...ffc7a9

Pending

##### Automatic Networking

Nodes automatically join a globally encrypted, and latency aware, IPv6 mesh network orchestrated by the Cycle control plane.

<https://cycle.io/platform/networking>

##### External Storage

Integrated support for iSCSI, Ceph, and more, without having to configure adapters and plugins. Mount as either raw block devices or file systems.

<https://cycle.io/platform/storage>

##### Built-In Orchestration

From load balancing, and auto-scaling, to integrated CI/CD pipelines, and more, servers are ready to accept deployments from boot time.

<https://cycle.io/platform/compute>

### Provision, monitor, and scale directly from Cycle's hosted MCP.

Work from whatever AI tool you already use. The MCP gives the model a way to interact directly with your infrastructure, so you can provision servers, deploy applications, or troubleshoot issues in minutes.

Server with CycleOS

Agent

OS Management &  
Node Telemetry

Compute Service

Frontend  
Container

API  
Container

Worker  
Container

Postgres  
VM

Windows  
VM

### A minimal OS built for modern infrastructure.

CycleOS is stripped of Linux bloatware, containing only exactly what is required to boot the server. Upon connecting to the control plane, the node downloads the remainder of the services and drivers it needs to run.

Minimum Server Specs

Architecture

x86\_64

Compute

2+ vCPUs

Memory

\> 4 GB RAM

Storage

\> 35 GB Disk

Network

100Mb/s+

### Designed for servers of almost all sizes.

From small VMs on the public cloud, to massive bare metal machines in your own data center, Cycle was built to run on a variety of infrastructure setups.

Our Control Planes

North America

Europe

### Geographically Distributed Control Planes.

To meet strict compliance and data residency requirements, teams can select which geographic control plane manages their infrastructure.

Both the North American and European control planes are fully distributed across multiple underlying infrastructure providers. Because of this, an region, or provider, outage won't lead to an outage of the Cycle control plane.

-   [Talk to an Engineer](https://cycle.io/contact)
-   [See a Demo](https://cycle.io/demo)
-   [Create an Account](https://signup.cycle.io/)

### Want to see what Cycle can do for you?

Experience the only control plane that natively orchestrates Containers, VMs, and Functions across any provider with a fully automated networking fabric.

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
