Any S3-compatible service

Nyx Backup works with any S3-compatible storage - Cloudflare R2, MinIO, DigitalOcean Spaces, and more. You need an endpoint URL, a bucket, and an access key / secret.

Which services work

What Nyx Backup needs from a provider is multipart upload, ranged downloads, and an existence check on an object. Anything implementing the S3 API provides those.

Recognised by name. These are detected automatically, so the region is worked out for you and the app labels the backup set with the provider:

• Amazon S3 - the original, and what everything else is measured against.
• Cloudflare R2 - no egress fees. Also uploaded and restored in smaller pieces, which makes large restores over home internet far more reliable.
• Backblaze B2 - low cost per gigabyte, usable through either its own API or its S3 interface.
• Wasabi - no egress fees. Note its minimum storage period: deleted data is still billed until that period is up, which matters for a backup that expires old versions continuously.

Everything else that speaks S3. Not individually tested here, but nothing about them is unusual:

• Self-hosted and NAS: MinIO, Ceph (RADOS Gateway), Garage, SeaweedFS, and the S3 services built into TrueNAS, Synology and QNAP - the option if you want backups to stay on hardware you own.
• Hosting providers: DigitalOcean Spaces, Linode / Akamai Object Storage, Vultr, Hetzner, OVHcloud, Scaleway, Exoscale SOS, UpCloud, Contabo.
• Larger clouds: IBM Cloud Object Storage, Oracle Cloud Infrastructure Object Storage, Alibaba Cloud OSS (S3-compatible mode), Tencent Cloud COS.
• Other: iDrive e2, Storj and Filebase - the last two reached through an S3 gateway rather than their own native protocol.

If yours is not listed, try it. A service either speaks the S3 API or it does not, and Test connection tells you before you save the backup set.

Two exceptions. Google Cloud Storage and Azure Blob Storage each have their own connector in Nyx Backup - use those instead of routing them through S3. Google offers an S3 interoperability mode, but the direct connector is better; Azure has no S3 interface of its own at all, and putting a third-party translation layer in front of your backups is not something we would suggest.

1. Set up the storage

Cloudflare R2:

1. In the Cloudflare dashboard open R2 and Create bucket.
2. Open R2 > API Tokens > Create API token with Object Read & Write for the bucket, and copy the Access Key ID and Secret Access Key.
3. Note the S3 endpoint shown for your account: https://<accountid>.r2.cloudflarestorage.com.

MinIO / other:

1. Create a bucket on your server.
2. Create a user/access key with read-write on that bucket.
3. Your endpoint is the server’s S3 URL (for example https://minio.example.com).

2. Connect it in Nyx Backup

New backup set > destination S3-Compatible, then enter:

• Endpoint URL - from step 3.
• Bucket - the bucket name.
• Region - use auto for R2, or your provider’s region.
• Access key and Secret key.

Once Test connection succeeds, set a schedule and retention, save the set, and choose Run now. Nyx Backup encrypts everything on your machine before upload, so this destination only ever holds encrypted blobs. Give each machine its own bucket or folder - see Connecting storage.

Tip: Nyx Backup detects Cloudflare R2 automatically and tunes upload and download for it, which keeps large transfers reliable on residential connections.