# Disks and persistent storage

Source: https://docs.quake.ai/docs/block/concepts/disks
Markdown: https://docs.quake.ai/docs/block/concepts/disks.md

---

# Disks and persistent storage

When guides say **disk**, **persistent disk**, or **block storage**, they usually mean a detachable volume that survives instance reboots. On Quake AI that object is a **[volume](/docs/block/concepts/volumes)** in the Block Storage service (OpenStack Cinder).

Ephemeral **root disk** space comes from the instance **flavor**. Durable application data typically lives on a separate volume you attach to the instance.

## Mapping provider terms

| Elsewhere | On Quake AI |
|---|---|
| AWS EBS volume | [Volume](/docs/block/concepts/volumes) |
| Azure managed disk | [Volume](/docs/block/concepts/volumes) |
| GCP persistent disk | [Volume](/docs/block/concepts/volumes) |
| DigitalOcean volume | [Volume](/docs/block/concepts/volumes) |
| Hetzner volume | [Volume](/docs/block/concepts/volumes) |
| Root disk only | Flavor-defined ephemeral disk on the [instance](/docs/compute/concepts/instances) |

Volume **snapshots** and **clones** are Cinder operations distinct from **instance snapshots** (Nova/Glance). See [Snapshots (instance vs volume)](/docs/compute/concepts/snapshot-types).

## What to read next

- [Volumes](/docs/block/concepts/volumes): attach, detach, extend, snapshot, and clone
- [Create a volume](/docs/block/how-to/create-volume): first block volume
- [Create block volume tutorial](/docs/quickstart/create-block-volume): end-to-end attach workflow