> ## Documentation Index
> Fetch the complete documentation index at: https://docs.casebender.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Local Storage Limitations

> Default Docker-volume storage is single-host; object storage is optional

Local storage writes files to a named Docker volume at `/data`. New installs
use it by default. You can keep it after you apply an enterprise license.
Object storage (S3, GCS, Azure) is optional.

## Default local volume

`./casebender init` with no storage variables, and the Desktop Installer with
no storage fields filled, set `STORAGE_PROVIDER=local`. Files persist on a
named Docker volume mounted at `/data` for both web and worker. A bundled
ClamAV sidecar listens only on the internal Compose network.

The application shows a local-storage banner. To move to S3, GCS, Azure, or
certified S3-compatible storage, follow
[Storage Migration](/en/deployment/storage-migration-runbook).

## Limits

* One host holds both the application and the files. Keep replica count at
  one. Losing the volume loses attachments and evidence.
* There is no provider versioning, object lock, legal hold, or cloud audit
  control.
* Multiple replicas need an external shared filesystem with separately
  qualified consistency. Do not treat a host path as a hidden object store.
* Container-local and anonymous volumes can be lost when a container is
  replaced.
* Filesystem permissions and backup consistency are host-specific.

Do not enable MinIO.

## Operating a local volume

* Run web and worker on the same host and path.
* Encrypt the volume and back it up independently of the application.
* Monitor capacity, permissions, checksum failures, and backup restoration.
* Plan migration to S3, GCS, or Azure when you need more than one host or
  provider retention controls.

Follow [Storage Migration](/en/deployment/storage-migration-runbook) using
copy-first, non-destructive transfer and SHA-256 verification.