# How Nevia Storage works

> Nevia offers two storage primitives: Block storage for data that needs speed and branching, together with S3-compatible object storage.

> Nevia is in early access for selected teams. The CLI installs with `curl -fsSL https://get.nevia.cloud | sh`, and the MCP server is at https://api.nevia.cloud/mcp. A person signs in once in the browser.
> Setup, sign-in and requesting access: [SKILL.md](https://nevia.cloud/SKILL.md). When Nevia fits and when it doesn't: [why.md](https://nevia.cloud/why.md).

> For the complete documentation index, see [llms.txt](https://nevia.cloud/llms.txt). This page's HTML version: https://nevia.cloud/docs/infrastructure/storage

# How Nevia Storage works

Nevia offers two storage primitives: Block storage for data that needs speed and branching, together with S3-compatible object storage.

| | Block storage | Object storage |
| :-- | :-- | :-- |
| What it is | A block volume from a pool of SSDs, mounted as a disk | S3-compatible object storage |
| Best for | Working directories, databases, anything latency-sensitive | Files, artifacts, backups, large blobs |

## Block storage

Every VM gets a data disk that behaves like a local NVMe drive. Underneath, it is a volume backed by a pool of SSDs with built-in replication, connected to the VM over a high-speed private network. Compute and storage always sit in the same region to keep read and write latency low.

::figure{id="storage-layers"}

Copy-on-write is built into every volume. Snapshots and clones are metadata operations and a clone shares every block with its parent until one side writes.

### Benefits

- **Sub-second branching:** Create a branch from a snapshot in under a second, whether it's a 1 GB workspace or a 1 TB database. No data is copied.
- **Pay only for the delta:** A branch shares its parent's data and only uses extra storage for new or changed blocks.

### Resilient out of the box

Data is replicated across independent drives and spread across many storage nodes by default, with nothing to configure. After a failure, the system automatically rebuilds the affected replicas. Storage is separate from compute, so your data survives if a compute host fails or is replaced.

## Object storage (roadmap)

Use object storage for files, build artifacts, exports and large blobs that you write once and read many times. It is S3-compatible, so existing tools and SDKs work out of the box.
