# Persistent storage on Unbroker

Attach a service volume for application files. Configure its mount path and backups to an S3-compatible destination.

Canonical URL: https://unbroker.cloud/solutions/persistent-files
Updated: 2026-10-14
Author: Unbroker

[Deploy a stateful application](https://app.unbroker.cloud/login)

[Deployment tutorial](https://docs.unbroker.cloud/guides/app-with-persistent-files)

## Build with Unbroker

- **Keep data across deploys:** Mount a persistent directory while application containers remain replaceable.
- **Control the data path:** Point the application at an explicit directory instead of changing its storage model first.
- **Back up to your destination:** Configure scheduled volume backups to an S3-compatible destination you control.

## Bring a file-backed application to Unbroker

Some applications already expect a local data directory. Unbroker lets you attach a persistent volume to a service so you can keep that model while gaining a managed deployment workflow.

Keep code and dependencies in the image, then mount the application's durable data at a dedicated path. The service's deployment history and runtime logs remain in the same Cloud interface.

## Separate the application from its data

### Replace the running code

A new deployment can replace the container without treating the attached volume as disposable application output. Configure the application to write its durable files under the mounted directory.

### Keep storage operations visible

Use the service's Storage controls to inspect the volume and grow its capacity. Plan changes with the data lifecycle in mind: reset, detach and service deletion remove volume data.

## Build a recovery process around the volume

Persistence protects against routine container replacement; backups provide a separate recovery copy. Unbroker can schedule volume backups to your S3-compatible destination. Choose retention and test restoration for the application you actually run.

This model fits a single service with local durable state. For shared access across services or replicas, consider a database or external object store. Unbroker also provides database options when the product needs transactional records.

## Storage tutorial

The tutorial shows a configurable data path and a redeployment check that confirms a test record survives. It links to the operational storage guide for backup and volume management.

## Choose your plan

Persistent volumes require Pro and belong to one service. Volume-backed services run one replica; storage and your backup destination add to the cost.

[Current pricing](https://unbroker.cloud/pricing)

## Related solutions

- https://unbroker.cloud/deploy/docker.md
- https://unbroker.cloud/deploy/django.md
- https://unbroker.cloud/solutions/api-with-postgres.md