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 · Cloudflare vs Vercel →
Of the 860 products launched in 2026 that we know the hosting of, 20% use Cloudflare, against 11% of those launched in 2023 or earlier. The most picked now is Vercel (57%, up from 54%). On GitHub, 136+ public pull requests since Oct 2024 moved projects off Cloudflare: Vercel (83), Render (16), Netlify (15) and Amazon Web Services (10+); 448 moved to Cloudflare.
2 of the 20 are open source or self-hostable (Coolify and SST) and 11 have a free tier. For a team of 5 with 10,000 users, none costs less than Cloudflare ($12 a month on Workers Paid); the cheapest is Hetzner Cloud at $13. Cloudflare also answers image & video hosting, LLM gateway & routing and MCP server for your product: those alternatives are below too.
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% | |
| 9% | 6% | 6% | 4% |
Public pull requests on GitHub since Oct 2024 whose title says "Cloudflare to …" or "… to Cloudflare": real code changes, by developers in general, not only makers. Each count opens the search that finds them.
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 | |
|---|---|---|---|---|---|---|
| Edge platform | 385 | $12/mo · Workers Paid | Yes | No | ||
| Frontend cloud | 2,014 | $120/mo · Pro + Flat Rate CDN 10M | Yes | No | Compare → | |
| Hyperscaler cloud | 460 | $17/mo · Pay as you go (Lambda + EC2 t4g.small) | Yes | No | Compare → | |
| Frontend cloud | 265 | $30/mo · Pro 3,000 credits | Yes | No | Compare → | |
| PaaS | 137 | $61/mo · Pro | Yes | No | ||
| PaaS | 124 | $45/mo · Pro | No | No | Compare → | |
| Your own server | 110 | $13/mo · CPX12 | No | No | ||
| Container platform | 74 | $15/mo · Pay As You Go | No | No | ||
| Your own server | 23 | — | Yes | Yes | ||
| Hyperscaler cloud | 187 | — | Yes | No | ||
| PaaS | 150 | — | Yes | No | ||
| 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 | Compare → |
How many makers' products we track use each for image & video hosting, and what each costs at 10,000 users.
| Option | Kind | Makers' products | At 10,000 users | Free tier | Open source | |
|---|---|---|---|---|---|---|
| CDN bundle | 0 | $2.50/mo · Paid (images in your own bucket) | Yes | No | ||
| Image pipeline | 59 | $99/mo · Plus | — | No | ||
| Image pipeline | 25 | $14/mo · Lite | — | No | ||
| Video streaming | 24 | — | — | No | ||
| CDN bundle | 0 | $10/mo · Optimizer + Standard CDN + Storage | — | No | ||
| Process it yourself | 0 | — | — | Yes | ||
| Process it yourself | 0 | — | — | Yes | ||
| imgix | Image pipeline | 6 | — | No | No | |
| Image pipeline | 0 | — | Yes | No | Compare → |
How many makers' products we track use each for LLM gateway & routing.
| Option | Kind | Makers' products | Free tier | Open source | |
|---|---|---|---|---|---|
| Managed gateway + controls | 0 | Yes | No | ||
| Managed gateway + controls | 1 | Yes | Yes | ||
| Hosted model marketplace | 0 | Yes | No | ||
| Self-hosted proxy | 0 | Yes | Yes | ||
| Managed gateway + controls | 0 | Yes | Yes | ||
| Hosted model marketplace | 0 | Yes | No | ||
| Self-hosted proxy | 2 | — | Yes | ||
| Hosted model marketplace | 1 | — | No | ||
| Managed gateway + controls | 0 | Yes | No | ||
| Hosted model marketplace | 0 | No | No |
How many makers' products we track use each for MCP server for your product.
| Option | Kind | Makers' products | Free tier | Open source | |
|---|---|---|---|---|---|
| Edge platform | 0 | Yes | No | ||
| Official SDK | 0 | — | Yes | ||
| Framework | 0 | — | Yes | ||
| Framework | 0 | — | Yes | ||
| Framework | 0 | — | Yes | ||
| Framework | 0 | — | No | ||
| Edge platform | 0 | — | 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.
Cloudflare (Edge platform): Cheap global hosting with Workers, plus database (D1) and storage (R2) on the same platform. Trade-off: The Workers runtime isn't full Node.js; some libraries need adapting.
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 · Cloudflare vs Vercel →
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 · Cloudflare vs Amazon Web Services →
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 · Cloudflare vs Netlify →
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 · Cloudflare vs Railway →
Best forA lot of CPU and RAM per euro, in European, US and Singapore regions.
Trade-offFewer managed services than big clouds, and account verification can be strict.
Used by 110 makers' products for this
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
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
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 · Cloudflare vs Firebase →
Image pipeline, video streaming, or a raw CDN bundle. Image services resize, crop and convert through the URL. Video needs encoding and adaptive streaming, which is a separate job. A CDN bundle gives storage, delivery and basic optimization at low per-GB cost, with less done for you. Or process images yourself, with a library in your code or an image server you host.
Cloudflare (CDN bundle): Image resizing and video streaming from the same account that already runs your DNS and CDN, through Cloudflare Images and Stream. Trade-off: Fewer transformation options than a dedicated image service; Images and Stream are billed separately by images stored, transformations and minutes.
Best forApps with lots of user-uploaded images and video that need crops, overlays and format conversion through URLs.
Trade-offCredit-based pricing is hard to predict and climbs with transformations and bandwidth.
Used by 59 makers' products for this
Best forAdding resizing and optimization in front of storage you already have, such as an S3 bucket.
Trade-offFewer advanced media features than Cloudinary.
Used by 25 makers' products for this
Best forApps where video is the product — uploads encoded and streamed adaptively with a player and playback analytics.
Trade-offUsage-based by encoding, storage and delivery minutes; it's for video only, not images.
Used by 24 makers' products for this
Best forLow per-GB cost for storage, CDN delivery, image optimization and video streaming from one vendor.
Trade-offNo lasting free tier after the trial; tools are simpler than dedicated media platforms.
No maker product tracked for this yet
Best forResizing, cropping and converting images to WebP or AVIF inside your own Node code, at upload or build time.
Trade-offRuns on your server's CPU and memory, which is tight on serverless; storage and CDN delivery are still yours to set up.
No maker product tracked for this yet
Best forCloudinary-style resizing through URLs on a server you run, placed in front of your bucket and behind a CDN.
Trade-offYou host and scale it and add the CDN yourself; some features, such as video thumbnails and object-aware cropping, are in the paid Pro edition.
No maker product tracked for this yet
Best forResizing and optimizing images straight from your own bucket through URL parameters.
Trade-offNo free plan, and every resize, gigabyte delivered and cached original draws on one credit bundle.
Used by 6 makers' products for this
Best forImage optimization built into a Next.js app hosted on Vercel, with nothing else to set up.
Trade-offBilled per transformation and cache write on top of hosting, and only for apps deployed on Vercel.
No maker product tracked for this yet · Cloudflare vs Vercel →
Hosted gateway or self-hosted proxy. A hosted gateway gives you one key and one bill in minutes, but every request passes through someone else's service. A self-hosted proxy keeps your provider keys and traffic on your own servers, and you run and update it.
Cloudflare (Managed gateway + controls): Logging, caching, rate limits, spend limits and fallbacks in front of OpenAI, Anthropic, Workers AI and 20+ other providers, free on any Cloudflare account. Trade-off: Logs count against Workers Logs pricing for new accounts, buying model credits through Unified Billing adds a 5% fee, and dynamic routing, guardrails and BYOK are still in beta.
Best forAdding a gateway when your main goal is logging and debugging every request, with caching and rate limits on the side.
Trade-offIts focus is observability; routing features are thinner than a dedicated gateway's.
Used by 1 maker's product for this
Best forTrying many models from many providers with one API key and one bill, without opening an account at each.
Trade-offA fee on top of provider prices, and your traffic and data pass through a third party.
No maker product tracked for this yet
Best forRunning your own OpenAI-compatible proxy in front of your own provider keys, with retries, routing and per-key budgets.
Trade-offYou deploy, monitor and upgrade it yourself; SSO and audit logs are in the paid enterprise tier.
No maker product tracked for this yet
Best forA gateway that also handles guardrails, prompt management and request logs in one dashboard.
Trade-offThe free tier caps logged requests; the full control layer is a paid hosted product.
No maker product tracked for this yet
Best forOne key and one bill for hundreds of models at provider list prices, with fallbacks and budgets, built into the AI SDK.
Trade-offTied to a Vercel team and prepaid credits, and bringing your own provider keys needs the paid tier.
No maker product tracked for this yet
Best forRouting, auth, token budgets and usage analytics for LLM, MCP and agent-to-agent traffic, run as AI plugins on Kong Gateway.
Trade-offBuilt for platform teams; the quickstart needs a Konnect account and token, and it is a heavy setup if all you want is one key for several models.
Used by 2 makers' products for this
Best forOne API in front of many models that routed each prompt to the best one for quality, cost and speed.
Trade-offPivoted away from routing (now continual-learning models for agent teams); there is no gateway or pricing page.
Used by 1 maker's product for this
Best forOne OpenAI-compatible endpoint to 1,000+ models with fallbacks, caching, spend limits and every request logged in the same place you run evals.
Trade-offRequests pass through its cloud; the free plan caps proxy throughput at 412 requests a minute, and the self-hostable part is only the new open-source gateway.
No maker product tracked for this yet
Best forOne prepaid key for 200+ models behind OpenAI- and Anthropic-compatible endpoints, usable from Claude Code, Cursor and the Vercel AI SDK.
Trade-offA side offering of a research lab whose homepage no longer mentions it; no free tier, and keys fail until you buy credits.
No maker product tracked for this yet
Official SDK or a framework on top of it, and where the server runs. The official SDKs give you the protocol with nothing hidden, and you wire up transport, auth and deployment yourself. Frameworks add decorators or file-based tools, auth helpers and one-command deploys. A remote server runs next to your app — as a route in your web framework or on an edge platform — so users connect with a URL and sign in with OAuth instead of installing anything.
Cloudflare (Edge platform): Remote MCP servers on Workers, with the Agents SDK handling per-session state and a provider library handling OAuth. Trade-off: Workers' runtime limits and Cloudflare-specific APIs, so the server is harder to move elsewhere.
Best forBuilding MCP servers and clients against the protocol directly, with official SDKs for TypeScript, Python, Go, Java, C#, Rust and more.
Trade-offLow-level — auth, session handling and deployment are yours to build.
No maker product tracked for this yet
Best forPython MCP servers with tools defined by decorators, plus built-in auth providers, server composition and a testing client.
Trade-offPython only; its hosted option (Prefect Horizon) is aimed at teams and enterprises.
No maker product tracked for this yet
Best forServing an MCP server from a route in a Next.js or other TypeScript app, on serverless functions.
Trade-offA thin adapter over the official SDK, so tool design, auth and data access are still yours; the older SSE transport needs Redis.
No maker product tracked for this yet
Best forTypeScript MCP servers with file-based tool routing, hot reload and ready deploy targets.
Trade-offA young project with a smaller community than the official SDK.
No maker product tracked for this yet
Best forGenerating typed SDKs, docs and an MCP server straight from your OpenAPI spec and keeping them in sync.
Trade-offJoined Anthropic on 2026-05-18; all hosted products are winding down and new signups and projects stopped.
No maker product tracked for this yet
Best forCompanies governing which MCP servers and models their employees' AI clients may use, with role-based bundles and monitoring.
Trade-offRenamed from MintMCP on 2026-10-12; quote-based per-user pricing aimed at company-wide rollouts.
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 Cloudflare on GitHub moved to Vercel (83 pull requests). You built a Next.js or other frontend-heavy app and want preview URLs on every pull request: Vercel and Netlify. You have a long-running server, a background worker and a database to deploy together: Railway and Render. Your users are spread across continents and the app runs in Docker: Fly.io.
Yes. For hosting, Vercel, Amazon Web Services, Netlify, Render, Coolify, Google Cloud Platform and 5 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, none costs less than Cloudflare ($12 a month on Workers Paid); the cheapest is Hetzner Cloud at $13. From each vendor's pricing page.
On GitHub, 136+ public pull requests since Oct 2024 moved projects off Cloudflare: Vercel (83), Render (16), Netlify (15) and Amazon Web Services (10+); 448 moved to Cloudflare. Each is a real code change in a public repo, by developers in general.