
5 S3 Providers With Versioning in 2026
Jonas ScholzS3 versioning is boring until it saves you.
It keeps multiple versions of an object, which can help recover from accidental overwrites, bad deployments, broken export jobs, or that classic "I thought this script only touched staging" moment.
Here are five S3 providers with versioning to compare in 2026.
What versioning is good for
Object versioning helps with:
- Accidental overwrite recovery
- Backup safety
- Auditability
- Rollback workflows
- Protection against destructive scripts
- Safer generated-file pipelines
The trade-off is cost. If you keep multiple versions, you store more data. That is the point, but it still counts on the bill.
Quick comparison
| Provider | Versioning angle | Best for | Watch out for |
|---|---|---|---|
| Sliplane | Versioning plus no per-bucket fees, egress fees, or request fees | App files and backups | Stored versions increase usage |
| Hetzner | Lists object versioning | Hetzner users | Infra-style setup |
| Scaleway | Versioning plus storage classes | EU lifecycle workflows | Pricing by class/egress |
| AWS S3 | Mature S3 versioning | AWS users | Complexity and billing |
| Cloudflare R2 | Bucket/versioning-related S3 workflows | Cloudflare users | Request fees after free tier |
1. Sliplane Object Storage
Sliplane Object Storage supports object versioning and object locking.
That combination is useful for app uploads, generated files, backups, and anything where accidental overwrite protection matters. Pricing is 5 EUR per 250 GB per month, excluding tax. First GB free. No request fees. No egress fees.
Versioning increases stored data, so the simple pricing helps: you only need to think about total stored GB, not requests and downloads on top.
Sliplane does not charge per bucket, so splitting uploads, backups, staging assets, and customer files into separate buckets does not change the bill.
Use Sliplane if:
- You want versioning in a German region.
- You want no request or egress fees.
- You store app uploads, backups, exports, or generated files.
- You want storage near your app platform.
Skip it if:
- You need advanced AWS lifecycle/versioning controls.
- You need many storage classes.
- You need many global regions.
2. Hetzner Object Storage
Hetzner Object Storage lists object versioning as a feature.
It is S3-compatible, available in Germany and Finland, and a natural choice if your infrastructure already lives on Hetzner.
As of July 2026, Hetzner pricing starts at 6.49 EUR/month, excluding VAT, including 1 TB of storage and 1 TB of egress. Extra storage is listed at 8.70 EUR/TB-month, extra egress at 1 EUR/TB, and Hetzner lists ingress, internal eu-central traffic, and S3 API calls as free.
The caveat in 2026 is availability under load. On July 2, 2026, Hetzner's status page showed degraded Object Storage in multiple locations and an ongoing note that high Object Storage traffic may lead to timeouts. The durability and feature set can still make sense for backups or Hetzner-local workflows, but I would not make it the first choice for availability-sensitive app paths right now.
Use Hetzner if:
- You already use Hetzner.
- You want German/Finnish storage.
- You need versioning near your Hetzner servers.
Skip it if:
- You want no per-bucket fees, egress fees, or request fees.
- You want app-platform integration.
- You do not use Hetzner.
3. Scaleway Object Storage
Scaleway Object Storage lists versioning and object lock among its S3-compatible features.
It is especially useful if you want versioning combined with lifecycle rules and multiple storage classes.
Use Scaleway if:
- You want European storage.
- You need storage classes.
- You want versioning plus lifecycle workflows.
Skip it if:
- You want the simplest possible bill.
- You want no egress fees.
- You need German storage specifically.
4. AWS S3
AWS S3 has the most mature versioning implementation and the deepest ecosystem around lifecycle rules, replication, object lock, logging, policies, and compliance features.
If your company is already on AWS, S3 versioning is often the default. The main downside is the same as always: AWS is powerful, but not lightweight.
Use AWS S3 if:
- You already use AWS.
- You need advanced lifecycle/versioning features.
- You have enterprise compliance needs.
Skip it if:
- You want a simple S3-compatible provider.
- You want predictable pricing.
- You want European/German provider positioning.
5. Cloudflare R2
Cloudflare R2 is a good option if your versioned objects are part of a Cloudflare-heavy app architecture.
R2 is S3-compatible and has free egress. It is especially interesting for public assets and edge workflows. The thing to watch is operation fees after the free tier.
Use R2 if:
- You already use Cloudflare.
- Egress is your main concern.
- Your file workflows benefit from Workers/CDN integration.
Skip it if:
- You want no request fees.
- You want German storage.
- You do not use Cloudflare.
Which S3 provider with versioning should you choose?
| If you care most about... | Pick |
|---|---|
| Simple German versioned storage | Sliplane |
| Existing Hetzner setup | Hetzner |
| EU versioning plus storage classes | Scaleway |
| Advanced AWS versioning workflows | AWS S3 |
| Cloudflare-native versioned storage | Cloudflare R2 |
Conclusion
Versioning is one of the most useful object storage features for real apps. It protects against the boring mistakes that happen to everyone eventually.
If you need the most advanced versioning and lifecycle controls, AWS S3 is still the reference. If you want European infrastructure, Hetzner and Scaleway are worth checking.
If you want S3-compatible versioning in Germany with no egress fees, no request fees, and simple pricing, Sliplane Object Storage is the straightforward option.
For immutable backup workflows, read 5 S3 Providers With Object Locking in 2026.