Keeping training data inside the EU

Plenty of teams start with one hard requirement: the data stays in the EU. Nexpod runs two live EU regions, EU-AMS-1 in Amsterdam and EU-FRA-1 in Frankfurt, and EU-HEL-1 in Helsinki is being built. This post covers what region pinning does and where its limits are.

What region pinning covers

• Servers, Serverless workers and cluster nodes run only in the region you pick.
• Volumes are stored in that region, and Nexpod never copies them out.
• Snapshots stay in the same region as the volume they belong to.
• Logs and metrics about your resources are kept in the EU.

Where it stops

Pinning controls where Nexpod stores and processes your data. It cannot control where you send it. When a job pulls a dataset from a bucket on another continent, or pushes checkpoints to an outside registry, that traffic goes wherever you point it.

Pin a project to a region

Give the project a default region and a list of allowed ones, so nobody starts a server elsewhere by accident. The API then rejects requests for any other region.

Invoiced in euros

Every invoice is issued in euros, with VAT handled under EU rules. There is no currency conversion on your side and no line for exchange-rate differences.

For your audit file

On request we share a data processing agreement, the list of sub-processors and the street address of each region. Ask through the contact page and mention the project name.