# GPU cloud Spain Italy and Portugal: where to look for hosts

URL: https://cloudj.net/blog/gpu-cloud-southern-europe
Published: 2026-11-12 · Updated: 2026-11-12

> Where to look for GPU cloud Spain Italy and Portugal hosts: ES, IT and PT codes, FR and DE fallbacks, and Madrid or Milan VPS front ends for users.

Looking for GPU cloud Spain Italy or Portugal capacity usually starts with a simple goal: serve Mediterranean users from a machine that is not too far away. On Cloudj, the way to do that is the Country field on the GPU deploy page. Type `ES, IT, PT` and the console lists the independent host machines that report one of those countries, sorted by price. When that list is short, you fall back to France and Germany, and you keep the user-facing part of your app on a VPS in Madrid or Milan. This article explains when each step is worth it.

The [GPU cloud in Europe guide](https://cloudj.net/blog/gpu-cloud-europe-guide) covers all European codes. This one is for teams whose users live mostly in southern Europe.

## Who this is for

A few typical projects make southern Europe the right starting point:

- A Spanish or Italian language assistant for a local business, a newsroom or a public-facing service.
- A Portuguese language app whose European users are in Portugal and Spain.
- An e-commerce company in Spain or Italy adding product search, image generation or customer chat.
- A studio rendering or transcoding video for clients across the Mediterranean.

If your users are spread across the whole continent, a central location such as the Netherlands or Germany may serve them better. If they are mostly in Spain, Italy or Portugal, start here.

## The search ladder

Treat the Country field as a ladder. Climb only as far as you need.

1. **`ES, IT, PT`**. The direct answer. Each row reports its own country, so you can still prefer one of the three.
2. **`ES, IT, PT, FR`**. France borders Spain and Italy and often adds useful options. The [GPU cloud France guide](https://cloudj.net/blog/gpu-cloud-france) covers that code.
3. **`ES, IT, PT, FR, DE`**. Germany is farther from Lisbon or Palermo, but it is a major hub and widens the pool a lot.
4. **No country filter**. For training, batch embedding or rendering queues, sort by price and ignore distance.

Open the [GPU deploy page](https://app.cloudj.net/deploy/gpu) to try them. Stock changes during the day, so a model that is not listed at lunch may be listed in the evening, and the reverse. If you need help with the fields, the [country filter walkthrough](https://cloudj.net/blog/filter-gpu-by-country-console) explains them.

## Reading the results for a Mediterranean audience

When a row is listed, three columns deserve more attention than usual for a user-facing service in this region:

| Column | Why it matters here |
|---|---|
| Country | Spain and Italy are large; a host in the north of one country may still be closer to your users than one in the south of the other. Measure rather than assume. |
| Bandwidth price per TB | Media-heavy apps (images, voice, video) send a lot out. A cheaper GPU with expensive transfer can cost more overall. |
| Max duration | A service that should run for weeks needs a row whose "available until" date leaves a margin. |

Reliability, download speed and the Datacenter badge matter as always. Live "from" prices for every model are on [GPU cloud](https://cloudj.net/gpu-cloud).

## Measure from where your users are

A country label is a rough proxy for distance. Before you commit, deploy a short test on two candidates, for example one `ES` or `IT` host and one `FR` or `DE` host. Take the host and port from each instance's Connection tab and run from a machine near your users:

```bash
mtr -rwc 50 <host>
```

Compare at the busy evening hours. The [guide to measuring latency to a GPU host](https://cloudj.net/blog/measure-latency-to-gpu-host) explains how to read jitter and loss, not just averages. Per-minute billing keeps this test cheap, and a deployment that fails to start is not charged.

## Madrid or Milan VPS for the user-facing layer

GPU hosts are independent machines with an "available until" date. The instance and its disk are removed when that date comes, and there is no automatic move if a host goes offline. That is a reason to keep your public endpoint somewhere stable.

Cloudj runs a [VPS in Spain](https://cloudj.net/cloud-servers/spain) in Madrid and a [VPS in Italy](https://cloudj.net/cloud-servers/italy) in Milan. Pick the city closest to most of your users and let it hold the domain, TLS certificate, login, rate limits, product catalogue and request queue. Forward only the heavy GPU calls to the current GPU over an SSH tunnel. When you change GPU host, you change the tunnel, not DNS.

This split is common in e-commerce, where the shop must stay fast and online while AI features run in the background. The [e-commerce VPS guide for Spain and Italy](https://cloudj.net/blog/ecommerce-vps-spain-italy) covers the shop side.

## Choosing the card

Location does not change VRAM needs. For Spanish, Italian or Portuguese chat with a quantized mid-size open model, a 24 GB card such as the [RTX 4090](https://cloudj.net/gpu-cloud/rtx-4090) is a common starting point. For image generation, the same class works well. Larger models or longer contexts call for 48 GB cards, which need a higher account level than new accounts have; the console tells you when a choice is not available.

Respect the licence of any model you deploy, especially for commercial use.

## When southern Europe is not the right answer

If your contract requires a guaranteed machine in one specific country with a written SLA, a GPU from a live inventory is not the right tool, because each host is independent with no hardware SLA. If your users are in northern Europe too, a central location may be better. And if your job is pure batch work, the cheapest acceptable host anywhere will usually win.

## FAQ

### Can I get a GPU in a specific Spanish or Italian city?

No. GPU location is country level only. Use a Madrid or Milan VPS when the city matters.

### What if ES, IT and PT show nothing?

Add `FR`, then `DE`. For batch work, remove the country filter and sort by price.

### Can I keep work inside the EU?

You can restrict the Country field to EU codes. Check your own legal obligations; Cloudj does not make compliance claims.

### How do I pay?

From a prepaid account balance, billed per minute while the instance runs.

## Start searching

Open the [GPU deploy page](https://app.cloudj.net/deploy/gpu) and enter `ES, IT, PT`. If the list is short, add `FR` and `DE`, measure from your users, and keep your domain on a Madrid or Milan VPS so you can change GPU hosts without disruption.