Compare / Deno Deploy vs Hetzner Cloud
Deno Deploy vs Hetzner Cloud
Pre-calculated from hand-checked data — Deno Deploy checked 2026-08-06, Hetzner Cloud checked 2026-08-06.
The short version
Deno Deploy wins more of our comparison points, but Hetzner Cloud still fits if european projects that need serious compute or move a lot of traffic describes you.
Price Deno Deploy
Deno Deploy is cheaper at most of the stages we model.
Ease Deno Deploy
Deno Deploy is easier to get running: connect GitHub for builds on every push or run deno deploy from the CLI; framework presets configure common JavaScript stacks automatically.
Control Hetzner Cloud
Hetzner Cloud gives you more control over the stack — the flip side of the convenience trade.
Free tier Deno Deploy
Deno Deploy has a free tier; Hetzner Cloud doesn't.
Features Deno Deploy
Deno Deploy comes out ahead on 9 of the 15 features we track, versus 2.
What developers say about this matchup
We couldn't find a substantive first-person discussion comparing this exact pair. We leave the section empty instead of filling it with vendor marketing or generic SEO comparisons.
At a glance
| Deno Deploy | Hetzner Cloud | |
|---|---|---|
| Best for | JavaScript and TypeScript sites, full-stack framework apps, and APIs that benefit from built-in previews, databases, cron, caching, and telemetry. | European projects that need serious compute or move a lot of traffic. |
| How deploys work | Connect GitHub for builds on every push or run deno deploy from the CLI; framework presets configure common JavaScript stacks automatically. | You get root on a bare server: bring your own setup, or use one-click apps like Docker and WordPress. |
| The tradeoff | It runs the Deno runtime, not Node itself, and its two-region managed footprint and $0.50/GB egress overage trail broader competitors. | Self-managed like any VPS, and the bandwidth advantage mostly applies to EU locations. |
| Free tier | Free: 1M requests, 20 GB egress, 15 CPU hours, 350 GB-hours of memory, and 1 GiB each of volume and KV storage per month. | None |
What you'd realistically pay
Deno Deploy Hetzner Cloud
| Project stage | Deno Deploy | Hetzner Cloud | Cheaper |
|---|---|---|---|
| Just starting | Free Free — A small app can stay inside the monthly allowance; it pauses if any enforced Free limit is exhausted. | ≈€5.99/mo CX23 (EU) — €5.49 + €0.50 IPv4. 2 shared vCPU, 4 GB RAM, 40 GB SSD, 20 TB traffic. Germany and Finland only. | Deno Deploy |
| Steady traffic | ≈$20/mo Pro — Includes 5M requests, 200 GB egress, 40 CPU hours, and 1,000 GB-hours of memory. | ≈€8.99/mo CX33 (EU) — €8.49 + €0.50 IPv4. 4 shared vCPU, 8 GB RAM, 80 GB SSD, 20 TB traffic. | Hetzner Cloud |
| Growing | ≈$30/mo Pro + request usage — A representative 10M-request month is $20 plus $10 request overage, before any CPU, memory, storage, or egress overage. | ≈€43.49/mo CCX13 (EU) — €42.99 + €0.50 IPv4. 2 dedicated vCPU, 8 GB RAM, 80 GB NVMe — move to dedicated CPUs when shared bursting stops being enough. | Deno Deploy |
Deno Deploy pricing notes
- Pro overages are $2 per million requests, $0.50 per GB of egress, $0.05 per CPU hour, and $0.016 per GB-hour of memory.
- Pro includes 5 GiB of volume storage and 5 GiB of Deno KV storage; extra storage and KV operations have separate usage rates.
- Free has no paid overage: applications pause when an allowance is exhausted. Free and Pro do not include a reliability SLA.
Hetzner Cloud pricing notes
- Traffic overage costs €1/TB in the EU — most providers charge 10–100x that per GB.
- Billed hourly up to a monthly cap.
- The Arm-based CAX plans match CX specs at similar prices if the Intel CX line is out of stock.
Our ratings
Ease of use Deno Deploy
Pricing clarity Hetzner Cloud
Free tier Deno Deploy
Scaling Deno Deploy
Control Hetzner Cloud
Feature by feature
Deno Deploy wins 9, Hetzner Cloud wins 2, with 4 even.
Deploy workflow
| Deno Deploy | Hetzner Cloud | |
|---|---|---|
| Deploy from Git push | Yes Link GitHub and every pushed commit triggers an integrated build with streamed logs and caching. | No No deploy pipeline — bring your own CI or scripts. |
| Preview deploys | Yes Every Git branch has its own timeline and URL, and every revision receives an immutable preview URL. | No Nothing built in. |
| Official CLI | Yes The deno deploy command creates, configures, and deploys applications from a terminal or CI pipeline. | Yes hcloud CLI manages servers, networks, and snapshots. |
| Instant rollbacks | Yes A timeline can be locked to any previous revision to restore it without rebuilding the application. | Partial Snapshots and paid backups restore machines; no deploy-level rollback. |
Platform
| Deno Deploy | Hetzner Cloud | |
|---|---|---|
| Custom domains + HTTPS | Yes Custom domains include automatic Let’s Encrypt certificates; wildcard domains require Pro or higher. | Yes Point DNS at the server; TLS is yours via certbot or a proxy. |
| Built-in CDN / edge network | Yes A built-in HTTP edge cache respects standard cache headers and supports tag-based global invalidation. | No No CDN product — put Cloudflare in front if needed. |
| Serverless functions | Yes JavaScript and TypeScript applications run in isolated serverless environments that start on demand. | No Not a VPS feature. |
| Docker containers | No Deno Deploy builds source code for its own Deno runtime and does not accept arbitrary Docker images. | Yes Docker CE one-click app or install it yourself. |
| SSH / shell access | No There is no interactive SSH shell; use build logs, runtime logs, traces, metrics, or the CLI. | Yes Full root SSH. |
| EU hosting region | Yes Applications can run in the managed Europe execution region, although database residency depends on the selected database. | Yes Germany and Finland are the home turf — this is where the value is. |
Runtime & operations
| Deno Deploy | Hetzner Cloud | |
|---|---|---|
| Automatic scaling | Yes The platform automatically starts multiple isolated application instances across or within regions as traffic requires. | No Manual resizing or manual fleet management. |
| Scale to zero | Yes Idle applications stop after an implementation-selected period between five seconds and ten minutes, then restart on request. | No Servers bill until deleted, even powered off. |
| Scheduled jobs | Yes Deno.cron jobs are discovered at deploy time, scheduled by the platform, and monitored in the dashboard. | Yes Classic cron on the box. |
| Managed database | Yes Provision Deno KV or managed Prisma Postgres, or attach an externally hosted PostgreSQL database. | No No managed database product — self-host or go external. |
| Logs & metrics built in | Yes Logs, OpenTelemetry traces, request and outbound-call metrics, filtering, and dashboards are included. | Partial Basic server graphs in the console; app-level monitoring is yours. |
Watch out for
Deno Deploy
- Applications run on Deno rather than Node itself. Node and npm compatibility is broad, including native add-ons and subprocesses, but framework-specific edge cases still exist.
- The managed platform currently has two execution regions, the US and Europe; Deploy Classic had a broader footprint before it shut down in July 2026.
- Free and Pro have no published reliability SLA; a 99.95% SLA is reserved for Enterprise.
- Free-tier apps pause when the monthly allowance is exhausted; there is no paid overage on Free.
Hetzner Cloud
- Hetzner raised prices on 15 June 2026: dedicated CCX and shared CPX plans roughly tripled, while the budget CX line rose about 35%.
- The cheap CX plans are sold in Germany and Finland only, in limited capacity — Hetzner sometimes pauses sales when stock runs out.
- US locations include only 1–2 TB of traffic versus 20 TB in the EU — the famous value is a European value.
- A public IPv4 address costs €0.50/month extra; only IPv6 is free.
- Servers bill until deleted, even while powered off.
Read the full reviews: Deno Deploy and Hetzner Cloud. Or answer four questions to see what fits your project.