S3-compatible storage per TB · no API fees · encrypt before upload · pay in BTC, USDT, USDC, ETH, SOL, LTC, XMR
Get storage

How it works · checked 17 November 2026

How does PrivateS3 storage work?

Last updated: · 5 min read

Quick answer

How does PrivateS3 work?

PrivateS3 rents a bucket of a fixed size, from 1 to 100 TB, in one EU data center. Your backup tool encrypts files on your machine, then uploads them over the S3 API with your access keys. Disks are also encrypted at rest. A plan costs $5.40 per TB a month, with downloads up to 3 times its size.

In brief
  • What you rent: one bucket with a hard size limit, reached with any S3 client.
  • How a file travels: encrypted on your side, sent over HTTPS, stored on disks encrypted at rest.
  • What the operator sees without client-side encryption: names, sizes and contents. With it: encrypted blobs, sizes and times.
  • Limits: one region, not copied elsewhere; keys made by a person within 24 hours; some S3 features missing.

What does the operator see at each step?

What PrivateS3 can and cannot see at each step of a file's path, with and without client-side encryption
StepWithout client-side encryptionWith restic, Kopia, rclone crypt or Cryptomator
Upload over the S3 APIFile name, size, content type, time, source IPRandom-looking object names, sizes, time, source IP
Stored on diskReadable content, under disk encryption at restEncrypted blobs only
Request logs (14 days)IP, time, bucket, operation, bytesIP, time, bucket, operation, bytes
AccountAccount number, balance, orders; email if addedSame
PaymentCoin, amount, transaction on the blockchainSame

What exactly do you rent?

You rent one S3-compatible bucket with a fixed quota, for 30 days or 12 months. S3-compatible object storage: buckets reached with the Amazon S3 API (Signature Version 4, path-style and virtual-hosted URLs), sold as a fixed number of terabytes per month. Monthly Bay plans run from 1 to 100 TB; 12-month Silo plans cover 1, 5 and 10 TB. The full list is on the pricing page.

The bucket speaks the calls backup tools need. 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. It does not offer everything AWS does: No S3 Select, no bucket website hosting, no event notifications, no IAM policies beyond one key pair per bucket. If object storage itself is new to you, the object storage explainer starts from zero.

What happens to a file from your disk to the bucket?

It is encrypted by your tool, sent over HTTPS, and written to disks that are encrypted again at rest.

  1. On your machine. restic and Kopia always encrypt a repository with your password. rclone crypt and Cryptomator encrypt plain files and their names.
  2. On the wire. The S3 client signs each request with your keys and sends it over HTTPS to the endpoint.
  3. At PrivateS3. Disks encrypted at rest with AES-256 on the server; for privacy from the operator, files are meant to be encrypted on the customer's side (restic, rclone crypt, Kopia, Cryptomator) before upload.
  4. On restore. Your tool downloads the blobs and decrypts them locally.

The server-side layer protects against a stolen disk. It does not hide data from the operator. The encrypted storage page explains who holds which key.

What can PrivateS3 see and log?

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. That is why PrivateS3 asks you to encrypt before upload, and why it says so on every page.

Request logs (source IP, time, bucket, operation, bytes) are kept 14 days for abuse handling and quota accounting, then deleted. Account data is short: an account number, a balance, orders and tickets. An account number is the login; email is optional. Payments are on public blockchains, so a coin, an amount and a transaction exist outside PrivateS3 too.

Lose your encryption key and PrivateS3 cannot help: it never had it.

How do the quota and downloads work?

The plan size is a hard ceiling, and downloads are included up to 3 times that size each month. The plan size is a hard quota: an upload that would pass it is refused with a QuotaExceeded error, nothing is billed on top. Old versions count too: S3 versioning can be turned on per bucket from any S3 client; old versions count toward the quota.

Download traffic included up to 3 times the plan size each month; above that, download speed is limited to 100 Mbit/s until the next month, never billed. A 10 TB plan can download 30 TB at full speed in a month, enough for three full restores. According to PrivateS3's survey of 17 November 2026, Amazon S3 Standard bills $0.09 per GB for the same downloads after the first 100 GB. No fee for API requests, uploads, deletions or early deletion; no minimum storage duration; no minimum object size. The quota guide covers cleanup when the bucket fills.

What are the limits?

One region, a short wait for keys, and some self-serve features handled by a person.

  • One copy in one place. 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.
  • Keys by a person. One access key and secret key per bucket, created by a person within 24 hours of the order and shown in the client area.
  • Object Lock by ticket. Object Lock (immutable backups) is set on a new bucket on request through a support ticket.
  • Plans end. A plan ends at the end of its period unless renewed from the balance; the bucket then turns read-only for 14 days, then it and its contents are deleted.

These limits are why PrivateS3 fits a backup copy well and does not fit an app that needs IAM roles or a public website.

How PrivateS3 works: common questions

Do I need special software?

No. Any S3 client works: restic, rclone, Kopia, Duplicati, Veeam, Cyberduck, Nextcloud, MinIO Client (mc) and the AWS CLI.

Is server-side encryption enough?

It protects against a stolen disk, not against the operator. Encrypt on your side for that.

Presigned URLs work for a limited time. Public bucket websites are not offered.

What happens if the data center fails?

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. An outage over 24 hours gets the lost days credited back.

Can I create more keys myself?

Not yet. One key pair per bucket is created by a person. Ask support by ticket for changes.

Verdict
  • PrivateS3 works like any S3-compatible bucket: endpoint, region, bucket, two keys, and your tool does the rest.
  • Privacy is your encryption, not a promise: encrypt before upload and keep a second copy elsewhere.
Sources (2)
  1. restic: preparing a new repository (S3-compatible storage) — restic (read 2026-11-17)
  2. rclone S3 backend documentation — rclone (read 2026-11-17)

5 TB for 12 months: $133.87

One bucket, two keys, encrypted on your side. Pay in BTC, USDT, USDC, ETH, SOL, LTC, XMR.

$5.40/TB-month · no KYC

Get storage