Choosing between Hetzner and AWS for email server hosting comes down to cost versus ecosystem. Hetzner delivers some of the best price-performance in European infrastructure. AWS offers unmatched global reach and managed service integration. For email specifically, each has critical differences that affect deliverability, setup complexity, and total cost of ownership.
| Criteria | Hetzner | Amazon AWS |
|---|---|---|
| Entry server cost (4 vCPU, 16GB RAM) | €14.51/month (Hetzner Cloud CX32) | ~$80–$120/month (c6i.xlarge, on-demand) |
| Dedicated IPv4 (one address) | Included with server | $0.005/hour (~$3.60/month additional) |
| Outbound bandwidth | 20TB included per month | $0.09/GB after 100GB (1M emails ≈ ~50GB ≈ $4.50) |
| Port 25 outbound (direct SMTP) | Open — no request required | Blocked by default; must submit support request (not guaranteed) |
| IP reputation of new addresses | Generally clean — Hetzner network has decent email reputation | Mixed — AWS IP space heavily monitored by ISPs; new IPs often get extra scrutiny |
| Global datacenters | EU (Germany, Finland) + US (Virginia, Oregon) | 30+ regions worldwide |
| Managed services (DNS, load balancing) | Basic — Hetzner DNS and load balancer available | Extensive — Route53, ALB, SES, CloudWatch, etc. |
| Setup time for email server | 30 minutes to a running Postfix instance | 2–4 hours with AWS expertise required |
| Support for email senders | Community + ticket support | AWS support tiers — basic is limited |
| Typical monthly cost for email infrastructure | €40–€120/month all-in | $100–$300/month depending on services used |
The core difference is economics and simplicity versus ecosystem depth. Hetzner is a German provider known for delivering excellent hardware value at transparent pricing. A Hetzner CX32 (4 vCPU, 16GB RAM, 80GB SSD) costs €14.51/month — a comparable EC2 instance on AWS costs 5–8x more. For email infrastructure where you're primarily running an MTA and don't need AWS's managed services, Hetzner's cost advantage is decisive.
Hetzner is the right choice for cost-focused European email senders who don't need deep AWS integration.
AWS is the right choice for teams already operating in the AWS ecosystem or needing global multi-region infrastructure.
Port 25 access is the most important technical consideration for email senders on AWS. Amazon blocks port 25 outbound by default on all EC2 instances to prevent abuse. To send email on port 25, you must submit a request through the AWS console explaining your use case. AWS approves these requests at their discretion — there is no guarantee of approval, and the review process can take days. For email infrastructure, this is a significant operational friction point that Hetzner doesn't impose. Port 587 (authenticated submission) remains open on both platforms, but MTA-to-MTA delivery (the actual SMTP connection to recipient mail servers) requires port 25.
Total monthly cost for a production email infrastructure on Hetzner: €40–€120/month covering the server, additional IPs (€2–4 per IP), and Hetzner DNS (free). On AWS, the same configuration costs $100–$300/month including EC2, Elastic IPs, Route53, and data transfer — before any premium support. Over 12 months, Hetzner saves €600–€2,000+ compared to equivalent AWS infrastructure for a typical email server deployment.
For most European email infrastructure deployments, Hetzner's cost advantage, open port 25 access, and clean IP reputation make it the better choice. AWS makes sense when you need deep ecosystem integration, global presence beyond EU+US, or when your team's AWS expertise makes it operationally simpler despite the higher cost. The decision is rarely about technical superiority — both can run excellent email infrastructure — and almost entirely about cost, familiarity, and integration requirements.
Every email program is different. Our infrastructure team has helped hundreds of senders make the right architecture decisions. Talk to us — no commitment required.
Discuss Your SituationWhen evaluating Hetzner versus Aws Email Server, the most important comparison isn't price or feature count — it's the underlying infrastructure architecture and how that architecture affects the metrics that matter: inbox placement rates, deliverability during volume spikes, control over authentication configuration, and response time when problems occur.
Infrastructure choices made today compound over time. A shared platform that generates acceptable deliverability at 100K emails per month may create significant problems at 1M — not because the platform changed, but because shared IP reputation becomes more volatile as volume increases and ISP throttling behavior changes. Understanding the architecture each option represents — not just its current feature set — is critical for making a decision that remains right at scale.
The most significant infrastructure difference between Hetzner and dedicated email infrastructure is IP reputation isolation. In any shared sending environment, your inbox placement rate is determined not only by your own sending behavior but by the behavior of every other sender using the same IP pool. A campaign from another sender that generates high complaint rates — which you have no visibility into and no control over — can degrade your inbox placement within hours.
Dedicated infrastructure eliminates this dependency entirely. Your IPs are yours exclusively. Your reputation is a direct function of your own list quality, your own complaint rate, your own engagement signals. Good operators with well-managed sending programs consistently achieve 95–98% inbox placement at Gmail. That performance doesn't depend on what any other sender does, because no other sender shares your infrastructure.
Email authentication — SPF, DKIM, DMARC — has become more consequential in 2024–2025 following Google and Yahoo's bulk sender requirements mandating proper authentication for all senders above 5,000 daily messages. The question isn't just whether authentication is set up correctly, but who controls it and how quickly problems can be diagnosed and resolved.
With dedicated infrastructure, authentication records are under your direct control. You own the DKIM private keys. Your SPF record explicitly authorizes your IPs. Your DMARC policy is configured at the level appropriate to your security requirements. When a delivery problem traces back to an authentication failure, the investigation and fix require one team — yours — rather than a support ticket to a shared platform.
Every major ISP applies different throttle limits to incoming mail. Gmail has different per-IP hourly limits than Outlook, which differ from Yahoo's limits. These limits scale with established reputation — an IP with HIGH reputation at Gmail can send at significantly higher rates than a new IP or one with MEDIUM reputation. Without per-ISP throttle control, high-volume sends either hit these limits and generate deferred messages, or must be configured conservatively enough for the most restrictive ISP — leaving capacity on the table with ISPs that would accept higher volumes.
Dedicated infrastructure with a commercial MTA (PowerMTA for high-volume operations, or optimized Postfix) allows fine-grained per-ISP configuration: different connection limits, different messages-per-connection values, different retry schedules for each destination domain. This operational control translates directly to faster delivery of large sends and better utilization of available reputation capital.
Mixing transactional email (password resets, purchase confirmations, 2FA codes) and marketing email on the same IP pool creates a structural risk: a complaint spike from a poorly-performing marketing campaign can delay the delivery of transactional messages that customers expect immediately. A user waiting 30 minutes for a password reset email because a marketing campaign degraded the sending IP's reputation doesn't experience this as an "email marketing problem" — they experience it as a broken product.
Dedicated infrastructure implements this isolation architecturally: separate IP pools for separate sending streams, each with independent reputation, independent queue management, and independent monitoring. Transactional email maintains sub-minute delivery times regardless of what's happening in the marketing email queue.
A complete cost comparison must account for more than the monthly service fee. The true comparison is cost per inbox-delivered email — accounting for both the infrastructure cost and the inbox placement rate each option delivers.
| Metric | Shared ESP / Hetzner | Dedicated Infrastructure |
|---|---|---|
| Typical inbox placement | 72–82% | 94–98% |
| IP reputation control | Shared pool | Fully isolated |
| Per-ISP throttle config | Platform-managed | Full control |
| Stream isolation | Add-on or unavailable | Native support |
| Blacklist response time | Support ticket | <2 hours managed |
| Authentication ownership | Platform default | Full ownership |
At 1 million emails per month: a 15% inbox placement improvement (from 82% to 97%) means 150,000 additional emails reaching the inbox. If email revenue is $0.10 per inbox-delivered email, that's $15,000 per month in additional revenue from the same sending volume. Against a typical dedicated infrastructure premium of $300–$500 per month over comparable ESP pricing, the ROI case is compelling at any meaningful commercial email program.
Moving from Hetzner to dedicated infrastructure is not a flip-the-switch operation. The transition requires: domain authentication reconfiguration (updating DKIM keys, revising SPF records to include new sending IPs, updating DMARC records), IP warm-up on the new dedicated IPs (4–12 weeks to reach full production volume), and monitoring of the transition period to ensure new infrastructure performs as expected before decommissioning the old setup.
The warm-up requirement is the most significant timeline consideration. You cannot move 1 million emails per month from day one onto a new dedicated IP — the IP needs to build reputation incrementally. The practical approach is to run old and new infrastructure in parallel during warm-up, shifting volume progressively as the new IP establishes reputation.
Our infrastructure team manages this migration process for clients transitioning from shared ESPs, minimizing risk and ensuring continuity of deliverability during the transition period.
The right choice between these two options isn't universal — it depends on your specific sending program, team capabilities, budget, and performance requirements. Here's a structured framework for making the decision:
One dimension of the comparison that's often overlooked is operational visibility: how much information do you have about what's happening with your email delivery, and how quickly can you respond when something goes wrong?
Shared platforms typically provide: campaign-level delivery statistics, aggregate bounce and complaint data, and a support ticket process for investigating problems. When a deliverability incident occurs — a sudden inbox placement drop, a blacklist listing affecting one ISP, an authentication failure — the investigation pathway runs through the platform's support team, which has other customers to serve and may not prioritize your issue at the speed your business requires.
Dedicated infrastructure with proper monitoring provides: per-IP delivery data segmented by recipient ISP, real-time DNSBL monitoring with immediate alerting, direct access to MTA logs for granular delivery investigation, Gmail Postmaster Tools domain and IP reputation in real time, Microsoft SNDS data, and Yahoo FBL complaint data within hours of complaints occurring. When a deliverability incident occurs, the investigation starts immediately with your team — not after a support ticket is routed and triaged.
This operational visibility difference matters most during two scenarios: active deliverability incidents (where speed of detection and response directly determines the extent of the damage) and ongoing optimization (where granular per-ISP data enables specific improvements that aggregate statistics can't identify).
Email infrastructure decisions have compounding consequences. Reputation built on dedicated IPs accumulates over time — an IP with 3 years of clean sending history has a reputation buffer that absorbs occasional performance fluctuations that would significantly damage a newer IP. That accumulated reputation has real economic value: better inbox placement rates, higher acceptable sending volumes without throttling, faster recovery when problems occur.
The ISP environment is also becoming more authentication-demanding, not less. Gmail's 2024 bulk sender requirements, Yahoo's authentication mandates, and BIMI adoption by Gmail and Apple Mail are all trends in the direction of more rigorous authentication standards. Dedicated infrastructure with direct control over authentication configuration is better positioned to adapt to these evolving requirements than platforms where authentication configuration is managed by a third party.
For organizations evaluating this choice as a long-term infrastructure decision rather than a short-term cost comparison, the trajectory of the industry consistently favors dedicated infrastructure with direct authentication control and IP reputation ownership as the path to sustainable high deliverability.
Deliverability outcomes depend on infrastructure architecture, not just configuration settings. Shared platforms mean your inbox placement is partly a function of other senders' behavior on the same IP pool. Dedicated infrastructure means your deliverability is entirely controlled by your own sending practices — better or worse, the results are yours alone. For organizations with well-managed sending programs, this control translates into consistently higher inbox placement rates.
Migration requires three parallel workstreams: (1) Authentication reconfiguration — updating SPF records, generating new DKIM keys, updating DMARC records to reflect new infrastructure; (2) IP warm-up — new dedicated IPs must be warmed gradually over 4–12 weeks before reaching full production volume; (3) Traffic transition — shifting sending volume from old to new infrastructure progressively as the new IP builds reputation. Running both systems in parallel during the transition minimizes risk and ensures continuity.
The economics typically favor dedicated infrastructure at 300,000–500,000 emails per month for self-managed, and 500,000–800,000 for fully managed. But volume is only one factor — the nature of the email program matters equally. Transactional programs with high per-email value may justify dedicated infrastructure at much lower volumes. Programs experiencing deliverability problems attributable to shared IP reputation may find the switch economically justified at any volume where the revenue impact of better inbox placement exceeds the infrastructure premium.
On shared platforms, blacklist management is handled by the platform — but you have no visibility into whether a shared IP is currently blacklisted, and you can't prioritize remediation. With dedicated infrastructure and 24/7 monitoring, blacklist listings are detected within minutes and addressed within the stated SLA (typically 2 hours). You also have the option to rotate to a clean IP while the listed IP is being remediated, maintaining delivery continuity during the incident.
Our infrastructure team can analyze your current sending program and provide a specific recommendation on whether dedicated infrastructure makes sense for your volume and use case — including a realistic timeline and migration plan.
Request Infrastructure Assessment →