Buy OVHcloud Accounts
OVHcloud Developer Cloud & VPS
OVHcloud is the largest European-owned cloud provider, headquartered in France, with Public Cloud built on OpenStack, monthly VPS plans, Bare Metal dedicated servers and Hosted Private Cloud, all managed from one Control Panel. Data centres across Europe, North America and Asia Pacific, vRack private networking and included anti-DDoS protection make it a common choice for teams that want infrastructure under EU jurisdiction.
When you Buy OVHcloud Accounts on CloudAccountHub you choose between a listing labeled by Public Cloud vCPU quota level, 34 vCPUs, and a variant listed with outbound port 25 available for compliant transactional email. Each label describes exactly what the account is; usage inside it is billed by OVHcloud at its published rates. The guide below explains both variants and what to do after purchase.

What an OVHcloud account covers
OVHcloud is a European cloud provider headquartered in Roubaix, in the north of France. It designs and assembles its own servers, runs its own data centres and sells four infrastructure families under one customer login: Public Cloud, VPS, Bare Metal dedicated servers and Hosted Private Cloud. When you Buy OVHcloud Accounts on CloudAccountHub, the listing you receive is an OVHcloud customer account with access to the OVHcloud Control Panel, described exactly by the variant label you pick. This section walks through what sits behind that login so you know the vocabulary before you order your first resource.
The OVHcloud Control Panel and the customer account
Every OVHcloud customer has a customer account identified by a customer ID, historically called a NIC handle, which is a short string of letters and digits followed by the OVHcloud suffix. The Control Panel is the web interface for that account. It is organised into product universes: Bare Metal Cloud for dedicated servers and VPS, Hosted Private Cloud, Public Cloud, Web Cloud for domains, shared hosting and email, and Network for IP addresses, load balancers and vRack. Each service you order appears under its universe with its own billing line, its own contacts and its own renewal settings.
The account also has a billing area with invoices and payment methods, and a security area for two-factor authentication and login IP restrictions. The OVHcloud API exposes almost every Control Panel operation through application keys you generate per integration, and there is an official OVH Terraform provider for account-level resources.
Public Cloud projects built on OpenStack
Public Cloud is the on-demand infrastructure line, and it is built on OpenStack. Resources live inside projects. A project is a billing and quota boundary: it has its own monthly invoice, its own quotas per region, its own OpenStack users, its own SSH keys, its own private networks and its own API credentials. One customer account can hold several projects, so an agency can separate clients and an engineering team can separate production from staging with a hard line between them.
Because the platform is OpenStack, you get two management surfaces. The Control Panel offers a simplified view for creating instances, volumes and buckets. The Horizon dashboard and the OpenStack command line tools give you the full API: Nova for compute, Cinder for volumes, Neutron for networking and Glance for images. Anything that speaks OpenStack, including the Terraform OpenStack provider and Ansible modules, works against an OVHcloud project once you download the OpenRC file for a project user. The OVHcloud Public Cloud page lists the full catalogue of project-level services.
Public Cloud instances and per-project vCPU quotas
Instances are the virtual machines inside a project. OVHcloud groups them into ranges by workload: General Purpose, Compute Optimized, Memory Optimized, Discovery for low-cost sandboxes on shared vCPUs, IOPS for local NVMe throughput, GPU instances built around NVIDIA cards, and Metal instances that hand you a whole physical host through the OpenStack API. Each instance type has a fixed number of vCPUs and a fixed amount of RAM. A vCPU is a share of a physical core's time; our Cloud Library article What Is a vCPU? explains how to translate that into real capacity.
Every project carries quotas per region that cap how many instances, vCPUs, gigabytes of RAM, volumes and gigabytes of block storage the project can hold at the same time. New projects start with modest quotas. The Control Panel has a quota section where you can review current usage per region and request an increase, which OVHcloud evaluates on its own terms. The "34 vCPUs" label on this page refers to this concept: it describes the listed Public Cloud vCPU quota level of that account, and nothing beyond that. Quotas exist on every provider, and Cloud Service Quotas and Limits Explained covers the general pattern of starting limits and increase requests.
Object Storage and Block Storage
Public Cloud storage comes in two shapes. Object Storage is bucket storage behind an S3-compatible API, offered in a standard class for everyday access, a high performance class for hot data, and a Cold Archive class for long-term retention with a retrieval delay. Buckets are regional, can be made public for static asset hosting, and work with any S3 client or SDK. Block Storage provides volumes that attach to an instance in the same region and appear as raw disks, in classic and high-speed tiers with different IOPS characteristics. Volumes can be snapshotted, detached and reattached to another instance, and they survive the deletion of the instance they were attached to. Instance backups capture the boot disk as an image you can launch again later.
Managed Kubernetes and other managed services
OVHcloud Managed Kubernetes Service runs a certified Kubernetes control plane inside a Public Cloud project. OVHcloud operates and upgrades the control plane; you define worker node pools from the instance ranges and pay for those nodes as ordinary instances. The cluster integrates with Block Storage for persistent volumes, with the OVHcloud Load Balancer for services of type LoadBalancer, and with the project's private networks. Alongside Kubernetes, the Public Cloud universe includes a Managed Private Registry based on Harbor, managed databases for PostgreSQL, MySQL, MongoDB, Redis, Kafka and OpenSearch, and a Logs Data Platform, each billed as a project-level resource.
AI Endpoints, AI Notebooks and the rest of the AI range
The AI range inside Public Cloud follows the lifecycle of a model. AI Notebooks launches a Jupyter or VS Code environment on CPU or GPU resources with your datasets mounted from Object Storage. AI Training runs a containerised training job on GPUs and stops billing when the job finishes. AI Deploy serves a model or an API from a container with scaling rules. AI Endpoints is the managed inference service: OVHcloud hosts open-weight models, including large language models, embedding models and speech models, behind an API, and you pay per use without operating any GPU instance yourself. All of the AI products are billed inside a Public Cloud project like any other resource, and GPU instances count against the same per-region quotas.
VPS ranges
OVHcloud VPS is a separate product line from Public Cloud. A VPS is a KVM virtual server sold as a monthly plan with a fixed number of vCPUs, fixed RAM, NVMe storage and a bandwidth allowance, in ranges that step up in size. VPS plans are ordered from the Bare Metal Cloud universe, sit on their own billing line and renew monthly, and they are available in OVHcloud locations across Europe, North America and Asia Pacific. They suit workloads that want a predictable monthly price rather than hourly metering: a small business website, a game server, a self-hosted application or a monitoring node. An OVHcloud customer account can order from the OVHcloud VPS catalogue at any time; the listings on this page describe the account, not a VPS.
Bare Metal dedicated servers
Dedicated servers are the product OVHcloud began with. The catalogue runs from entry-level machines for developers and small businesses, through advanced servers for production databases and virtualisation, up to high-grade servers with large memory and storage configurations, plus GPU servers for AI work and storage servers for backup targets. Servers are ordered with a monthly commitment and, on some ranges, a setup fee, and OVHcloud offers hourly billing on part of the catalogue. Every server includes anti-DDoS protection, a public bandwidth allowance that varies by range, out-of-band console access, and operating system reinstallation from the Control Panel. As with VPS, the account can order from the Bare Metal server catalogue after purchase, subject to OVHcloud's own order review; no server is part of the variants listed here.
Hosted Private Cloud
Hosted Private Cloud is the managed virtualisation line, built on VMware vSphere and, more recently, on Nutanix. OVHcloud provides the hosts, storage and hypervisor licences and keeps them patched; you receive a dedicated vCenter or Prism environment. It is aimed at enterprises migrating an existing VMware estate and at regulated workloads that need physical isolation, and it appears here for completeness rather than as a typical follow-on order from a developer account.
vRack private networking
vRack is the private network that ties the product lines together. It is a layer 2 network you can extend to dedicated servers, Public Cloud projects, Hosted Private Cloud environments and Load Balancers, across data centres, so that a database on a dedicated server in Gravelines can talk to Public Cloud instances in Strasbourg over private addressing without crossing the public internet. Inside a Public Cloud project, private networks are created on top of vRack through Neutron, and a Gateway resource gives instances without a public address outbound access.
Data centres in Europe, North America and Asia Pacific
OVHcloud operates data centres it designs and runs itself, with in-house water cooling as a signature of its engineering. Its European footprint is the largest, with several sites in France, including Roubaix, Gravelines and Strasbourg, and further sites in Germany, Poland, the United Kingdom, Italy and Spain. In North America it operates in Canada near Montreal and at sites in the United States, and in Asia Pacific it has locations in Singapore, Sydney and Mumbai. Public Cloud regions are named after the site, with codes such as GRA, SBG, BHS, DE, WAW, UK, SGP and SYD, and OVHcloud has added a multi-availability-zone region in the Paris area for workloads that need zone-level redundancy. Not every instance type is offered in every location, and the region list changes, so treat the OVHcloud documentation as the authoritative source.
European data sovereignty positioning
OVHcloud presents itself as a European alternative to the American hyperscalers. It is European-owned and headquartered in France, which places the company and its European data centres under EU law and the GDPR with no foreign parent company in the chain. It publishes its certifications, including ISO 27001 and the French HDS health data qualification for relevant ranges, and it has pursued the SecNumCloud qualification from the French cybersecurity agency for specific offers aimed at public sector and regulated customers. For a European business whose regulators ask where data lives and who can compel access to it, this positioning is often the reason OVHcloud is on the shortlist. It does not make any individual account compliant on its own; the account holder still has to configure services and processes correctly.
Who these OVHcloud listings suit
People who search for an OVHcloud Account for Sale, or who type Buy OVHcloud Account Online into a search engine, usually belong to one of a handful of groups. The right variant depends on which group you are in, so place yourself here before you look at prices.
Developers who want OpenStack without running it. You would rather consume a project with an API than maintain a control plane. A Public Cloud project with a sensible vCPU quota gives you instances, volumes, networks and a Kubernetes cluster through the same credentials.
European businesses with residency requirements. Your contracts or your regulator want data in the European Union under a European provider. OVHcloud's French headquarters, its EU data centres and its published certifications answer that question in a way a US-headquartered provider's EU region does not.
Startups building on a budget. You need to run an API, a database, a queue and a couple of workers for a price that does not jump when traffic does. Hourly instances with monthly pricing options, included anti-DDoS protection and bandwidth allowances keep the bill legible while you find product-market fit.
Teams that send application email from their own infrastructure. Your application emits receipts, password resets and alerts directly from a mail agent rather than through a third-party API. Outbound SMTP on port 25 matters to you, and OVHcloud restricts that port on new Public Cloud instances by default, which is why the Open 25 Port variant exists as a separate listing.
Researchers, students and AI experimenters. You want a GPU for a few hours, a notebook that mounts a dataset from a bucket, or an inference API for a prototype, billed by the hour or by the token and shut down when the experiment ends.
If your reason is not on this list, the FAQ near the end of this page and the contact page are the fastest way to check whether a variant fits.
OVHcloud variant guide: both listings explained
Buyers who Buy OVHcloud Accounts here choose from two variants in a single Options group. The table shows the exact names and prices as they appear in the cart. Below the table, each variant is explained by restating what its label says and then describing the underlying OVHcloud concept in general terms. Neither variant includes anything beyond what its label states.
| Variant | Group | Price (USD) | What the label describes |
|---|---|---|---|
| 34 vCPUs | Options | $30 | An OVHcloud account listed at the 34 vCPU Public Cloud quota level |
| Open 25 Port | Options | $200 | An OVHcloud account listed with outbound port 25 available |
OVHcloud 34 vCPUs account, $30
The label "34 vCPUs" describes an OVHcloud account whose Public Cloud project is listed at a vCPU quota level of 34, exactly as the label states. A vCPU quota is the ceiling on the total number of virtual CPUs that instances in a region of the project can consume at the same time; it is not a single 34-core machine and it is not prepaid compute. With a 34 vCPU ceiling, you decide how to spend it. Eight General Purpose instances with four vCPUs each fit inside it with room for a two-vCPU bastion, and a Managed Kubernetes cluster with three eight-vCPU workers uses 24 and leaves ten for a database instance and a build runner.
Usage inside the quota is billed by OVHcloud at its published rates, hourly for Public Cloud resources, with monthly pricing available on instances you flag for it. The listing price of $30 is for the account as described; nothing in it is a credit balance. Any change to the quota after purchase is a request you make to OVHcloud through the Control Panel, which OVHcloud decides.
OVHcloud Open 25 Port account, $200
The label "Open 25 Port" describes an OVHcloud account listed with outbound TCP port 25 available, exactly as labeled. Port 25 is the port mail servers use to hand messages to each other. OVHcloud, like most cloud providers, restricts outbound port 25 on new Public Cloud instances by default because open SMTP from freshly created servers is a common spam vector; its documentation describes the default block and the request process for lifting it. The Open 25 Port variant is listed with that port available, which is a different account state from the vCPU quota variant, and the price reflects that difference.
This variant suits legitimate application notification and transactional email: order confirmations, password resets, monitoring alerts and messages a user has explicitly asked to receive. It is meant to be used within OVHcloud's terms of service and the anti-spam law that applies to you, which in practice means consent for every recipient, honest headers, a working unsubscribe path, and SPF, DKIM and DMARC records for the sending domain. Our article on port 25 and cloud email sending explains why providers restrict the port and what a compliant setup looks like. The listing says nothing about vCPU quota, sending volume or reputation; those are governed by OVHcloud and by the receiving mail providers.

