Best forNext.js apps — zero-config deploys and preview URLs.
Trade-offThe Hobby plan is non-commercial; costs grow with usage.
Used by 2,014 makers' products for this
Of the 860 products launched in 2026 that we know the hosting of, 1% use Hetzner Cloud, against 3% of those launched in 2023 or earlier. The most picked now is Vercel (57%, up from 54%). On GitHub, 8 public pull requests since Oct 2024 moved projects off Hetzner Cloud: Amazon Web Services (8); 19 moved to Hetzner Cloud.
2 of the 20 are open source or self-hostable (Coolify and SST) and 12 have a free tier. For a team of 5 with 10,000 users, the cheapest is Cloudflare at $12 a month on Workers Paid, against $13 for Hetzner Cloud on CPX12.
Not a ranking: each option is described by the situation it fits, with its trade-off.
The share of makers' products we track that use each for hosting, by the year they launched on Product Hunt. The stack is the one we see today, not the one it launched with; a product can use more than one.
| Option | Launched ≤2023 · 207 | Launched 2024 · 582 | Launched 2025 · 629 | Launched 2026 · 860 |
|---|---|---|---|---|
| 54% | 54% | 60% | 57% | |
| 11% | 7% | 10% | 20% | |
| 17% | 10% | 14% | 9% | |
| 1% | 2% | 4% | 8% | |
| 8% | 6% | 7% | 6% | |
| 3% | 5% | 3% | 1% |
Public pull requests on GitHub since Oct 2024 whose title says "Hetzner Cloud to …" or "… to Hetzner Cloud": real code changes, by developers in general, not only makers. Each count opens the search that finds them.
| Tool | Moved from Hetzner Cloud | Moved to Hetzner Cloud | |
|---|---|---|---|
| 8 | 8 | ||
| 0 | 11 |
How many makers' products we track use each for hosting, and what each costs for a team of 5 with 10,000 users.
| Option | Kind | Makers' products | Team of 5, 10,000 users | Free tier | Open source | |
|---|---|---|---|---|---|---|
| Your own server | 110 | $13/mo · CPX12 | No | No | ||
| Frontend cloud | 2,014 | $120/mo · Pro + Flat Rate CDN 10M | Yes | No | ||
| Hyperscaler cloud | 460 | $17/mo · Pay as you go (Lambda + EC2 t4g.small) | Yes | No | Compare → | |
| Edge platform | 385 | $12/mo · Workers Paid | Yes | No | ||
| Frontend cloud | 265 | $30/mo · Pro 3,000 credits | Yes | No | ||
| PaaS | 137 | $61/mo · Pro | Yes | No | ||
| PaaS | 124 | $45/mo · Pro | No | No | Compare → | |
| Container platform | 74 | $15/mo · Pay As You Go | No | No | Compare → | |
| Your own server | 23 | — | Yes | Yes | ||
| Hyperscaler cloud | 187 | — | Yes | No | ||
| PaaS | 150 | — | Yes | No | Compare → | |
| Frontend cloud | 128 | — | Yes | No | ||
| Hyperscaler cloud | 74 | — | Yes | No | ||
| PaaS | 53 | — | No | No | ||
| Your own server | 32 | — | No | No | ||
| Your own cloud account | 12 | — | No | No | ||
| Your own cloud account | 8 | — | No | No | ||
| Your own cloud account | 7 | — | Yes | Yes | ||
| PaaS | 6 | — | No | No | ||
| Zeabur | Your own server | 3 | — | No | No | |
| Frontend cloud | 0 | — | Yes | No |
What shape is your app? A frontend or serverless app fits a frontend cloud. Long-running servers, background workers and databases fit a PaaS or container platform. A hyperscaler cloud has every building block but leaves you to assemble them; a platform or framework that deploys into your own cloud account sits between, with platform-style deploys and the resources on your own cloud bill.
Hetzner Cloud (Your own server): A lot of CPU and RAM per euro, in European, US and Singapore regions. Trade-off: Fewer managed services than big clouds, and account verification can be strict.
Best forNext.js apps — zero-config deploys and preview URLs.
Trade-offThe Hobby plan is non-commercial; costs grow with usage.
Used by 2,014 makers' products for this
Best forThe widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure.
Trade-offYou wire up networking, permissions and deploys yourself; billing is per service and hard to predict.
Used by 460 makers' products for this · Hetzner Cloud vs Amazon Web Services →
Best forCheap global hosting with Workers, plus database (D1) and storage (R2) on the same platform.
Trade-offThe Workers runtime isn't full Node.js; some libraries need adapting.
Used by 385 makers' products for this
Best forStatic sites and JAMstack apps on any framework.
Trade-offServer-side features run as functions with time limits; long-running work needs another host.
Used by 265 makers' products for this
Best forA Heroku-style platform for web services, cron jobs and Postgres.
Trade-offFree instances sleep when idle and wake slowly; paid instances are billed whether busy or not.
Used by 137 makers' products for this
Best forServers, workers and databases deployed together, with almost no configuration.
Trade-offUsage-based billing needs watching; fewer regions and compliance options than a hyperscaler.
Used by 124 makers' products for this · Hetzner Cloud vs Railway →
Best forDocker apps that should run close to users in many regions.
Trade-offMore operations work than a PaaS.
Used by 74 makers' products for this · Hetzner Cloud vs Fly.io →
Best forA Heroku- or Vercel-style dashboard on your own server, with many one-click services.
Trade-offThe dashboard itself runs on your server and needs updates.
Used by 23 makers' products for this
Best forContainers on Cloud Run that scale to zero, next to BigQuery, Firebase and Google's AI services.
Trade-offMore setup than a PaaS, and IAM and billing take learning.
Used by 187 makers' products for this
Best forApp Platform deploys from git next to DigitalOcean's managed databases, storage and droplets.
Trade-offFewer built-in extras than Vercel or Railway, and instances are billed per size, not per request.
Used by 150 makers' products for this · Hetzner Cloud vs DigitalOcean →
Best forFree hosting for static sites, docs and landing pages published straight from a repo.
Trade-offStatic files only — no server code, no preview URLs for pull requests, and soft bandwidth limits.
Used by 128 makers' products for this
Best forApp Service, Functions and Container Apps alongside Azure OpenAI and Microsoft's identity and enterprise tooling.
Trade-offA large, enterprise-shaped console with more configuration than a PaaS.
Used by 74 makers' products for this
Best forA long-established git-push platform with managed Postgres, Redis and a large add-on marketplace.
Trade-offNo free tier, and since March 2026 Heroku runs as a sustaining-engineering platform focused on stability rather than new features.
Used by 53 makers' products for this
Best forA low-cost KVM VPS with root access and one-click templates such as Docker and Coolify, from a large consumer hosting company.
Trade-offLow prices are introductory and paid upfront, with higher renewals; the server's location is fixed after setup, and snapshots last only a day.
Used by 32 makers' products for this
Best forA Heroku-style dashboard that runs your apps on Kubernetes in your own AWS, Google Cloud or Azure account.
Trade-offTwo bills (Porter plus the cloud), and a managed Kubernetes cluster costs more at the low end than a PaaS.
Used by 12 makers' products for this
Best forGit-connected hosting for static and SSR frontends inside your AWS account, with an optional AWS-backed backend.
Trade-offFramework support and build settings lag the frontend clouds, and debugging leads into CloudWatch and IAM.
Used by 8 makers' products for this
Best forDefining an app and its AWS or Cloudflare infrastructure — functions, containers, queues, databases — in TypeScript, and deploying it with one command.
Trade-offYou still own an AWS account's billing, limits and permissions; mistakes in config create real resources.
Used by 7 makers' products for this
Best forManaged servers for WordPress, Laravel and other PHP apps on DigitalOcean, AWS or Google Cloud, with patches, backups and SSL handled.
Trade-offNo root access and a stack built around PHP; Node.js apps need the separate Velocity plan, and you pay per server size whether busy or not.
Used by 6 makers' products for this
Best forA PaaS-style dashboard that deploys apps, databases and one-click templates onto servers bought through Zeabur or connected from your own cloud.
Trade-offTwo bills, the plan plus the servers, and its earlier shared, usage-billed cluster stopped taking new services in April 2026, so older guides describe a different setup.
Used by 3 makers' products for this
Best forStatic sites and SSR apps (App Hosting) deployed next to Firebase Auth, Firestore and Cloud Functions.
Trade-offServer-side parts run on Google Cloud under the hood, with Google Cloud billing and limits.
No maker product tracked for this yet
It depends on what you need it for; we don't rank them. Among products launched in 2026, the most picked for hosting instead is Vercel (57%), and the most projects leaving Hetzner Cloud on GitHub moved to Amazon Web Services (8 pull requests). You built a Next.js or other frontend-heavy app and want preview URLs on every pull request: Vercel and Netlify. Your app is a static site or docs and should cost nothing to host: Cloudflare. You have a long-running server, a background worker and a database to deploy together: Railway and Render.
Yes. For hosting, Vercel, Amazon Web Services, Cloudflare, Netlify, Render, Coolify and 6 more have a free tier a small product can start on.
Yes. For hosting: Coolify and SST.
For a team of 5 with 10,000 users, the cheapest is Cloudflare at $12 a month on Workers Paid, against $13 for Hetzner Cloud on CPX12. From each vendor's pricing page.
On GitHub, 8 public pull requests since Oct 2024 moved projects off Hetzner Cloud: Amazon Web Services (8); 19 moved to Hetzner Cloud. Each is a real code change in a public repo, by developers in general.