AWS S3, Wasabi and Backblaze are US providers – their parent companies fall under the CLOUD Act regardless of the region your buckets physically sit in. On top of that come egress models that make your monthly bill unpredictable the moment you actually read data back. intercolo speaks the exact same S3 API with SigV4 signing, but stores your objects exclusively in our Frankfurt data center, provides a DPA under Art. 28 GDPR, and bills egress transparently: 1 TB included per stored TB. Your tooling stays put – Veeam, Restic, rclone, s3cmd, the AWS SDKs – you only swap the endpoint to https://de-fra.i3storage.com with region de-fra.
| AWS S3 | Wasabi | Backblaze B2 | intercolo | |
|---|---|---|---|---|
| Location / operator | USA / global | USA | USA | Frankfurt, DE |
| GDPR & DPA | CLOUD Act | CLOUD Act | CLOUD Act | DPA / Art. 28 |
| Egress model | per GB billed | ≤ storage, else throttled | 3× storage free, then per GB | 1 TB free/TB, +3.99€/TB |
| Minimum storage duration | none | 90 days | none | none |
| Durability | 99.999999999% | 99.999999999% | 99.999999999% | 99.999999% |
| Support | paid tiers | ticket (EN) | ticket (EN) | direct, DE/EN |
| Price / TB / month | ~21€/TB + egress | ~6€/TB | ~6€/TB | €2.49/TB |
We don't promise zero-egress – others do, then quietly throttle you at fair-use limits or bill every read-back GB individually. At intercolo you get 1 TB egress included per stored TB. Pull more than that and you pay a predictable 3.99 €/TB – transparent, no surprises on the invoice, no throttling. For backup and archive workloads that are rarely read back, the included allowance usually covers you comfortably, including regular restore tests. For delivery-heavy workloads you put our CDN (PoPs across the DACH region and Europe) in front and keep egress costs low.
After the CJEU's Schrems II ruling, transferring personal data to providers subject to US law is legally fraught – even when the data sits in an EU region. The CLOUD Act obliges US companies to hand over data regardless of where it is stored. A DPA and an EU region do not fully remove that residual risk. intercolo is a German operator with a German contracting party: your data processing happens exclusively in the Frankfurt data center, under German and European law, with no parent company in the US legal sphere. That removes the need for standard contractual clauses, transfer impact assessments and CLOUD Act analysis for this part of your infrastructure.
You don't rewrite a single application. Create a bucket and an API key pair with us, enter the endpoint https://de-fra.i3storage.com with region de-fra, and mirror your objects with rclone directly bucket-to-bucket. rclone verifies checksums, transfers only deltas, and runs parallelized across many streams. Your source stays in production throughout the migration – you only cut the endpoint over in your app once the sync has fully completed. Want client-side encryption? Put rclone crypt in front: your data is encrypted before it ever reaches our storage – the key never leaves your side.
Endpoint https://de-fra.i3storage.com, region de-fra. The crypt layer encrypts client-side before upload – the storage only ever sees ciphertext.
As an S3-compatible object storage repository (type "S3 Compatible", not "Amazon S3"). Service point https://de-fra.i3storage.com, region de-fra, set keys, pick a bucket – you cover immutability as the second copy in a 3-2-1 design, not on the storage side.
restic -r s3:https://de-fra.i3storage.com/my-bucket init – Restic encrypts client-side and deduplicates. Ideal for incremental, encrypted backups with no server-side dependencies.
Copy, sync, mount. Buckets can be mounted as a drive via rclone mount; rclone crypt gives transparent client-side encryption on top of TLS transfer.
aws s3 ls --endpoint-url https://de-fra.i3storage.com works unchanged. SigV4 is the default, and the AWS SDKs (boto3, aws-sdk-js …) talk to the endpoint directly – just set endpoint_url and region_name.
Nextcloud as primary object store, s3fs for POSIX mounts, Cyberduck or Mountain Duck for GUI access – over IPv4 and IPv6, with strong read-after-write built in.
Create a bucket and an API key pair (access key + secret). Access runs exclusively through these SigV4 keys and optional presigned URLs – no public buckets, no guesswork.
Enter https://de-fra.i3storage.com with region de-fra into your tool. One line in the config – the S3 API stays identical, SigV4 is the default.
Mirror your objects straight from the old provider with rclone sync. Checksum-based, parallelized, with no downtime for the running source.
Cut the endpoint over in your app once the sync completes. For delivery-heavy assets, put our CDN (DACH region and Europe) in front of the bucket to keep egress low.
Instead of bucket policies, ACLs or IP filters, intercolo uses a lean, controlled access model: every request is authenticated via API keys with SigV4 signing, and every transfer runs over TLS. For time-limited, shareable downloads you generate presigned URLs without handing out your keys – the URL expires automatically. Rotate keys deliberately by issuing a dedicated key pair per application or per project. And because encryption at rest is deliberately not done on the storage side, you encrypt client-side with rclone crypt, Restic or Cryptomator: the key stays with you, our storage only ever sees ciphertext. No object lock, no versioning, no audit logs – but a model you hold entirely in your own hands.
Durable storage for Veeam, Restic or Duplicati. Rarely read-back data sits here cheaply, and the included egress allowance of 1 TB per stored TB covers regular restore tests – you model immutability cleanly as the second copy in a 3-2-1 design.
Images, videos and downloads live straight in the bucket and are delivered through our CDN (PoPs across the DACH region and Europe). Reachable over IPv4 and IPv6, with strong read-after-write for freshly written objects.
As a primary object store for Nextcloud or as an s3fs mount for teams that share files GDPR-compliant from the Frankfurt data center – without the data ever leaving the German legal sphere.
S3-compatible storage for your own applications, ETL flows and analytics exports. After setting endpoint_url and region_name, the AWS SDKs (boto3, aws-sdk-js …) write straight against https://de-fra.i3storage.com.
Vår erfaring taler for seg selv: Vi har gjennomført vellykkede migreringer med flere petabyte data og over 500 millioner filer.