A bare metal server is a physical computer rented to a single customer, with your operating system installed straight onto the hardware and no provider hypervisor in between. If you’ve ever rented a dedicated server, you’ve rented a bare metal server; the two terms describe the same machine.
The name is literal. “Bare metal” means the bare hardware before anything is layered on it, so a bare metal environment is one where your OS, or your own hypervisor, is the first thing that runs when the box powers on. Below is what that changes in practice, when it’s worth paying for, and what to check before you rent one.
What “bare metal” means in practice
With a bare metal server you get the whole machine: every core, every DIMM, every drive bay and the network card. Nobody else’s workload runs on it. You get root (or Administrator on Windows), and with a decent provider you also get out-of-band access through IPMI, so you can watch it boot, change BIOS settings and reinstall the OS from a remote console.
Compare that with a virtual server. A VPS or cloud VM is a slice of a bigger physical host. The provider runs a hypervisor such as KVM on that host and carves it into virtual machines for many customers. You see virtual CPUs and virtual disks, and the hypervisor decides how real hardware gets shared out.
Dedicated servers vs cloud “bare metal instances”
The term gets muddy because cloud providers sell bare metal too. AWS launched instance types like m5.metal and r5.metal that, in AWS’s own words, give “direct access to the Intel Xeon Scalable processor and memory resources of the underlying server”. They’re aimed at the same jobs: running your own hypervisor, or software whose license or support terms demand a non-virtualized machine.
The hardware is just as single-tenant. The deal around it is different. A cloud metal instance is billed by the hour, sized as the entire host (so it’s the biggest and priciest size in its family), and lives inside the provider’s network, where outbound data is metered per GB. A dedicated server from a hosting company is usually rented by the month at a flat price, comes in a wider range of sizes down to small single-CPU boxes, and often includes a bandwidth allowance or an unmetered port.
Same physics, different invoice.
Bare metal vs VPS vs cloud VM
| Bare metal server | VPS | Cloud VM | |
|---|---|---|---|
| Who’s on the hardware | Only you | You plus other customers | You plus other customers |
| Hypervisor | None, or one you install | Provider’s | Provider’s |
| Performance hour to hour | Same every hour | Can dip when neighbors get busy | Mostly steady; burstable types throttle |
| Hardware access | Full root, BIOS, RAID, IPMI console | Root inside the VM only | Root inside the VM only |
| Run your own hypervisor | Yes | Rarely | Only on metal instance types |
| Billing | Flat monthly | Flat monthly | Per second or hour, plus per-GB egress |
| Time to get one | Hours to days (in-stock vs custom) | Minutes | Seconds to minutes |
| Best fit | Steady, heavy or licensing-sensitive work | Small sites, dev boxes | Spiky or short-lived load |
One quick way to see the difference: run top on a busy VPS and watch the st (steal) column. That’s time your virtual CPU wanted to run but the hypervisor gave the physical core to someone else. On bare metal there’s no one to steal from.
When you actually need a bare metal server
You need the same performance every hour
Databases, game servers, trading systems and build farms all care about the slow requests, not the average ones. On shared hardware, the worst hour of the week often lines up with someone else’s batch job. On a box nobody else touches, the numbers you benchmark on Monday are the numbers you get on Friday.
Your software is licensed per socket
Some licenses count physical hardware, and that’s much easier to pin down when the hardware is yours. A Proxmox VE subscription, for example, is required “for every occupied physical CPU socket”, and core count doesn’t change the price (Proxmox pricing). Oracle goes the other way in public cloud: its cloud licensing policy counts every four vCPUs as one socket for Database Standard Edition 2 and caps SE2 at eight vCPUs per instance. On a two-socket bare metal server you just count the two sockets.
You want to run your own hypervisor
This is a big one. Install Proxmox on a dedicated server and one machine becomes a small private cloud: your VMs, your storage layout, your backup schedule, and no per-VM fees to anyone. Nested virtualization inside a cloud VM is possible on some platforms, but it’s slower and fiddlier than running the hypervisor on real hardware.
A security questionnaire asks about tenancy
“One customer per physical machine” is an easy answer to give an auditor. Single tenancy doesn’t make you compliant on its own, though. Your controls, your patching and your access logs still do the heavy lifting.
You push a lot of traffic, all the time
A server averaging 300 Mbps out moves about 97 TB a month. Billed per GB, that egress can cost more than the server itself. On a flat monthly plan with a big allowance or an unmetered port, it’s a known number you budget once.
When you don’t need one
Plenty of workloads are better off virtual, and I’d rather you didn’t overbuy. If your app fits comfortably in 4 GB of RAM and two cores, a VPS is cheaper and you won’t notice the difference. The same goes for load that spikes for a few hours and then disappears, machines you need for an afternoon of testing, or stacks built on a cloud provider’s managed databases and queues. If nobody on your team will patch an OS or answer a failed-disk alert at 2 a.m., either buy a management plan or stay on a platform that hides the hardware from you.
Mixing is normal. A bare metal database server with app servers in the cloud is a very ordinary setup.
What to check before you rent one
- CPU model and generation. Ask for the exact model, not “8 cores”. An Intel Xeon E3-1230 is a 2011 Sandy Bridge chip with 4 cores, 8 threads and a 32 GB memory ceiling. That’s fine for a dev box or a small site and wrong for a busy database. Look up the model and check its memory limit before you pick RAM.
- IPMI or other out-of-band access. You want a remote console and power control for the day the OS won’t boot. Ask where the management interface lives. On the open internet is a bad answer, because those controllers are a favorite target.
- Network. Port speed, metered or unmetered, the overage rate if metered, whether a private network between your servers is included, and how many IPv4 addresses come with it. Ask for a test IP and run your own
mtrfrom where your users are. - Contract terms. Month to month or a 12-month term, setup fees, notice period to cancel, and what the SLA promises for hardware replacement.
- Delivery time. In-stock builds and custom builds are very different timelines. If you have a launch date, ask which one you’re actually ordering.
GigeNET’s bare metal servers
Every GigeNET dedicated server is single-tenant bare metal, with no hypervisor of ours between you and the hardware. The entry build is that Xeon E3-1230 v1 at $126 a month in Chicago and Los Angeles, with $0 setup and month-to-month terms. In-stock servers are delivered the same or next day, and custom builds take a week or less. IPMI sits on a private management network by default, and Proxmox is a $0 option on the order form. If you want something bigger, look at our bare metal servers in Chicago or the current dedicated server specials, or tell us the workload on the custom quote form and we’ll spec it.
Not ready to order yet?
Tell us what you’re after and we’ll email you the build and the price. Need it today? Call (800) 561-2656 and we’ll check what’s in stock.
FAQ
Is a bare metal server the same as a dedicated server?
Yes, in hosting they’re the same thing: one physical server, one customer. “Bare metal” stresses that there’s no provider virtualization layer, while “dedicated” stresses that nobody else shares it. The only real split is cloud bare metal instances, which are single-tenant too but billed hourly inside a cloud provider’s network.
What is a bare metal environment?
It’s a setup where software runs directly on physical hardware rather than inside a virtual machine. The OS, or a hypervisor you install yourself, talks straight to the CPU, memory and disks. People also use the phrase for the empty server before an OS goes on it.
Is bare metal faster than a virtual machine?
For most CPU-bound work, a modern hypervisor costs very little, so a VM with the same cores won’t feel much slower on an idle host. The bigger gap is consistency. On bare metal there are no neighbors, no CPU steal and no shared disk queue, so performance doesn’t swing with someone else’s workload.
Can I run VMs or containers on a bare metal server?
Yes, and it’s one of the main reasons to rent one. Install Proxmox, KVM, VMware ESXi or Docker and carve the machine up however you like. You get the flexibility of virtualization without paying per VM.