Storage Overview
FileNest supports two storage modes: Managed (FileNest owns the bucket) and BYOB (you supply the credentials).
Storage modes
| Mode | Who manages the bucket | When to use |
|---|---|---|
managed | FileNest | Getting started, no storage preferences |
byob | You | Compliance requirements, existing bucket, cost control |
Supported providers
| Provider | Mode | SSE default |
|---|---|---|
| AWS S3 | managed + byob | Always on (AES-256) |
| Azure Blob Storage | byob | Always on (Azure-managed) |
| Google Cloud Storage | byob | Always on (Google-managed) |
| Cloudflare R2 | byob | Always on (AES-256) |
| MinIO | managed + byob | Off by default (togglable) |
| RustFS | managed + byob | Off by default (togglable) |
Choosing a provider
- Start with Managed S3 — zero configuration, SSE always on, scales automatically.
- Switch to BYOB when you need to store data in your own AWS account, use an existing bucket, or comply with data residency requirements.
- MinIO or RustFS — for on-premises or air-gapped deployments where data cannot leave your infrastructure.
Server-side encryption
All cloud providers (S3, R2, Azure, GCS) have encryption enforced at all times and cannot be disabled.
MinIO and RustFS support optional SSE-S3 encryption. When enabled, FileNest sends ServerSideEncryption: AES256 on every upload. The MinIO/RustFS server must have a KMS key configured.
See Encryption (SSE) for full details.
Next steps
- Managed Storage — what's included with managed mode
- Bring Your Own Bucket — how BYOB credentials work
- Provider-specific guides: S3 · Azure · GCS · MinIO · R2 · RustFS