Volumes the Fly.io Way
Fly Volumes are persistent local storage for your Fly Machines. Each one is:
- NVMe on the same physical server as its Machine
- Mounted like a regular directory
- Encrypted at rest by default
- Snapshotted automatically every day
- Extendable, by hand or automatically
- Billed on your regular Fly.io invoice
What You Get With Fly Volumes
fly volumes create
spread across separate hardware zones by default
Manage them with fly volumes, or declare them in the
[mounts]
section of your fly.toml.
How Do Volumes Work?
A single Machine with a volume goes down during host failures and every deploy. That's fine for development; for anything else, plan for two.
Snapshots and Forks
A daily snapshot may not have your latest writes, so keep your own backup plan for data you can't lose.
Simple Pricing
Volumes bill on the capacity you provision, not what you use. Snapshots bill on what they store, and the first 10 GB each month are free.
Volumes
Billed on provisioned size.
Snapshots
Billed on the total size stored.
Free snapshots
The first 10 GB of snapshots each month cost nothing.
Performance by Machine Size
A volume's speed limit comes from the Machine it's attached to.
| Machine size | Max IOPS | Max bandwidth |
|---|---|---|
| shared-cpu-1x, 2x | 4,000 | 16 MiB/s |
| shared-cpu-4x, 8x | 8,000 | 32 MiB/s |
| performance-1x | 12,000 | 48 MiB/s |
| performance-2x, 4x | 16,000 | 64 MiB/s |
| performance-8x, 16x | 32,000 | 128 MiB/s |
Getting Started
Tell your app where to mount the volume in fly.toml:
[mounts]
source = "myapp_data"
destination = "/data"
Then create one volume per Machine, with that name, in the region your Machines run in, and deploy:
fly volumes create myapp_data -r ord
fly deploy
Check on them any time with fly volumes list.