Hosting · for Next.js
Hosting for Next.js
Among 366 makers' products we track that are built with Next.js, here's what they chose for hosting — each counted from a live-product source.
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.
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.
122 of the 366 Next.js products here · free tier
llms.txtMCPBest 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.
92 of the 366 Next.js products here · free tier
llms.txtIn BoltBest forStatic sites and JAMstack apps on any framework.
Trade-offServer-side features run as functions with time limits; long-running work needs another host.
50 of the 366 Next.js products here · free tier
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.
40 of the 366 Next.js products here · free tier
llms.txtMCPBest forServers, workers and databases deployed together, with almost no configuration.
Trade-offUsage-based billing needs watching; fewer regions and compliance options than a hyperscaler.
36 of the 366 Next.js products here
llms.txtBest 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.
34 of the 366 Next.js products here · free tier
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.
25 of the 366 Next.js products here
llms.txtBest 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.
23 of the 366 Next.js products here · free tier
llms.txtBest forDocker apps that should run close to users in many regions.
Trade-offMore operations work than a PaaS.
15 of the 366 Next.js products here
llms.txtBest 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.
11 of the 366 Next.js products here · free tier · open source
MCPBest 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.
9 of the 366 Next.js products here · free tier
llms.txtCLIBest 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.
7 of the 366 Next.js products here
llms.txtBest 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.
3 of the 366 Next.js products here
llms.txtCLIBest 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.
2 of the 366 Next.js products here · free tier
CLIBest 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.
1 of the 366 Next.js products here
SSTYour own cloud account llms.txtCLIBest 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.
1 of the 366 Next.js products here · free tier · open source