OVHcloud is Europe’s largest cloud provider, operating its own data centres and
manufacturing its own servers. That vertical integration is the reason its pricing sits
where it does, and it is also why the company occupies a distinct position for
organisations with European data-residency requirements. If you need to buy OVHcloud account access, this page lists two configurations, at $30 and $250.
Overview: what makes OVHcloud different
Most cloud providers lease data centre space and buy servers. OVHcloud builds both.
It designs its own server hardware, operates its own facilities across Europe, North
America and Asia-Pacific, and runs its own network backbone. The practical consequences
are lower unit costs on raw compute, and a supply chain that sits entirely within the
company.
The second distinguishing factor is jurisdiction. OVHcloud is French, and for
organisations that need data processed under European jurisdiction — whether for
GDPR posture, public-sector procurement rules or internal policy — that matters in
a way no technical benchmark captures. The
OVHcloud documentation
covers the product range in detail.
Available OVHcloud account configurations
The table below is the complete list. Read it as the menu you choose from when you buy OVHcloud account configurations on this page — each row is priced and specified independently, so nothing is bundled or assumed.
| Configuration | Price |
|---|---|
| 34 vCPUs | $30 |
| Open 25 Port | $250 |
34 vCPUs — $30
A compute-denominated configuration. Thirty-four vCPUs is a substantial allocation at
this price point, and it reflects OVHcloud’s general position on raw compute economics.
The figure describes processing capacity available to the account; how it is distributed
across instances is a design decision.
A vCPU corresponds broadly to a thread on the underlying processor, so the number
governs how much work can proceed in parallel rather than how fast any single sequential
task completes. For parallel workloads — batch processing, concurrent request
handling, build farms — 34 vCPUs is meaningful headroom.
Open 25 Port — $250
References port 25 availability for outbound SMTP. As with other providers, OVHcloud
restricts outbound port 25 by default because it is the channel through which mail is
delivered directly to recipient servers, and unrestricted access is the primary vector
for outbound spam.
An account with it available can operate a mail transfer agent directly. This is a
legitimate architecture for self-hosted mail and for systems that must speak SMTP
outward, and it carries corresponding responsibility: OVHcloud’s acceptable use terms
apply, as does anti-spam law, and correct SPF, DKIM and DMARC configuration is
non-optional if mail is to be delivered at all. Where the requirement is application
notification email rather than operating a mail server, a managed service such as
Amazon SES is the more appropriate
choice.
Key features
The points below summarise what distinguishes these options for anyone about to buy OVHcloud account configurations for the first time.
- A 34 vCPU compute allocation at a $30 entry price.
- European infrastructure and jurisdiction for data-residency requirements.
- Owned data centres and hardware, which underpins the cost position.
- A port 25 configuration for accounts operating their own mail infrastructure.
- Anti-DDoS protection included across OVHcloud’s network as standard.
OVHcloud product families
Public Cloud instances
On-demand virtual machines billed hourly or monthly, spanning general purpose,
CPU-optimised, memory-optimised and GPU-attached flavours. This is the closest analogue
to what other providers call a VM or Droplet.
Bare metal servers
Dedicated physical machines with no hypervisor layer. For sustained heavy workloads,
databases with strict latency requirements, or licensing that is priced per physical
core, bare metal frequently works out both faster and cheaper than equivalent virtual
capacity. This is an area where OVHcloud is genuinely strong relative to the
hyperscalers.
VPS
A simpler, lower-cost virtual server line aimed at straightforward hosting rather than
elastic cloud workloads.
Object and block storage
S3-compatible object storage alongside block volumes that attach to instances. The S3
compatibility matters for the same reason it does elsewhere: existing tooling works
without modification.
Managed Kubernetes
A managed control plane with OVHcloud instances as nodes, for teams that have already
containerised.
Who should buy OVHcloud account configurations
- Teams needing substantial parallel compute economically — 34 vCPUs ($30).
- Organisations with European data-residency requirements — either configuration, with region selected accordingly.
- Operators of self-hosted mail infrastructure — Open 25 Port ($250).
Common use cases
Compute-intensive batch processing
Rendering, encoding, simulation, data transformation — work that divides into
independent units and scales close to linearly with available parallelism. A 34 vCPU
allocation addresses this directly, and it is the use case where the configuration’s
economics are most obvious.
European-hosted applications
Applications serving European users, or processing data that policy requires to remain
within European jurisdiction. Latency to European users is good and the jurisdictional
position is unambiguous.
Web and application hosting
Standard multi-tier hosting: application instances, a database, a load balancer.
Nothing exotic, and the cost position makes it attractive for workloads that are steady
rather than spiky.
Development and build infrastructure
Self-hosted CI runners and build farms benefit directly from parallel compute, and
build workloads are exactly the kind of embarrassingly parallel task that a large vCPU
count accelerates.
Mail infrastructure
Where operating a mail transfer agent is genuinely required, the port 25 configuration
enables it.
Choosing between the configurations
These two options are not points on a scale; they answer different questions.
The $30 configuration is about compute. If you need processing capacity and the
economics matter, that is the one. The $250 configuration is about a specific network
capability. It costs more than eight times as much, and the difference buys outbound SMTP
rather than additional compute.
Choose on requirement, not on price ordering. Most workloads want the first.
Technical considerations
Regions and data residency
OVHcloud operates across Europe, North America and Asia-Pacific. If data residency is
the reason you are choosing OVHcloud, confirm the specific region rather than assuming,
since the company operates outside Europe as well.
Network and DDoS protection
OVHcloud includes anti-DDoS mitigation across its network as standard rather than as a
paid add-on, a consequence of operating its own backbone. For publicly exposed services
this is a meaningful baseline.
Backups
Snapshots and backup options exist across the product lines but are not universally
enabled by default. Establish a backup position deliberately at the start rather than
assuming one exists.
Support model
Support tiers differ across product lines, and the bare metal and public cloud
offerings have different service expectations. Check the tier attached to the products
you actually intend to use.
Getting started
- Choose a region deliberately, particularly if data residency is the reason for the platform.
- Use SSH keys and disable password authentication immediately.
- Configure firewall rules permitting only the ports you serve.
- Establish a snapshot or backup routine before putting real data on the account.
- Set up monitoring, particularly disk utilisation alerts.
- If operating mail, configure SPF, DKIM and DMARC before sending anything.
Bare metal versus virtual instances on OVHcloud
OVHcloud is one of the few major providers where dedicated physical servers are a
first-class product rather than an afterthought, so the choice between bare metal and
virtual capacity is a real one here.
When bare metal wins
Sustained, predictable load is the clearest case. A machine running near capacity
around the clock costs less as dedicated hardware than as equivalent virtual capacity,
and it delivers consistent performance because there is no hypervisor and no noisy
neighbour. Licensing is the second case: software priced per physical core is frequently
cheaper on dedicated hardware than on virtualised equivalents. Latency-sensitive
databases are the third, since removing the virtualisation layer removes a source of
jitter.
When virtual instances win
Variable load, short-lived environments and anything that needs to be provisioned in
seconds. Bare metal takes longer to provision and is billed monthly rather than hourly,
so elastic workloads are a poor match. If you cannot predict demand, virtual capacity is
the correct default.
A practical middle path
Many estates end up mixed: dedicated hardware for the steady core — databases,
primary application servers — and virtual instances for variable capacity, staging
and batch work. This is usually cheaper than committing entirely to either model.
Data residency and European hosting in practice
Hosting jurisdiction is one of the main reasons organisations choose OVHcloud, and it
is worth being precise about what it does and does not settle.
Choosing a European region means the data is physically stored and processed in
Europe, which addresses a common procurement and policy requirement directly. What it
does not do by itself is make a system compliant with any particular regulation.
Compliance depends on what data you collect, the lawful basis for processing it, how long
it is retained, who can access it and what happens when someone asks for it to be
deleted. Hosting location is one input to that analysis rather than the conclusion.
Two practical points follow. First, confirm the specific region rather than assuming,
because OVHcloud operates outside Europe as well and an account is not inherently
European. Second, remember that backups, logs and any third-party services your
application calls also process data — residency applies to the whole system, not
only to the primary instance.
Operating an OVHcloud estate
Network baseline
Anti-DDoS mitigation is included across OVHcloud’s network rather than sold
separately, which is a direct consequence of the company operating its own backbone. For
anything publicly exposed this is a meaningful default that competitors frequently
charge for.
Private networking
vRack private networking connects servers across OVHcloud’s infrastructure without
traversing the public internet, including across data centres. Keeping database and
internal service traffic on private networking is both faster and materially safer than
exposing it publicly and relying on firewall rules alone.
Backups and recovery
Backup and snapshot options exist across the product lines but are not universally
enabled by default. Decide your backup position explicitly, and test a restore at least
once — an untested backup is an assumption rather than a recovery plan.
Automation
OVHcloud exposes a public API and maintains a Terraform provider. Beyond a handful of
servers, defining infrastructure declaratively is what prevents machines drifting into
subtly different states that nobody can reproduce.
Important considerations
The configurations state vCPU count and port 25 availability. They do
not state regions, instance shapes, storage allocations or quotas. Confirm anything your
design depends on in advance through the contact page.
vCPU count is not performance. Parallel capacity helps parallel work.
A sequential process does not run faster because more threads are available.
Provider terms apply. OVHcloud publishes its
terms and conditions,
which govern acceptable use including outbound mail.
Prices are per configuration, exactly as listed.
Understanding OVHcloud pricing
OVHcloud’s cost position is one of the main reasons to consider it, so it is worth
understanding where that position comes from and where it does not apply.
Why raw compute is inexpensive
The company designs its own servers, assembles them in its own facilities and runs
them in data centres it owns, using a water-cooling design it developed internally.
Removing the hardware vendor margin and the leased-facility cost from the stack is what
produces the pricing, and it is a structural advantage rather than a promotional one.
Where the economics change
The advantage is clearest on raw compute and dedicated hardware. It narrows on managed
services, where the hyperscalers have far broader catalogues and deeper automation. If
your architecture depends on a long list of managed services rather than on servers, the
comparison is no longer primarily about unit price — it is about whether the
services you need exist at all.
Traffic and bandwidth
OVHcloud has historically been generous on included bandwidth relative to the
hyperscalers, where egress charges frequently become a significant share of the bill.
For bandwidth-heavy workloads — media delivery, backups leaving the platform,
large downloads — this can matter more than the compute price itself.
Choosing a region and planning capacity
Two decisions shape everything that follows.
Region determines latency to your users, which jurisdiction governs
the data, and which products are actually available — not every product line
exists in every location. Because moving between regions means rebuilding rather than
migrating, this is worth an hour of thought at the start.
Capacity shape is the other. Thirty-four vCPUs can be one large
machine or several smaller ones, and the right answer depends on whether the workload is
one process that needs many cores or many processes that each need a few. Parallel batch
work generally prefers several machines, since a failure then costs one unit rather than
the whole job. A single database prefers one larger machine, because splitting it is not
an option.
Frequently asked questions
Which configuration should I choose?
Match the configuration to the workload rather than to the price. Most people who buy OVHcloud account configurations start from the smallest option that covers their current need and move up once real usage is measured, which avoids paying for headroom that never gets used. The comparison sections above set out the trade-offs; the FAQ page covers ordering questions.
Is it safe to buy OVHcloud account configurations listed here?
Every configuration on this page states its specification and price exactly as supplied, and nothing is implied beyond what is written. Anything your project depends on that is not named should be confirmed on the contact page before you buy OVHcloud account configurations.
What does 34 vCPUs actually give me?
Parallel processing capacity. It governs how much work can run simultaneously rather
than how quickly a single-threaded task finishes.
Is OVHcloud a good choice for GDPR compliance?
OVHcloud is a European provider operating European data centres, which is frequently
relevant to data-residency requirements. Compliance itself depends on how you process
data, not only on where it is hosted, so treat hosting jurisdiction as one input rather
than as an answer.
How does bare metal compare with virtual instances?
Bare metal removes the hypervisor layer, giving consistent performance and,
frequently, better economics for sustained heavy workloads. Virtual instances are more
flexible and faster to provision. Which is right depends on whether your load is steady
or variable.
Why is the port 25 configuration so much more expensive?
Outbound SMTP is restricted by default across the industry because of abuse potential.
Accounts where it is available are a different proposition, and the price reflects that.
Do I need port 25 for application emails?
Generally not. Applications typically send through a managed API or an authenticated
relay, neither of which needs outbound port 25.
How does OVHcloud compare with other providers here?
See Hetzner for the other major European
option, or DigitalOcean and
Linode for developer-focused alternatives. The
full range is in Cloud
Infrastructure.
How do I order?
Select the configuration above, add it to the cart and complete checkout through the
configured cryptocurrency gateway.
Where to buy OVHcloud account configurations
Everything needed to buy OVHcloud account configurations is on this page — the full list of 2 options, the price of each, and the specification each one carries.
Every configuration described above can be ordered directly from this page. Select the one you need in the selector at the top, add it to the cart and complete checkout — there are 2 configurations listed, $30.00 – $250.00. Checkout collects only a name and an email address, and payment runs through the cryptocurrency gateway configured on this site.
If you are unsure which option fits, describe the workload on the contact page before ordering rather than after — it is usually possible to narrow the list quickly. Common questions are collected on the FAQ page.
What you get when you buy OVHcloud account
Every listing on this page is a specific, named configuration rather than an open-ended arrangement. When you buy OVHcloud account here you are choosing one of the 2 configurations described above, at the stated price $30.00 – $250.00, with the specification exactly as written.
- The exact configuration named in the selector, with no substitutions.
- The price shown, with no added fees at checkout.
- A checkout that asks only for a name and an email address.
- Direct contact before ordering if you are unsure which option fits.
If you are comparing providers rather than configurations, the Cloud Accounts and Cloud Infrastructure categories list the alternatives side by side. If you already know what you need, you can buy OVHcloud account configurations directly from the selector at the top of this page.
Related products
Compare with Hetzner,
Linode,
DigitalOcean and
UpCloud. For hyperscaler platforms see
Cloud Accounts, or reach us via the
contact page.
Reviews
There are no reviews yet.