OVHcloud VPS, Public Cloud or Dedicated Server: Which Fits Your Workload
A practical comparison of OVHcloud VPS plans, OpenStack-based Public Cloud and bare metal dedicated servers, with a checklist for matching each to your workload.
OVHcloud sells three quite different kinds of server: VPS plans, Public Cloud instances and dedicated (bare metal) servers. An OVHcloud VPS is often the cheapest way in, but it is not always the right fit, and choosing the wrong product can mean a migration later. This guide compares the three so you can match the product to the workload.
The short answer #
- Choose a VPS for a single website, a small application, a VPN or a personal project where a fixed monthly price and simple management matter most.
- Choose Public Cloud when you need to create and destroy servers on demand, automate through APIs or Terraform, scale horizontally, or combine compute with managed Kubernetes, databases and object storage.
- Choose a dedicated server when you need the full resources of a physical machine: consistent CPU, large amounts of RAM or local disk, or hardware-level isolation.
The rest of this guide explains the reasoning, so you can test it against your own requirements. For background on the company, its datacenter footprint and wider product range, see our OVHcloud provider overview.
Side-by-side comparison #
| Factor | VPS | Public Cloud | Dedicated server |
|---|---|---|---|
| What it is | Virtual machine with a fixed plan | OpenStack-based instances and services | Physical machine reserved for you |
| Billing model | Monthly, with discounts for longer commitments | Hourly, or monthly per instance for savings | Monthly or longer commitment, sometimes with setup fees |
| Provisioning speed | Minutes | Minutes, fully API-driven | Minutes to days depending on stock and configuration |
| Scaling | Upgrade to a larger plan | Add or remove instances freely, resize flavors | Order another server or a bigger model |
| Private networking | Limited | Private networks and vRack | vRack on most ranges |
| Best for | Simple, steady workloads | Elastic, automated infrastructure | Heavy, sustained workloads |
Product names, plan sizes and the features included in each range change from time to time, so treat this table as a model of how the products differ and confirm details on the official product pages before you order.
OVHcloud VPS in detail #
An OVHcloud VPS is a virtual server with a set allocation of vCores, RAM and storage, sold at a fixed monthly price. You pick an operating system or a preinstalled application, choose a datacenter location, and manage the server as root over SSH.
Where a VPS works well
- WordPress or other CMS sites with steady traffic
- Small APIs, bots, cron workers and monitoring tools
- Personal VPNs, Git servers and development sandboxes
- Teams that want predictable monthly spend with no metered surprises
Where a VPS starts to strain
Because VPS plans are fixed bundles, scaling means upgrading to the next plan rather than adding capacity in small steps. There is less emphasis on API-driven lifecycle management, so building and tearing down servers automatically for CI or autoscaling is awkward. If you find yourself running several VPS instances and wiring them together by hand, that is usually the signal to look at Public Cloud.
OVHcloud Public Cloud in detail #
Public Cloud is OVHcloud’s elastic cloud platform, built on OpenStack. It is closer in spirit to the hyperscalers: you create instances from flavors, attach block storage volumes, put files in S3-compatible Object Storage, and connect everything through private networks.
What you get beyond compute
- Instances in general-purpose, CPU-optimized, RAM-optimized, GPU and other families
- Block Storage volumes that can be detached and moved between instances
- Object Storage with an S3-compatible API
- Managed Kubernetes Service, with Public Cloud instances as worker nodes
- Managed databases, load balancers and other platform services
- OpenStack APIs, the OVHcloud API and a Terraform provider for automation
Why the billing model matters
Public Cloud instances can be billed hourly, which suits test environments, batch jobs and anything short-lived. For instances you will run all month, the monthly billing option is usually cheaper. A common pattern is to run the steady baseline on monthly instances and burst with hourly ones. Our guide to cloud cost management covers how to tag and review resources so hourly instances do not linger unnoticed.
The trade-off
Public Cloud asks more of you. You design networks, security groups and storage yourself, and the OpenStack concepts (projects, flavors, images, security groups) have a learning curve if you have only used a control panel before. For a single website, that is overhead you do not need.
Dedicated servers in detail #
OVHcloud is known for its bare metal range, which runs from budget lines aimed at individuals up to high-end servers for large databases and storage clusters. You get the whole physical machine, with no hypervisor overhead and no neighbors competing for CPU.
When bare metal makes sense
- Databases with large working sets that need lots of RAM and fast local NVMe
- Game servers, streaming and other latency-sensitive workloads
- Virtualization hosts where you run your own hypervisor (Proxmox, VMware and similar)
- Workloads with sustained, predictable load where the per-resource cost of bare metal beats virtual servers
- Compliance or licensing requirements that call for single-tenant hardware
What you take on
You are responsible for the operating system, RAID configuration, monitoring and hardware-level concerns such as reacting to disk failure alerts. Scaling is coarse: you add another server rather than a few more vCPUs. Minimum commitment terms and possible setup fees also make dedicated servers a poor choice for experiments.
Features that apply across the range #
A few OVHcloud characteristics are relevant whichever product you choose:
- Anti-DDoS protection is included on OVHcloud infrastructure, which is useful for game servers and public-facing services.
- vRack is OVHcloud’s private network that can connect dedicated servers and Public Cloud projects, letting you build hybrid designs such as a bare metal database with Public Cloud application servers.
- Datacenter choice includes several locations in Europe as well as North America and Asia-Pacific. Not every product is sold in every location.
- Account verification: new customers may be asked to verify identity or payment details before certain orders are delivered. This is a standard anti-fraud measure; complete it through the official control panel.
A decision checklist #
- How variable is your load? Flat and predictable points to VPS or dedicated. Spiky or short-lived points to Public Cloud.
- How many servers will you run? One or two suits a VPS. Fleets managed with code suit Public Cloud.
- Do you need managed services? Kubernetes, managed databases and object storage live in Public Cloud.
- Is raw performance per dollar the priority? Sustained heavy workloads often favor dedicated servers.
- Can you commit? If not, avoid long terms and pick hourly Public Cloud until usage settles.
If you are comparing OVHcloud with other providers at the same time, our framework for choosing a cloud provider helps structure the evaluation, and the guide to object, block and file storage explains the storage options you will meet in Public Cloud.
Where to read more #
OVHcloud’s official help center and documentation covers each product in depth, including getting-started guides for VPS, Public Cloud and dedicated servers. Current plans and rates are published on the official OVHcloud website; confirm prices there, since ranges and promotions change regularly.
Frequently asked questions #
Can I move from an OVHcloud VPS to Public Cloud later?
There is no one-click conversion between the two products. You typically build new Public Cloud instances, migrate your data and application, then switch DNS. Keeping configuration in scripts or cloud-init makes this much easier.
Is a dedicated server always faster than a VPS?
Not always. A dedicated server gives you the full, unshared machine, which helps with sustained load, but a well-sized VPS can outperform an older or entry-level dedicated model. Compare CPU generation, storage type and RAM, not only the product category.
Does OVHcloud Public Cloud work with Terraform?
Yes. You can use the OVHcloud Terraform provider and the OpenStack provider to manage Public Cloud resources as code, alongside the OVHcloud API and standard OpenStack tools.
Which option is best for a single WordPress site?
For most single sites, a VPS is the simplest and most cost-predictable choice. Consider Public Cloud only if you expect to scale out to multiple servers or need managed services.
