Hosting · for NestJS

Hosting for NestJS

Among 10 makers' products we track that are built with NestJS, 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.

What makers on NestJS chose

Counts are live products with a source, not market share; a product using two options counts in both.

VercelFrontend cloud
llms.txtMCPCLIIn v0

Best forNext.js apps — zero-config deploys and preview URLs.

Trade-offThe Hobby plan is non-commercial; costs grow with usage.

5 of the 10 NestJS products here · free tier

Hetzner CloudYour own server

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.

2 of the 10 NestJS products here

NetlifyFrontend cloud
llms.txtIn Bolt

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.

1 of the 10 NestJS products here · free tier

CloudflareEdge platform
llms.txtMCP

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.

1 of the 10 NestJS products here · free tier

llms.txtMCP

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.

1 of the 10 NestJS products here

Amazon Web ServicesHyperscaler cloud

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.

1 of the 10 NestJS products here · free tier

llms.txt

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.

1 of the 10 NestJS products here · free tier

Also real options for hosting, not seen among these NestJS products yet: Render, Fly.io, Coolify.