Define what “European” means for this workload
An application may need low latency to European compute, a specified storage location, a European invoice, or a contractual processing arrangement. Those are separate requirements. Write them down individually before selecting a provider. A region filter cannot establish that an entire application meets an organizational or legal requirement.
This guide is an infrastructure checklist. It makes no compliance determination. Include the people responsible for contracts and data governance when the choice depends on processing terms rather than only on a bucket location.
What the launch dataset establishes
The comparison contains a verified subset of locations. S3 includes Ireland as an availability example while its calculator row is priced in N. Virginia. B2 lists its EU Central region in Amsterdam. Wasabi documents an Amsterdam endpoint. Scaleway lists Paris, Amsterdam and Warsaw; its calculator uses Paris. Bunny lists European storage locations, while the model also assumes EU/NA CDN delivery. R2’s EU jurisdiction option is different from a best-effort location hint.
These statements describe provider documentation, not our observation of physical placement. Follow each profile’s source links before creating the production resource. “Available in Europe” does not mean every rate is the same across Europe or that a global delivery cache stays within a storage jurisdiction.
Follow every copy
Draw the path from the user to the application, storage and backups. Add logs, caches, replicas, monitoring exports and support workflows. A bucket can be in the intended region while a log of object names or a cached response exists elsewhere. Decide which data categories the requirement covers.
For a replicated design, distinguish multiple copies in a region from copies in multiple regions. A price for one storage region does not prove either failure model. Ask what happens if the selected location becomes unavailable, and document the restore path before relying on it.
Keep the budget in its real currency
Scaleway’s row remains in EUR; the other launch rows remain in USD. That avoids a hidden exchange-rate assumption. If your internal budget uses a single currency, record the rate and date you use, and keep room for exchange movement. Do not compare the digits of a euro total and a dollar total as if they were the same unit.
Also keep billing quantity separate from currency. The calculator takes decimal GB and converts to binary units for AWS and Wasabi. Bunny and Scaleway’s decimal treatment is a stated modeling assumption. Provider bills should be checked against actual metered units before forecasting from them.
Run a location-specific evaluation
Use a test bucket in the intended region and clients near the actual workload. Measure upload, retrieval, failure recovery and access control. A test from your laptop does not stand in for a distributed user population. Record your test conditions so a future team can understand the result.
Start with the comparison’s European filter, then inspect the selected profile and use the calculator with its displayed pricing region. For private repositories, continue with the backup guide and include recovery copies in the placement discussion.