We have added a new European region to Mave. EU_4 runs in Scaleway’s Paris region and is now the default for new paid customers. We have also completed the migration of existing paid customer spaces from Amsterdam to Paris.
For customers, this change requires no action. Existing video URLs and embeds remain the same.
Earlier this year, we explained why Mave is moving to Scaleway. Scaleway is a French cloud provider and gives us a stronger European foundation for Mave’s infrastructure.
But choosing a European cloud provider does not mean every part of its physical infrastructure is necessarily owned and operated by a European company.
While reviewing the infrastructure chain behind our Amsterdam region, we learned that Scaleway uses third-party colocation providers there. Scaleway’s subprocessor list identifies Iron Mountain, Digital Realty, and Equinix EMEA as US-headquartered providers offering colocation services in the Netherlands.
The data was still stored and processed in the EU, and this did not make the Amsterdam region inherently insecure or non-compliant. But it introduced a dependency that did not fully match the direction we described in our post about why EU-hosted infrastructure does not automatically mean European control.
EU_4 uses Scaleway’s Paris region. Moving this workload to France removes the specific dependency on the US-headquartered colocation providers used for Scaleway’s Amsterdam region, while keeping Mave on Scaleway’s European cloud platform.
We migrated the video content of all existing paid customer spaces that were using our Amsterdam region. We then moved delivery of that content to the new Paris region, while keeping their existing Mave URLs unchanged.
That means:
EU_4 by default; andInfrastructure decisions are rarely final. Providers change, subprocessors change, and new information can change how we evaluate an existing setup.
For us, transparency means looking beyond the name and headquarters of our direct provider. It also means reviewing the physical infrastructure and subprocessors behind it, then making adjustments when a different setup better fits our goals.
The move to EU_4 is one of those adjustments. It keeps Mave’s paid video infrastructure in the EU while reducing a specific non-European dependency in the underlying data center chain.
We will keep reviewing these choices and documenting the providers involved on our subprocessors page.
1
2
3
4
5
<script type="module">
import { Player } from "https://cdn.video-dns.com/npm/@maveio/components/+esm";
</script>
<mave-player embed="ubg50Cq5Ilpnar1"></mave-player>
<script type="module">
import { Player } from "https://cdn.video-dns.com/npm/@maveio/components/dist/react.js";
</script>
<Player embed="ubg50Cq5Ilpnar1"></Player>
<script type="module">
import { Player } from "https://cdn.video-dns.com/npm/@maveio/components/+esm";
</script>
<mave-player embed="ubg50Cq5Ilpnar1"></mave-player>