Where to host a Next.js app
Next.js runs anywhere Node.js runs. But the setup can feel very different.
The simplest option is a managed platform. Push to your Git repository, and the platform builds and deploys the app for you.
With a virtual server, you manage the server, reverse proxy, updates, and backups. You get more control, but also more work.
Vercel Hobby is free for personal, non-commercial projects. Netlify Free allows commercial projects within its 300-credit monthly limit.
Cloudflare Workers also has a free allowance. The prices below assume steady traffic and an external database such as Neon or Supabase.
The two Next.js hosting paths
Recommended hosts
Netlify
1,000 credits/month; extra 500-credit packs cost $5.
- Free option
- Free: 300 credits per month with a hard stop. Commercial use is allowed; enough for a small site with modest traffic and few production deploys.
- Why it fits
- Static sites and frontend apps that deploy from Git and want a generous, mature workflow.
- How deploys work
- Connect the Git repo; pushes build and deploy automatically with previews for every pull request.
- The tradeoff
- The credit system makes bills hard to predict — traffic, deploys, and compute all drain one pool.
Laravel Cloud
One always-on Flex 1GB app instance reaches a $12 monthly compute cap; the $5 usage credit offsets the $5 Starter fee.
- Free option
- New Starter subscriptions get their first month free; after that, Starter costs $5/month and includes $5 in monthly usage credit.
- Why it fits
- Laravel teams that want the framework, database, queues, scheduler, cache, and deploy workflow managed as one platform.
- How deploys work
- Connect a Git repository or run cloud ship; Laravel Cloud builds the supported runtime and deploys every push with zero downtime.
- The tradeoff
- The excellent Laravel experience comes from an opinionated runtime, so arbitrary containers and server-level access are out.
Vercel
Includes $20/month of usage credit, which covers modest traffic.
- Free option
- Hobby: free for personal, non-commercial projects — 100 GB data transfer, 1M function invocations, and 4 active CPU hours per month.
- Why it fits
- Next.js and frontend apps where you want deploys and previews to just work.
- How deploys work
- Connect the Git repo; every push builds and deploys with a preview URL per branch.
- The tradeoff
- Usage pricing past the credit can climb fast with real traffic, especially data transfer.
We rank providers by deployment ease first, then monthly cost. Commission payments don't affect the rank. If your project is different, answer four questions and get a specific recommendation.