# Hetzner Dedicated Server: Complete Guide for 2026
> Everything you need to know about Hetzner dedicated servers in 2026. Covers the AX41, AX101, Hetzner Robot, Proxmox setup, pricing, and who should actually use bare-metal hosting.
- **Author**: rohan-kulkarni
- **Published**: 2026-06-17
- **Modified**: 2026-06-17
- **Category**: Deployment Guides
- **URL**: https://kuberns.com/blogs/hetzner-dedicated-server/
---
Hetzner dedicated servers are physical bare-metal machines rented from Hetzner Online. You get exclusive access to the full hardware, no shared CPU resources, no noisy neighbours, and no virtualisation overhead. For the right team, that is genuinely compelling hardware at a price point that is hard to find elsewhere.
The catch is the same as every bare-metal option: Hetzner delivers the physical server. Getting your application deployed, monitored, scaled, and maintained on that hardware is entirely your responsibility. Teams that want production-grade cloud infrastructure without that operational overhead should look at [Kuberns](https://kuberns.com), an Agentic AI platform that deploys your app from GitHub in under five minutes on AWS-backed infrastructure, with no server management required.
This guide covers what Hetzner dedicated servers are, how Hetzner Robot works, which plans to consider, how to run Proxmox, and who should actually be using bare-metal hosting in 2026.
### TL;DR
- Hetzner dedicated servers are physical machines with exclusive hardware access, managed through Hetzner Robot
- Popular models include the AX41 (Ryzen 5 3600, 64 GB RAM) and AX101 (Ryzen 9 7950X, up to 128 GB RAM)
- Proxmox and Docker run well on Hetzner hardware; Kubernetes requires self-managed setup
- Pricing starts from around 39 EUR per month for auction servers, with new dedicated models from around 49 EUR
- Dedicated servers require significant Linux and infrastructure expertise to operate in production
- Teams that want deployment without server management should use [Kuberns](https://kuberns.com) instead
## What Is a Hetzner Dedicated Server?
A Hetzner dedicated server is a physical machine hosted in Hetzner's data centres in Nuremberg, Falkenstein, and Helsinki. Unlike a cloud VPS, where resources are divided across multiple tenants on the same physical host, a dedicated server gives you the entire machine to yourself.
That means full CPU access with no noisy neighbour effects, direct NVMe or SATA storage with no shared I/O contention, and a known hardware configuration you can rely on for consistent performance. You install your own operating system, configure everything via SSH, and have root access to the full stack.
Hetzner manages the physical hardware, the network, and the data centre. You manage everything from the OS upward.
Dedicated servers at Hetzner are managed through **Hetzner Robot**, a separate control panel that is distinct from the Hetzner Cloud Console. If you have only used Hetzner Cloud, Robot is a different product with a different interface.
## What Is Hetzner Robot?
Hetzner Robot is the management panel for all Hetzner dedicated servers. It is where you order servers, manage your billing, and access the controls that let you operate your physical hardware remotely.
Key things you do through Robot:
- **Order and configure dedicated servers.** Choose your server model, select additional IP addresses, and set up your initial operating system.
- **Reinstall the OS.** Use the Hetzner installimage tool to wipe and reinstall any supported Linux or Windows distribution without physically touching the hardware.
- **Access the rescue system.** Boot into a live environment for remote recovery when your main OS becomes unreachable. This is how you fix broken bootloaders, corrupted file systems, or misconfigured networking without needing physical access.
- **Manage IP addresses and subnets.** Add additional single IPs, /29 through /24 subnets, and configure reverse DNS for your addresses.
- **Set up firewall rules.** Hetzner Robot includes a stateless firewall that filters incoming and outgoing traffic before it reaches your server.
- **Configure vSwitch connections.** Connect multiple dedicated servers across Hetzner locations using a private VLAN without routing traffic over the public internet.
Robot does not do deployment, CI/CD, or application management. It is purely for infrastructure-level server management.
## Hetzner Dedicated Server Plans in 2026
Hetzner offers dedicated servers under two main categories: the **AX series** powered by AMD Ryzen processors, and the **EX series** powered by Intel Xeon processors. There is also a **server auction** where decommissioned and refurbished hardware is available at lower prices.
### AX Series: AMD Ryzen Dedicated Servers
The AX series is built on AMD Ryzen consumer and workstation CPUs. These processors offer high core counts and strong multi-threaded performance at a price point that makes them popular for virtualisation, home labs, and self-hosted applications.
| Model | CPU | RAM | Storage | Uplink | Price |
|---|---|---|---|---|---|
| AX41 | AMD Ryzen 5 3600 | 64 GB DDR4 | 2x 512 GB NVMe | 1 Gbit | ~49 EUR/month |
| AX42 | AMD Ryzen 7 PRO 8700GE | 64 GB DDR5 | 2x 512 GB NVMe | 1 Gbit | ~65 EUR/month |
| AX102 | AMD Ryzen 9 7950X3D | 128 GB DDR5 ECC | 2x 1.92 TB NVMe | 1 Gbit | ~120 EUR/month |
| AX162 | AMD EPYC 9454P | 128 GB DDR5 ECC | 2x 1.92 TB NVMe | 1 Gbit | ~220 EUR/month |
### The Hetzner AX41: What You Get
The AX41 is one of the most popular Hetzner dedicated servers for developers and self-hosters. It runs an AMD Ryzen 5 3600, a six-core, twelve-thread Zen 2 processor with strong multi-threaded performance for the price.
**Specifications:**
- CPU: AMD Ryzen 5 3600 (6 cores / 12 threads, up to 4.2 GHz)
- RAM: 64 GB DDR4
- Storage: 2x 512 GB NVMe SSD
- Network: 1 Gbit uplink, unlimited traffic
- DDoS protection: included
- IPv4 and IPv6: included
The AX41 is a solid starting point for teams running multiple containerised applications, a self-hosted Kubernetes cluster, Proxmox virtualisation with several VMs, or compute-heavy services that benefit from dedicated CPU resources without shared tenancy.
### The Hetzner AX101: High-End Bare Metal
The AX101 sits at the high end of the Ryzen lineup. It uses the AMD Ryzen 9 7950X, a 16-core, 32-thread processor with strong single-thread and multi-thread performance.
**Specifications:**
- CPU: AMD Ryzen 9 7950X (16 cores / 32 threads, up to 5.7 GHz)
- RAM: 128 GB DDR5 ECC (upgradeable to higher configurations)
- Storage: 2x 960 GB NVMe SSD
- Network: 1 Gbit uplink, unlimited traffic
- DDoS protection: included
The AX101 is suited to large virtualisation environments, high-traffic self-hosted services, video processing or rendering workloads, and any application that genuinely needs 16 dedicated cores and high-speed DDR5 memory.
### EX Series: Intel Xeon Dedicated Servers
The EX series runs Intel Xeon processors and is designed for workloads that require ECC RAM, specific Intel features, or compatibility with software that performs better on Xeon architecture. Pricing is broadly comparable to the AX series for similar hardware configurations.
### Hetzner Server Auction
Hetzner's server auction (accessible through Robot) lists refurbished and decommissioned dedicated servers at reduced prices. Servers in the auction are functional but may have older hardware configurations. Pricing starts from around 30 to 39 EUR per month.
The auction is a good option for teams that want to experiment with bare-metal hosting at a lower cost before committing to a current-generation server. Hardware is still hosted in Hetzner's data centres with the same physical support and network quality.
## How to Set Up Proxmox on a Hetzner Dedicated Server
Proxmox VE is one of the most common use cases for Hetzner dedicated servers. It turns a single physical machine into a full virtualisation host, allowing you to run multiple virtual machines or LXC containers with a web-based management interface.
Here is how the setup works at a high level.
**Prerequisites:**
- A Hetzner dedicated server (AX41 or similar)
- Access to Hetzner Robot
- An additional IP address or subnet ordered through Robot (required for VM networking)
- Basic Linux and networking knowledge
### Step 1: Boot Into the Hetzner Rescue System
In Hetzner Robot, navigate to your server, open the **Rescue** tab, select a rescue OS (typically Debian or Ubuntu), and activate the rescue system. Reboot the server through Robot. Your server will boot into a temporary live environment accessible via SSH.
### Step 2: Install Proxmox Using installimage
Once connected to the rescue system via SSH, run the Hetzner `installimage` tool:
```bash
installimage
```
Select **Other** and then choose **Proxmox VE** from the available images. The installer presents a configuration file where you set your hostname, partition layout, and RAID configuration. Save and confirm. The installer writes Proxmox to disk and reboots the server.
### Step 3: Configure Networking for VMs
After rebooting into Proxmox, you need a network bridge so your VMs can reach the internet. Because Hetzner uses routed networking rather than bridged networking at the host level, VM traffic must route through your server's main IP using either a virtual MAC address per VM or masquerading with NAT.
For each VM that needs a public IP, request a virtual MAC address through Hetzner Robot and assign the additional IP to that VM's network interface.
### Step 4: Access the Proxmox Web Interface
Proxmox runs a web interface on port 8006. Connect to `https://your-server-ip:8006` and log in with the root credentials you set during installation. From here you can create VMs, manage storage, configure backups, and monitor resource usage across your virtualisation environment.
### Step 5: Harden and Secure Your Setup
Before putting workloads on the server, disable password-based SSH in favour of key-based authentication, set up the Hetzner Robot firewall to restrict access to Proxmox's web interface, configure automated backups using Proxmox's built-in backup scheduler, and enable email alerts for critical events.
## What Hetzner Dedicated Servers Are Good For
Bare-metal hosting at Hetzner makes sense for a specific set of use cases.
**Consistent, high-performance compute.** When you need predictable CPU and RAM without the variance that comes from shared cloud infrastructure, a dedicated server delivers that. Workloads like video encoding, scientific computing, large database servers, and high-traffic applications all benefit from exclusive hardware.
**Self-hosted infrastructure at scale.** Running a Proxmox cluster with dozens of VMs, a self-hosted Kubernetes setup with k3s, or a large Docker Swarm deployment is significantly cheaper on Hetzner bare metal than on equivalent cloud VMs.
**Privacy and data sovereignty.** Hetzner's European data centres make dedicated servers an attractive option for teams with strict GDPR requirements or data residency obligations. You know exactly where your hardware is and who has physical access to it.
**Cost at high utilisation.** Dedicated servers become cost-effective when the machine runs at high utilisation continuously. A cloud VM that scales up and down saves money for variable workloads. A dedicated server running at 80 to 90 percent utilisation around the clock is typically cheaper than an equivalent cloud compute spend.
## What Hetzner Dedicated Servers Are Not Good For
Bare-metal hosting is the wrong choice for most application teams. Here is where the real friction shows up.
**There is no deployment layer.** Hetzner gives you a server. Getting your application onto that server, configured with Nginx, SSL, CI/CD, environment variables, and process supervision, is work your team does manually. None of it is provided. A developer new to Linux can easily spend two to three days just getting a basic app live for the first time.
**Scaling requires manual intervention.** If your app gets a traffic spike at midnight, there is no autoscaling. You provision another server through Robot, wait for it to come online, configure it, install your stack, and update your load balancer manually. By the time that is done, the traffic may have already passed.
**No managed services out of the box.** Hetzner dedicated servers come with bare hardware. There are no managed databases, no built-in load balancers, no object storage tied to your account. Each service you need has to be either self-hosted on the same machine or sourced separately and wired in. Every addition to your stack is another thing to configure, secure, and maintain.
**Account verification is slow and unpredictable.** Hetzner's fraud prevention process can hold new accounts for hours or days before server orders are approved. Teams that need infrastructure quickly regularly run into this wall with no clear timeline for resolution.
**Limited global coverage.** Hetzner's dedicated server locations are in Germany and Finland. If your users are in Asia, South America, or the Middle East, there is no data centre option to reduce latency for them. Hyperscalers and managed platforms that run on AWS or GCP infrastructure offer far broader reach without any extra configuration.
**Knowledge walks out the door.** A dedicated server setup is only as reliable as the person who built it. When a DevOps engineer or the one developer who configured everything leaves the team, the institutional knowledge of how the server is structured often goes with them. Undocumented Nginx rules, custom systemd services, and manual SSL renewals become landmines.
**Failure is entirely your problem.** When your application goes down at 2 AM, you SSH in and fix it. Hetzner supports the physical hardware. Everything above the OS is on you. There is no platform team to escalate to, no monitoring built in, and no automatic recovery.
If your team wants production-grade hosting without owning the infrastructure layer, [Hetzner Cloud pricing](https://kuberns.com/blogs/hetzner-cloud-pricing/) documents the managed cloud option, and [what Hetzner Cloud offers](https://kuberns.com/blogs/what-is-hetzner-cloud/) covers the VPS product in detail.
## The Faster Path to Production: Deploy on Kuberns
For most teams building applications in 2026, the infrastructure work that bare-metal hosting requires is not a competitive advantage. It is overhead. Every hour spent on Nginx configs, SSL renewals, and CI/CD pipelines is an hour not spent on the product itself.
Here is what the gap actually looks like in practice:
| Task | Hetzner Dedicated | Kuberns |
|---|---|---|
| Get app live | Hours to days of server setup | Under 5 minutes |
| SSL certificate | Manual Certbot setup and renewal | Automatic, always current |
| CI/CD on push | Build your own GitHub Actions pipeline | Built in, zero config |
| Traffic spike | Provision servers manually | Autoscales automatically |
| App goes down at 2 AM | You SSH in and debug | Platform handles recovery |
| New team member onboards | Weeks to learn the setup | Push to branch and deploy |
[Kuberns](https://kuberns.com) is an Agentic AI cloud platform that handles the entire deployment lifecycle automatically. Connect your GitHub repository, set your environment variables, and click deploy. Kuberns detects your stack, builds your app, provisions HTTPS, and sets up CI/CD from your connected branch. Your app is live on AWS-backed infrastructure in under five minutes, with no server to manage and no DevOps knowledge required.
**What you need:**
- A GitHub repository with your application code
- Environment variables your application needs in production
### Step 1: Create a Kuberns Account
Go to [dashboard.kuberns.com](https://dashboard.kuberns.com) and sign up using your Google or GitHub login. No credit card is required to start.
### Step 2: Create a New Project and Connect GitHub
Click **New Project**, connect your GitHub account, and select the repository and branch you want to deploy.
### Step 3: Review Auto-Detected Settings
Kuberns scans your repository and automatically detects your framework, build command, and start command. Review the pre-filled settings and adjust only if something looks off. For most standard frameworks, nothing needs changing.
### Step 4: Add Environment Variables
Navigate to the **Environment** tab and add your API keys, database URLs, and any other values your app needs at runtime. Kuberns encrypts and injects them securely at deploy time.
### Step 5: Click Deploy
Press **Deploy**. Kuberns provisions your infrastructure on AWS, issues an SSL certificate, sets up CI/CD from your connected GitHub branch, and makes your app live at a public HTTPS URL. Every subsequent push to that branch triggers an automatic redeploy with zero manual steps.
## Frequently Asked Questions
### What is a Hetzner dedicated server?
A Hetzner dedicated server is a physical bare-metal machine rented from Hetzner Online. You get exclusive access to all hardware resources including CPU, RAM, and storage without sharing them with other tenants. Hetzner manages the physical hardware and data centre infrastructure. You manage the operating system, software, and everything running on top of it.
### What is Hetzner Robot?
Hetzner Robot is the control panel used to manage Hetzner dedicated servers. It is separate from the Hetzner Cloud Console. Through Robot you can order servers, reinstall the operating system, access the rescue system for remote recovery, configure firewall rules, manage IP addresses and subnets, and set up vSwitch connections between dedicated servers. It is the primary interface for all bare-metal server management at Hetzner.
### What is the Hetzner AX41?
The Hetzner AX41 is an AMD Ryzen 5 3600 based dedicated server with 64 GB DDR4 RAM and two 512 GB NVMe SSDs. It is part of the AX series designed for multi-threaded workloads and fast read and write operations. It suits self-hosted applications, game servers, home lab setups, and any workload that benefits from high core count AMD processors.
### What is the Hetzner AX101?
The Hetzner AX101 is a high-performance dedicated server based on AMD Ryzen 9 7950X with up to 128 GB DDR5 ECC RAM and 2x 960 GB NVMe SSDs. It handles compute-intensive workloads, large virtualisation environments, and applications that require consistent high single-thread and multi-thread performance.
### How do I run Proxmox on a Hetzner dedicated server?
Boot into the Hetzner rescue system from Robot, run the installimage tool and select Proxmox VE, configure the partition layout, and allow the installer to write Proxmox to disk. After reboot, set up a network bridge with virtual MAC addresses for VM networking, then access the Proxmox web interface on port 8006. Additional IP addresses or subnets from Robot are required to give each VM a public IP.
### How much does a Hetzner dedicated server cost?
Hetzner dedicated server pricing starts from around 39 EUR per month for auction servers. The AX41 costs around 49 EUR per month. Higher-tier servers like the AX101 are priced upward of 120 EUR per month. All dedicated servers include unlimited traffic and a 1 Gbit uplink. Pricing excludes the engineering time required to configure and maintain the server.
### What is the difference between Hetzner Cloud and Hetzner dedicated servers?
Hetzner Cloud offers virtual machines that can be created and deleted on demand with hourly billing. Dedicated servers are physical machines rented monthly with exclusive hardware access. Cloud servers are more flexible for variable workloads. Dedicated servers offer consistent raw performance and are suited to teams that need high compute, full hardware control, or maximum cost efficiency at sustained high utilisation.
### Is a Hetzner dedicated server good for Docker or Kubernetes?
Yes. Hetzner dedicated servers are popular for self-managed Docker and Kubernetes workloads, particularly for teams that want bare-metal performance without hyperscaler costs. Tools like k3s, k3sup, and hetzner-k3s make Kubernetes cluster provisioning on Hetzner hardware straightforward. The tradeoff is that you own cluster setup, upgrades, and ongoing maintenance entirely.
## Final Thoughts
Hetzner dedicated servers are genuinely excellent hardware for the teams that need them. If you have the DevOps skills to run bare metal, a workload that benefits from exclusive CPU resources, and users primarily in Europe, the price-to-performance ratio is hard to beat anywhere in the market.
But bare-metal hosting asks a lot in return. You own the operating system, the deployment pipeline, the monitoring stack, the SSL certificates, the scaling decisions, and the 2 AM incident response. For a team with a dedicated infrastructure engineer, that tradeoff makes sense. For everyone else, it is a significant ongoing tax on engineering time.
Most teams searching for a Hetzner dedicated server are not looking to become infrastructure experts. They are looking to ship software reliably without spending more than they need to. If that describes your team, the honest answer is that bare metal is not the right starting point.
[Kuberns](https://dashboard.kuberns.com) gets your app live in under five minutes on AWS-backed infrastructure, with autoscaling, CI/CD, HTTPS, and monitoring handled automatically. No servers to manage. No expertise required. [Try it free and see how fast deployment can actually be.](https://dashboard.kuberns.com)
---
- [More Deployment Guides articles](https://kuberns.com/blogs/category/deployment-guides/1/)
- [All articles](https://kuberns.com/blogs/)