# Storage | Cycle.io

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

## Data that moveswith your workloads.

Cycle abstracts the complexity of data management, ensuring your stateful workloads remain completely portable. Attach local NVMe disks, SANs, or shared mounts, and migrate them across providers without rewriting your stack.

-   [Deploy Your First Stack](https://signup.cycle.io/)

Node A

Node B

### Connect powerful storage options.

A workload shouldn't be limited to a single type of disk. Cycle lets you provision and attach multiple different storage backends simultaneously to the exact same container, VM, or function.

##### Local Volumes

Maximize IOPS by binding directly to the physical NVMe drives attached to your nodes for absolute peak database and cache performance.

##### Shared Mounts

Create shared directories at the host level, making it trivial to mount a shared filesystem across multiple containers on the same server.

##### External Volumes

Connect to high-availability network storage protocols like iSCSI and Ceph.

##### NFS Targets

Provide an IP and path, and Cycle will create a host mount accessible to your containers at startup.

Relative I/O Performance

Local / Shared MountsNative (100%)

External (iSCSI/Ceph)~70%

NFS Targets~45%

Baseline performance measured against direct NVMe physical attachments. Network overhead introduces standard latency to external and NFS protocols.

External Target Config

iSCSI PROTOCOL

TARGET\_IQN:

iqn.2001-04.com.example:storage.disk2.sys1.xyz

Portal IP

10.100.4.55

Port

3260

MOUNT\_MODE:

Raw Block Device (/dev/sdb)

### Attach SAN and Ceph seamlessly.

External Volumes are a native Cycle primitive designed to manage high-availability network storage protocols directly from the control plane.

##### Formatted File Systems

Let Cycle automatically format the external volume (ext4, xfs) and mount it as a standard directory inside your container or VM.

##### Raw Block Devices

For advanced database tuning or custom file systems, mount the target directly as a raw block device.

### Built for stateful data.

Take complete control over your data lifecycle with flexible, streaming-based backup commands and dynamic storage expansion.

##### Scheduled Backups

Cycle natively supports scheduled data backups executed entirely via streaming. You configure the exact command; Cycle streams the data from `stdout` for backups and pipes it back via `stdin` for restores.

Backup Stream Config

\# Example Backup Command (Postgres)

pg\_dump -U postgres -d production\_db

\# Example Restore Command

psql -U postgres -d production\_db < /dev/stdin

##### Thin Provisioning & Expansion

Cycle supports thin provisioning for local storage, ensuring you only consume the physical disk space you actually use. Need more headroom? Expand local volume limits dynamically via the API or portal without downtime.

20GB Allocated

500GB Expanded

-   [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
