Hetzner Cloud is one of the best-value cloud providers in Europe. Their VPS pricing is hard to beat: a 2 vCPU, 4 GB server for under €5 per month, with data centers in Nuremberg, Falkenstein, and Helsinki offering consistently strong performance. Developers who have priced infrastructure elsewhere know that Hetzner's rates are genuinely exceptional.
But there is a cost that Hetzner's pricing page does not show. Running a production application on a Hetzner VPS means configuring your own deployment pipeline, installing and maintaining a database, setting up SSL certificates, managing OS updates, and handling everything else that sits between a server and a running application. That engineering time adds up, and for most teams, it costs far more than the server itself.
Why Developers Consider Hetzner Alternatives
Hetzner gives you an excellent server. It does not give you a deployment platform. That distinction matters more than it initially appears, because every layer between the server and a production-ready application requires engineering work that Hetzner does not provide.
Server management is ongoing, not one-time. A fresh VPS requires OS hardening, user configuration, and firewall rules before your application can run. After that, OS security patches arrive regularly. Skipping them creates security exposure. Applying them requires testing and sometimes causes unexpected behavior in running services. This is not a deployment task — it is infrastructure operations.
No managed deployment pipeline. Deploying code to Hetzner means building your own process. Common approaches include running Ansible playbooks, setting up a Docker Compose workflow over SSH, configuring a GitHub Actions runner on the server, or using a CI/CD service that connects to the VPS via a deploy key. Each approach works, but each requires upfront investment and ongoing maintenance.
No managed databases. A Hetzner VPS does not include PostgreSQL. You install it, configure it, tune connection limits, set up backups, and maintain it across version upgrades. If the database becomes unavailable, you troubleshoot and recover it. For production data, this represents meaningful operational risk.
SSL certificates require manual configuration. Certbot with Let's Encrypt is the standard approach on self-managed servers. It works, but it requires initial Nginx or Caddy configuration, certificate auto-renewal setup, and occasional debugging when renewal fails silently.
No auto-scaling. When traffic spikes, a single Hetzner VPS handles it until CPU or memory saturates. Adding capacity means provisioning a new server, configuring it, adding it behind a load balancer, and distributing the application across both. Hetzner's load balancer is a separate paid service that requires its own configuration.
Monitoring requires separate tooling. Hetzner provides basic instance metrics. Application-level visibility — HTTP response times, error rates, log aggregation — requires installing and configuring Prometheus, Grafana, the ELK stack, or a third-party service.
This Is Not a Fair Comparison, and That Is the Point
Hetzner Cloud is an Infrastructure as a Service provider. They sell virtual machines: raw compute, storage, and networking. The value they deliver is real: exceptional hardware quality, competitive pricing, and reliable uptime in European data centers.
Out Plane is a Platform as a Service. It accepts your application code and handles everything required to run it in production: building, deploying, scaling, database management, SSL provisioning, monitoring, and load balancing.
These are different products solving different problems at different layers of the stack. Comparing their prices directly makes no more sense than comparing the cost of a car engine to the cost of a running vehicle.
The relevant comparison is total cost of ownership — what it costs to run your application in production across both approaches, including your engineering time. That comparison is less flattering to the raw server model. For a deeper analysis of this question, see The True Cost of Cloud Deployment.
Comparison: Hetzner Cloud vs. Out Plane
| Factor | Hetzner Cloud | Out Plane |
|---|---|---|
| What You Get | Virtual server (VPS) | Managed deployment platform |
| Deployment | DIY (SSH, Docker, CI/CD setup) | GitHub connect, then deploy |
| Server Management | Your responsibility | Managed |
| OS Updates | Manual | Managed |
| SSL Certificates | Manual (Certbot) | Automatic |
| Database | Install and manage yourself | Managed PostgreSQL |
| Auto-Scaling | Not available | Built-in |
| Monitoring | DIY (Prometheus, Grafana, etc.) | Built-in metrics and logs |
| Load Balancing | Hetzner LB (separate service) | Included |
| Billing | Hourly, minimum 1 hour | Per-second |
| Starting Price | ~€4.50/month (CX22) | Free tier + $20 credit |
| Engineering Time | 10–20 hours/month (estimated) | 1–2 hours/month |
| EU Data Centers | Nuremberg, Falkenstein, Helsinki | Nuremberg (same location) |
Total Cost of Ownership
Server pricing is visible on a pricing page. Engineering time is not. A realistic TCO analysis requires putting a number on both.
Hetzner Scenario
A typical small production setup on Hetzner: a CX22 server at €4.50 per month for compute, plus either a managed database elsewhere or a self-hosted PostgreSQL instance on the same server. Add Nginx or Caddy for reverse proxying, Certbot for SSL, a GitHub Actions runner or equivalent for deployments, and basic monitoring tooling.
Visible infrastructure cost: approximately €10 to €20 per month, depending on whether you add object storage, additional servers, or Hetzner's load balancer.
Engineering time: setup takes 20 to 40 hours for a production-grade configuration. Ongoing maintenance — OS patches, deployment pipeline issues, certificate renewals, database backups verification, incident response — typically runs 10 to 20 hours per month once the system is established.
At a conservative engineering rate of €50 per hour, 10 hours per month of infrastructure work costs €500 per month. At 20 hours, it is €1,000 per month.
True monthly cost: €510 to €1,020, including engineering time.
Out Plane Scenario
Deploy your application from GitHub. Out Plane builds it, runs it, and handles SSL automatically. Provision a managed PostgreSQL database from the console. Configure custom domains. Done.
Visible infrastructure cost: per-second compute plus managed database, variable by usage. New accounts start with $20 in free credit and 3 free instances on the Hobby plan.
Engineering time: initial setup takes 1 to 2 hours. Ongoing deployment work is minimal — push to GitHub, and the deployment happens. Infrastructure maintenance drops to near zero.
True monthly cost: a fraction of the self-managed equivalent, once time is priced honestly.
The difference narrows for teams with experienced DevOps engineers who are already performing this work. The difference widens for development teams where infrastructure work pulls engineers away from product development.
For a structured breakdown of how managed vs. self-hosted costs compare across scenarios, see Self-Hosted vs. Managed PaaS: Which Costs Less?.
When Hetzner Cloud Makes Sense
Hetzner remains an excellent choice in specific situations. Advocating for managed PaaS does not require dismissing the legitimate use cases for raw infrastructure.
You genuinely enjoy server administration. Some developers do. Managing infrastructure is a skill set that some engineers find rewarding and interesting. If your team has dedicated DevOps engineers and server management is work they want to do, Hetzner's pricing makes it an attractive platform.
You need specific OS or kernel configurations. Managed PaaS platforms run applications in containers on managed infrastructure. If your workload requires a particular kernel module, a custom OS build, or hardware-level configuration, a VPS gives you access that a container-based platform does not.
Non-web workloads with specific requirements. Game servers, VPN endpoints, media transcoding pipelines, and batch processing systems often have requirements that don't map cleanly to a web application deployment model. A raw VPS offers the flexibility to configure exactly what those workloads need.
Budget is the absolute constraint and engineering time is available. If you have engineers whose time would otherwise be unused — or if you are a solo developer who enjoys the work — the server cost savings are real. Hetzner's infrastructure quality justifies the choice.
Self-hosting open-source tools. Running Gitea, Nextcloud, Bitwarden, or other self-hosted applications on Hetzner with Coolify or CapRover is a popular and cost-effective model. See Best Coolify Alternative for a comparison of the self-hosted PaaS approach.
When Out Plane Is a Better Fit
Web applications, APIs, and SaaS products. If your deliverable is an application that handles HTTP traffic, Out Plane's deployment model is directly aligned with your workflow. Connect a GitHub repository, and the platform handles everything else.
Teams without dedicated infrastructure engineers. Development teams building product features should not spend significant time managing servers. Out Plane eliminates infrastructure work so engineers focus on application code. The same reasoning applies to solo founders and small teams where every hour counts.
Applications that need to scale. Per-second billing and automatic scaling mean you pay for actual load. When traffic increases, Out Plane adds instances within your configured bounds. When traffic drops, costs drop with it. This is not possible with a fixed-size VPS.
Projects where time to production matters. Configuring a production-grade Hetzner setup takes days. Deploying to Out Plane takes minutes. For teams validating new products or launching quickly, reducing infrastructure setup time has direct business value.
EU data residency requirements. Out Plane's default region is Nuremberg, Germany — the same data center location as Hetzner. Applications deployed on Out Plane benefit from the same geographic and legal advantages of EU hosting. For GDPR considerations and EU data residency, see GDPR-Compliant Hosting in Europe.
You want managed databases. Provisioning PostgreSQL on Out Plane takes two clicks in the console. The connection string is injected directly into your application's environment. Backups are automated. There is no database administration overhead.
The Middle Ground: Self-Hosted PaaS on Hetzner
A significant number of developers combine both approaches: run Coolify or CapRover on a Hetzner VPS to get a PaaS-like experience at Hetzner pricing.
This model is popular and reasonable. Coolify provides a web dashboard for deployments, handles Docker containers, and gives you Heroku-like functionality on infrastructure you control. Combined with Hetzner's pricing, it can reduce visible costs compared to managed PaaS.
The trade-off is that you still own the server Coolify runs on. OS updates, Coolify upgrades, security patches, and infrastructure incidents remain your responsibility. When a critical vulnerability is disclosed in Coolify — and the January 2026 disclosure of 11 CVEs including command injection and root key exposure is a recent example — you apply the patch yourself.
For a detailed comparison of this model against fully managed deployment, see Best Coolify Alternative.
How to Move from Hetzner to Out Plane
If you are running an application on Hetzner and want to eliminate server management overhead, migration is straightforward for most web applications.
Step 1: Containerize your application if it isn't already.
Out Plane deploys via Dockerfile or Paketo Buildpacks. If your application is a Node.js, Python, Ruby, Go, or Java project, Buildpacks will detect and build it automatically without a Dockerfile. If you prefer explicit control, add a Dockerfile to your repository root:
FROM node:20-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
EXPOSE 3000
CMD ["node", "server.js"]Step 2: Export your environment variables.
List every environment variable your application currently uses and collect their values. In Out Plane's console, these paste directly into the environment variable editor. If your current deployment uses a .env file on the server, copy its contents.
Step 3: Migrate your database.
If you are running PostgreSQL on the Hetzner VPS, dump the data:
pg_dump -U your_user -d your_database -Fc -f backup.dumpAfter provisioning a managed PostgreSQL database in Out Plane's console, restore the dump using the connection string provided:
pg_restore --no-acl --no-owner -d "your-outplane-connection-string" backup.dumpStep 4: Deploy.
Navigate to console.outplane.com and sign in with GitHub. Select your repository, choose Dockerfile or Buildpack, paste your environment variables, and deploy. Out Plane builds and deploys your application automatically. Subsequent pushes to your configured branch trigger redeployments without any manual action.
Step 5: Update your DNS.
Point your custom domain's CNAME record to your Out Plane application URL. SSL certificates provision automatically within minutes of DNS propagation. Once the application is verified running correctly, you can deprovision your Hetzner server.
Summary
Hetzner Cloud delivers exceptional value as an IaaS provider. The hardware quality, network performance, and pricing make it one of the best raw server options in Europe. For teams that want — or need — to manage their own infrastructure, it is a strong choice.
The limitation is not the server. The limitation is everything that sits between the server and a production-ready application, and the ongoing engineering time required to maintain it.
Out Plane operates from the same Nuremberg data centers as Hetzner, so EU data residency, latency, and geographic characteristics are comparable. The difference is that Out Plane handles deployment, SSL, databases, scaling, monitoring, and load balancing. Your team connects a GitHub repository and pushes code. The infrastructure layer is not your problem.
Key points:
- Hetzner provides raw VPS infrastructure; Out Plane provides a managed deployment platform
- The visible cost difference is real; the engineering time cost is larger and less visible
- Both platforms operate in Nuremberg, Germany — EU data residency applies to both
- Out Plane includes managed PostgreSQL, automatic SSL, built-in monitoring, and per-second billing
- Free tier includes 3 instances and $20 in credit — no credit card required to start
Ready to remove infrastructure overhead from your workflow? Get started with Out Plane and deploy your first application in minutes.