Key OVHcloud services at a glance
These are the services a practitioner touches most often inside an OVHcloud account.
Public Cloud on OpenStack
Projects with per-region quotas, hourly instances across General Purpose, Compute, Memory, Discovery, IOPS, GPU and Metal ranges, managed through the Control Panel, Horizon or any OpenStack client.
Object Storage and Block Storage
S3-compatible buckets in standard, high performance and Cold Archive classes, plus attachable volumes in classic and high-speed tiers with snapshots and instance backups.
Managed Kubernetes Service
A certified control plane operated by OVHcloud, worker node pools drawn from the instance ranges, and integration with Block Storage, Load Balancer and project private networks.
AI Notebooks, Training, Deploy and Endpoints
Notebook environments on GPUs, containerised training jobs, model serving with scaling rules, and a managed inference API for open-weight models billed per use.
VPS and Bare Metal
Monthly KVM virtual servers in stepped ranges, and physical dedicated servers from entry level to high grade and GPU, all orderable from the same customer account.
vRack and anti-DDoS
A layer 2 private network spanning product lines and data centres, and DDoS mitigation included on every service without a separate subscription.
What people build on OVHcloud: use cases by audience
The audiences below match the search phrases people use when they arrive on this page, each with a concrete example of what the account is used for.
Developers
Engineers who Buy OVHcloud Account for Developers typically want an environment they can script end to end. A common setup is a Public Cloud project with a Terraform configuration that creates a private network, a Gateway, three General Purpose instances behind an OVHcloud Load Balancer, and a Block Storage volume for PostgreSQL, with cloud-init installing packages at first boot. Self-hosted CI runners are another frequent workload, because Discovery instances are cheap enough to keep a runner idle.
Business
A company that decides to Buy OVHcloud Account for Business is usually consolidating: an ERP or CRM that was on a shared host, a file server, an internal wiki and a customer portal move onto Public Cloud instances and, later, a dedicated server for the database. The sovereignty story matters here, because the business can answer a customer's data processing questionnaire with a single provider, a single jurisdiction and published certifications.
Startups
Founders who Buy OVHcloud Account for Startups are optimising for a bill that stays proportional to usage. A typical first architecture is a Managed Kubernetes cluster with a small node pool, a managed PostgreSQL database, Object Storage for uploads and a Load Balancer in front, all inside one project so the monthly invoice is a single document. As the product grows, node pools scale and a second project appears for staging.
Cloud computing
Teams that Buy OVHcloud Account for Cloud Computing in the general sense are usually replacing on-premises capacity or spreading risk across providers. Batch rendering, nightly data pipelines, report generation and log processing are the classic examples: a Compute Optimized or Memory Optimized instance is created on a schedule, runs for a few hours, writes results to Object Storage and is deleted. Hourly billing maps cost directly to runtime, and the project quota caps concurrency.
Development
People who Buy OVHcloud Account for Development want disposable environments that look like production. The pattern is one project per developer or per feature branch, created from the same Terraform module as production but with smaller instance types, and torn down when the branch merges. The Managed Private Registry stores the container images built for those branches so that every environment pulls from the same source.
Testing
When QA teams Buy OVHcloud Account for Testing, the goal is usually load and integration testing against a realistic topology. A private network isolates the system under test, a Load Balancer sits in front, and load generators run on separate instances in the same region so that network latency does not skew results. A 34 vCPU ceiling comfortably hosts a target system of three or four instances plus a pair of load generators for a single afternoon.
Research
Academics and lab groups who Buy OVHcloud Account for Research often need bursts of compute that a shared university cluster cannot schedule quickly. A simulation runs on a Compute Optimized instance for a weekend, a genomics pipeline reads inputs restored from Cold Archive the day before, or a survey platform runs on a small instance for the duration of a study. The project boundary also makes it simple to hand a project to a collaborator or archive it when a grant closes.
Projects
Freelancers and agencies who Buy OVHcloud Account for Projects use the project model literally: one Public Cloud project per client, with its own quota, its own OpenStack users and its own invoice. When an engagement ends, the project can be handed over or deleted without touching any other client. Agencies often add a VPS for lower-traffic client sites that suit a flat monthly plan.
AI development
Engineers who Buy OVHcloud Account for AI Development have a full pipeline inside Public Cloud. Data lands in Object Storage. AI Notebooks provides an interactive environment on a GPU with that bucket mounted. AI Training runs the containerised job and stops the meter when it finishes. AI Deploy or a GPU instance serves the resulting model, or, for teams that do not want to host weights at all, AI Endpoints provides open-weight models behind an API billed per use. GPU instances count against the project's per-region quotas, so plan the vCPU and GPU quota together.
Choosing the right variant
Two variants, two different reasons to buy. Choosing between them comes down to one question: does your workload need to send outbound email over port 25 from OVHcloud infrastructure, or does it need Public Cloud compute headroom?
- You want compute for apps, clusters, tests or AI
- Choose 34 vCPUs at $30. The listed quota level covers a small production stack, a Kubernetes cluster with a few nodes, or a batch environment.
- Your application sends transactional email itself
- Choose Open 25 Port at $200. It is listed with outbound port 25 available for compliant notification and transactional mail.
- You mainly want VPS or dedicated servers
- Either variant is an OVHcloud customer account from which those products can be ordered; the 34 vCPUs listing is the lower-cost entry point.
- You want both compute headroom and port 25
- The variants are listed separately. Ask through the contact page before ordering rather than assuming one label implies the other.
Buyers who Buy OVHcloud Accounts for a client project usually start with the vCPU quota variant because it is the general-purpose option. The Open 25 Port variant is a specialist purchase: if you cannot name the application that will send mail, you do not need it yet.
Practical considerations after purchase
An OVHcloud account is a working environment from the moment you log in, and the first hour sets the tone for how safe and predictable it will be. Work through these areas in order.
Billing and payment
Public Cloud resources are metered hourly and invoiced per project at the end of the billing period, with monthly pricing available on instances you choose to flag. VPS plans and dedicated servers are ordered for a term and renew on a schedule you control per service from the Control Panel. Register a payment method and set renewal preferences before ordering anything with a monthly commitment. OVHcloud publishes its prices per market and currency on its own website; nothing on this page is a statement of OVHcloud's rates.
Account contacts and two-factor authentication
Each OVHcloud service has three contact roles: administrative, technical and billing. The administrative contact controls the service, the technical contact receives maintenance and incident notices, and the billing contact receives invoices. Set these deliberately so the right people are notified. Then enable two-factor authentication on the customer account; OVHcloud supports authenticator apps, SMS codes and hardware security keys, and it lets you generate backup codes. Store the account password in a password manager rather than a shared document.
SSH keys and OpenStack users
Public Cloud instances are created with an SSH key registered in the project, per region. Generate a key pair with a modern algorithm, upload the public key, and create instances with it so that password login is never enabled. Create a separate OpenStack user for each automation tool or team member rather than sharing one, and remove users and rotate keys when people leave.
Security groups and private networks
OpenStack security groups are the stateful firewall in front of each instance. Review the default group in every region you use and replace any broad allow rules with explicit ones: SSH from your addresses only, HTTP and HTTPS from anywhere if the instance serves the public, and nothing else. Put databases and internal services on a private network with no public address and reach them through a bastion or a Gateway. On dedicated servers and VPS, which sit outside OpenStack, the operating system firewall does the same job, and OVHcloud's edge network firewall can filter traffic before it reaches the server.
Backups and snapshots
Take a volume snapshot before any risky change and an instance backup on a schedule for anything that holds state. Copy the data that matters to Object Storage in a different region, and consider Cold Archive for long retention. Test a restore once; a backup that has never been restored is a hope, not a plan.
Compliance with OVHcloud's terms
The account you receive is subject to OVHcloud's terms of service and acceptable use policy, and to the anti-spam and data protection law that applies to you. Read the terms once, keep accurate contact details on the account, respond to abuse notices promptly, and treat email sending, whether or not port 25 is open, as something that has to be consented, authenticated and rate-limited. Provider promotions and quotas are set by OVHcloud and change over time; nothing on this page overrides them.
Getting started checklist
Once your order is delivered, this sequence takes an OVHcloud account from a fresh login to a working project with the basics in place. Most of it happens in the Control Panel; the last steps use the OpenStack tooling.
- Log in to the OVHcloud Control Panel, change the account password, and enable two-factor authentication with backup codes stored offline.
- Review the account's contact details, register a payment method, and check renewal settings so nothing renews or lapses unexpectedly.
- Open the Public Cloud project and read the quota page per region. For the 34 vCPUs variant, this is where you confirm the listed level; note the instance, RAM and volume ceilings alongside it.
- Create an OpenStack user for yourself, download its OpenRC file, and install the openstack CLI to confirm you can list regions and images.
- Upload your SSH public key in each region you plan to use, then create a private network, a subnet and, if needed, a Gateway.
- Edit the default security group in the region: remove broad inbound rules, add SSH from your addresses, and add HTTP and HTTPS only where an instance will serve the public.
- Launch a small instance from a current Linux image with cloud-init user data that updates packages and creates your user, then confirm SSH access.
- If you chose the Open 25 Port variant, publish SPF, DKIM and DMARC records for the sending domain, set reverse DNS on the instance's public address to match the mail hostname, and send a test message to a mailbox you control.
- Enable instance backups or a snapshot schedule for anything with state.
- If you plan to order a VPS or a dedicated server, place the order from the Bare Metal Cloud universe knowing that OVHcloud reviews orders on its own timeline.
Common OVHcloud search terms and what they map to here
Search engines send people to this page with many phrasings, and not all of them match a listed variant. This section maps each phrase honestly to what is actually on the page.
Buy OVHcloud Cloud Account. The everyday phrase for a customer account with Public Cloud access. Both variants on this page are OVHcloud customer accounts; the 34 vCPUs listing is the natural match for someone who simply wants Public Cloud compute.
Buy OVHcloud VPS Account. Searchers using this phrase want an account from which OVHcloud VPS plans can be ordered. Any OVHcloud customer account can order VPS plans from the catalogue after purchase, subject to OVHcloud's own checks. Neither variant includes a VPS; the label describes the account.
Buy OVHcloud Dedicated Server Account. The same logic applies. An OVHcloud customer account can order Bare Metal dedicated servers, and OVHcloud reviews each server order itself. No dedicated server is part of either variant.
Buy Verified OVHcloud Account. If you are searching to buy verified OVHcloud account listings, understand that verification is something OVHcloud performs on its customers under its own rules, and it can ask for identity or payment checks at any point in an account's life. Nothing on this page is labeled verified. What you can check before ordering is the variant label and the price; what you should do after ordering is keep the account's contact details accurate so that any request from OVHcloud reaches you.
Buy Old OVHcloud Account. Buyers who want to buy old OVHcloud account listings generally mean an account with some history behind it. Neither variant on this page carries an age label, and we do not describe account age. Choose by quota level or port availability, which are the properties actually listed.
Buy OVHcloud Account with Credits. Searchers who want to buy OVHcloud account with credits usually mean a promotional balance for new customers. Neither variant here is listed with a credit balance, and any OVHcloud promotion, where one exists, is set by OVHcloud and subject to change. If a credit-based start is what you want, the UpCloud listings on this marketplace are labeled by credit amount.
Buy OVHcloud AI Account. There is no separate AI account type at OVHcloud; AI Notebooks, AI Training, AI Deploy, AI Endpoints and GPU instances are all ordinary Public Cloud resources inside a project. Someone searching to buy OVHcloud AI account listings is best served by the 34 vCPUs variant, since GPU and CPU quotas live in the same project, with GPU quota requested from OVHcloud as needed.
OVHcloud Cloud Account for Sale. A generic listing phrase. Both variants fit it, and the table in the variant guide is the authoritative statement of what each one is.
Frequently asked questions before you Buy OVHcloud Accounts
What exactly do I receive when I buy an OVHcloud account here?
You receive an OVHcloud customer account with access to the OVHcloud Control Panel, described by the variant label you chose: a Public Cloud project listed at the 34 vCPU quota level, or an account listed with outbound port 25 available. Instances, storage, VPS plans and servers are created or ordered by you inside the account and billed by OVHcloud at its published rates. The listing does not include prepaid usage, credits, a VPS or a dedicated server.
What does the 34 vCPU quota mean in practice?
It is the ceiling on the total virtual CPUs that instances in a region of the project can use at the same time. It does not restrict the size of any single instance below that ceiling, and it does not describe RAM, volume or instance-count quotas, which have their own limits. Deleting an instance frees its vCPUs. Any change to the quota after purchase is a request you make to OVHcloud through the Control Panel, and OVHcloud decides on it.
Why does the Open 25 Port variant cost more?
OVHcloud restricts outbound port 25 on new Public Cloud instances by default, as its documentation explains, because unrestricted SMTP from new servers is a common spam vector. The Open 25 Port variant is listed with that port available, which is a different account state from the quota variant, and the $200 price reflects that. It is intended for legitimate transactional and notification email that complies with OVHcloud's terms and anti-spam law.
Can I send marketing newsletters from the Open 25 Port account?
Only when every recipient has consented, your messages carry honest headers and a working unsubscribe mechanism, and your sending follows OVHcloud's acceptable use policy and the anti-spam law that applies to you. For genuine bulk marketing, a purpose-built email platform with reputation tooling is a better choice than a self-hosted mail server. This variant is designed for application email such as receipts, alerts and password resets.
Which OVHcloud regions can I use?
Region choice is yours after purchase; the account is not tied to one location. OVHcloud operates Public Cloud regions in France, Germany, Poland, the United Kingdom, Canada, the United States, Singapore, Australia and other locations, and its region list changes over time. The Control Panel shows which instance types are offered in each region when you create one.
Does the account include a VPS or a dedicated server?
No. Both variants describe the customer account and its Public Cloud state. VPS plans and Bare Metal dedicated servers are separate products that a customer can order from within the same account through the Bare Metal Cloud universe. OVHcloud reviews those orders itself, and availability, pricing and delivery times are set by OVHcloud.
Is there a free trial or credit variant?
No. Nothing on this page is listed with a trial or a credit balance, and we make no claim about OVHcloud promotions. Provider promotions, where they exist, are set by the provider and change over time. The lowest-cost entry point here is the 34 vCPUs account at $30, and because Public Cloud bills hourly, a small experiment inside it costs very little.
How do I automate OVHcloud from code?
For Public Cloud, create an OpenStack user in the project, download its OpenRC file, and use the openstack CLI, the Terraform OpenStack provider or Ansible. For account-level resources such as projects, vRack and dedicated server settings, generate application credentials for the OVHcloud API and use the official OVH Terraform provider. Cloud-init user data configures an instance at first boot.
Can I run Kubernetes on OVHcloud?
Yes. OVHcloud Managed Kubernetes Service runs a certified control plane inside a Public Cloud project, and you pay for the worker nodes as ordinary instances. A small cluster with three eight-vCPU workers uses 24 vCPUs, which fits inside the 34 vCPU quota level with room for a database instance.
What happens if I reach the listed vCPU quota?
The Control Panel and the OpenStack API will refuse to create another instance in that region until you delete one or OVHcloud raises the quota. OVHcloud's documentation describes the quota increase request in the Control Panel, and OVHcloud decides on that request. Plan instance sizes against the listed level, and use monthly instances only for workloads you have already sized.
Where can I get help after purchase?
For questions about the listing itself, use our contact page. For questions about OVHcloud services, quotas, regions and billing, OVHcloud's documentation and its own support are the authoritative sources. Our marketplace FAQ covers ordering, delivery and general questions that apply to every listing.