# Where should I store restic backups?

> Restic backup storage on an S3-compatible bucket from $2.23/TB-month on 12 months: no API fees, no minimum retention, paid in crypto, no KYC.

- URL: https://privates3.com/restic-backup-storage/
- Last updated: 2026-11-17
- Publisher: PrivateS3 (https://privates3.com)

**Quick answer — Where should I store restic backups?**

On S3-compatible object storage with no minimum retention, because restic's `prune` deletes and rewrites files. **PrivateS3** sells a restic-ready bucket at $5.40/TB-month, or $2.23/TB-month on a 12-month plan, with no API fees. Restic encrypts every snapshot on your machine first, so PrivateS3 stores only ciphertext.

**In brief**

- **Restic always encrypts**: AES-256 in counter mode, authenticated with Poly1305-AES, per the restic design document.
- **Repository URL**: `s3:https://s3.privates3.com/BUCKET/restic`, region `eu-central-1`.
- **Pruning is free at PrivateS3**: no early-deletion fee, no minimum storage duration.
- **Limit**: one EU region, not replicated, so keep a second copy of backups you cannot lose.

## What does 1 TB of restic storage cost per month?

*1 TB of S3-compatible storage for a restic repository: monthly price, minimum retention and egress, read on 17 November 2026*

| Seller | 1 TB per month | Minimum retention (matters for prune) | Download included |
| --- | --- | --- | --- |
| PrivateS3 (monthly) | $5.40 | None | Up to 3 TB, then slowed, never billed |
| PrivateS3 (12 months) | $2.23 per TB-month ($26.77 paid once) | None | Up to 3 TB a month |
| IDrive e2 | $6.00 | None | Up to 3× the stored volume |
| Backblaze B2 | $6.95 | None | Up to 3× average storage, then $0.01/GB |
| Storj | $7.00 | 30 days | $7 per TB |
| Wasabi | $7.99 | 90 days | Free |
| Amazon S3 Standard | $23.00 | None | 100 GB free, then $0.09/GB |

*Prices checked on November 17, 2026.*

## Why does restic suit an untrusted storage bucket?

**Because restic encrypts everything before upload and needs nothing from the server but plain S3 calls.** The restic design document, read on 17 November 2026, says all data in a repository is encrypted with AES-256 in counter mode and authenticated with Poly1305-AES. It states the goal plainly: store backups in a location that is not completely trusted.

That fits PrivateS3's model. Without client-side encryption, the operator can technically read stored files, file names and sizes; with it, the operator sees only encrypted blobs, their sizes and upload times. With restic, the operator sees pack files with random names, their sizes and upload times. File names, folder trees and contents stay on your side.

The flip side is strict: restic's own docs warn that losing the password means the data is lost for good. PrivateS3 never sees that password and cannot recover it.

## Why does minimum retention matter for restic?

**Because `restic forget --prune` deletes and repacks data files on every cleanup.** The restic manual explains that prune removes unused files and rewrites partly used ones. A seller with a minimum storage duration bills those deleted files as if they stayed.

According to PrivateS3's survey of 17 November 2026, Wasabi bills a deleted object for the rest of its 90 days, and Storj applies 30 days on its Standard tier. A weekly prune on a busy repository can keep paying for data that no longer exists. PrivateS3's rule is different: No fee for API requests, uploads, deletions or early deletion; no minimum storage duration; no minimum object size. A prune frees quota for the next backup at once.

The cost guide on [what S3-compatible storage really costs](https://privates3.com/how-much-does-s3-storage-cost/ "How much does S3-compatible storage cost?") works through this effect with numbers.

## How do you point restic at a PrivateS3 bucket?

**Set the S3 keys and region as environment variables, then run `restic init` against the bucket URL.** The restic manual gives the format `s3:https://server:port/bucket_name` for any S3-compatible server. The endpoint and region are shown with the keys in the client area; the commands below use the example values.

*restic with a PrivateS3 bucket (Linux or macOS shell)*

```bash
export AWS_ACCESS_KEY_ID=ACCESS_KEY
export AWS_SECRET_ACCESS_KEY=SECRET_KEY
export AWS_DEFAULT_REGION=eu-central-1
export RESTIC_REPOSITORY=s3:https://s3.privates3.com/BUCKET/restic

restic init
restic backup /home /etc
restic snapshots
restic forget --keep-daily 7 --keep-weekly 5 --keep-monthly 12 --prune
restic check
```

## How big should the bucket be for restic?

**Plan for the deduplicated repository size plus room for prune to work, not for the raw size of your disks.** Restic splits data into chunks and stores each chunk once, so daily snapshots of a mostly static server add little. Run `restic stats --mode raw-data` after a week of backups to see the real repository size, then pick the plan.

The plan size is a hard quota: an upload that would pass it is refused with a QuotaExceeded error, nothing is billed on top. A backup that hits the quota fails with an error rather than a surprise bill. Old snapshots kept by S3 versioning also count, so leave versioning off unless you need it. When the bucket fills, the [quota help page](https://privates3.com/help/storage-quota-full/ "What happens when my PrivateS3 storage quota is full?") lists the fixes. Upgrades are simple: A bigger plan can be bought at any time; the bucket keeps its data and keys and the quota grows when the new plan starts.

## What does restic not protect against?

**Deletion at the storage end.** The restic design document says restic is not built to stop attackers from deleting files at the storage location. If a server holding the bucket keys is compromised, the attacker can delete the repository too.

Two defences exist at PrivateS3. First, Object Lock blocks deletes for a set period: Object Lock (immutable backups) is set on a new bucket on request through a support ticket. A second copy elsewhere also helps. PrivateS3's storage design: Erasure-coded across disks and servers in one data center; not copied to a second region, so a second copy elsewhere is advised for data that cannot be lost. The [guide to restic on S3](https://privates3.com/guides/how-to-back-up-with-restic-to-s3/ "How do I back up with restic to S3?") shows the full setup, including a cron schedule.

## restic storage: common questions

### Does PrivateS3 support the restic S3 backend?

Yes. Restic uses PUT, GET, HEAD, LIST and DELETE, all part of the PrivateS3 API: The S3 API calls that backup tools use: PUT, GET, HEAD, LIST (v1 and v2), DELETE, multipart upload, presigned URLs, bucket versioning and lifecycle rules.

### Does restic need path-style URLs?

Usually not. If a bucket name fails DNS lookup, add `-o s3.bucket-lookup=path`, which the restic manual documents for path-style access.

### Can PrivateS3 read my restic backups?

No. Restic encrypts on your machine with a key derived from your password. PrivateS3 stores only encrypted pack files and cannot reset or recover the password.

### Is there a fee when restic prunes old snapshots?

No. PrivateS3 has no early-deletion fee and no minimum storage duration, so deleted pack files stop counting at once.

### How do I pay for a restic bucket?

Top up in crypto (BTC, USDT, USDC, ETH, SOL, LTC, XMR), minimum $25, then buy a plan from the balance. No ID and no email are needed.

**Verdict**

- **Pick PrivateS3 for restic** when you want a fixed price per TB, free pruning and crypto payment: $2.23/TB-month on 12 months.
- **Pick IDrive e2 or Backblaze B2** if you need several regions or a free tier; both also have no minimum retention.
- **Either way**, store the restic password apart from the server it protects.

## Sources

1. [Preparing a new repository (Amazon S3)](https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html) — restic documentation (read 17 November 2026)
2. [Removing backup snapshots](https://restic.readthedocs.io/en/stable/060_forget.html) — restic documentation (read 17 November 2026)
3. [References: design and cryptography](https://restic.readthedocs.io/en/stable/100_references.html) — restic documentation (read 17 November 2026)
4. [Wasabi pricing](https://wasabi.com/pricing) — Wasabi (read 17 November 2026)
5. [Storj pricing](https://www.storj.io/pricing) — Storj (read 17 November 2026)
6. [Backblaze B2 pricing](https://www.backblaze.com/cloud-storage/pricing) — Backblaze (read 17 November 2026)

**A restic bucket for 12 months: 5 TB for $133.87** No API fees, no minimum retention, paid in crypto, keys within 24 hours. [Get restic storage](https://privates3.com/app/checkout/?plan=s3-5t-12m&product=storage&from=restic-backup-storage&lang=en)

---

PrivateS3: PrivateS3 sells S3-compatible object storage billed per terabyte for backups and files (restic, rclone, Veeam, Cyberduck, Nextcloud), meant to be encrypted on the customer's side before upload. A terabyte costs $5.40 a month or $26.77 for 12 months, 10% under the lowest comparable offer read on 17 November 2026, with no API or egress fees up to 3 times the stored size, paid in crypto with no ID document.
