OVHcloud: European Infrastructure and vCPU Profiles

OVHcloud differs from most providers in a structural way: it builds and operates much of its own infrastructure, including data centres and a substantial amount of the hardware inside them. That vertical integration is visible in how it prices and positions its services.

Why owning the infrastructure matters

Providers that lease capacity pass those costs through. A provider that owns the building, the racks and the network has a different cost base, and tends to compete on price for straightforward compute rather than on the breadth of managed services.

The consequence for you is a provider that is strong on predictable compute and networking, and less focused on a wide catalogue of higher-level managed products.

European presence and data residency

OVHcloud’s European footprint is one of its most cited characteristics. For organisations with obligations about where data is stored or processed, being able to place workloads in a specific European jurisdiction is a requirement rather than a preference.

Data residency is decided by placement, not by configuration afterwards, so it belongs early in the decision. The general principle is covered in regions and availability zones.

Reading vCPU profiles

Catalogue configurations for OVHcloud are commonly expressed in vCPU terms. That figure describes compute headroom available to the account rather than a single fixed machine. It answers how much you can run, not what shape it comes in.

What a vCPU actually represents, and why the number alone is not a performance promise, is covered in what vCPU counts mean.

Outbound mail

As with other providers, outbound traffic on port 25 is restricted by default and lifting it is an account-level matter. A configuration that already carries the permission removes that step for mail-sending workloads.

Current catalogue options

Who it suits

OVHcloud fits teams that want European placement, predictable compute pricing and straightforward networking. Teams whose architecture depends on a deep managed-service catalogue will find the hyperscale providers a closer fit. A direct European comparison is drawn in Hetzner vs DigitalOcean.

After taking control

Change the account password, enable available second factors, rotate API credentials, review existing services and firewall rules, and confirm which data centre locations existing resources occupy before assuming they meet your residency requirements.