Nitro makes Nuxt portable — but you still have to choose
Nuxt 3+ is built on the Nitro server engine, which can target dozens of deployment platforms via presets: Node server, static, edge runtimes, and serverless. That portability is a gift, but it also means the hosting decision hinges on your rendering strategy:
- SSR (Node server) — render on each request; needs a long-running Node process.
- Static (
nuxi generate) — prerender to static files for a CDN. - Hybrid / ISR — mix per-route, using route rules.
- Edge — run on an edge runtime via a Nitro preset.
What matters for Nuxt
- A Node runtime for SSR (or an edge target if you go that route).
- Nitro preset compatibility with the host.
- Static output support for
generate. - Managed database access since Nuxt server routes (
/server/api) often hit a DB. - WebSocket support if you use Nitro's experimental WebSocket handlers.
The options
| Platform | SSR (Node) | Static | Edge preset | Managed DB |
|---|---|---|---|---|
| Vercel / Netlify | Yes | Yes | Yes | No |
| Cloudflare Pages/Workers | Workers | Yes | Yes | No |
| NuxtHub (on Cloudflare) | Yes | Yes | Yes | D1/KV |
| Fly.io / Railway / Render | Yes | Yes | No | Some |
| PandaStack | Yes (container) | Yes (static) | No | Yes |
Vercel, Netlify, NuxtHub
Vercel and Netlify have first-class Nuxt presets and are the smoothest path for SSR and hybrid Nuxt. NuxtHub (built on Cloudflare) is compelling if you want Nuxt plus an integrated edge database (D1) and KV in the Nuxt ecosystem. These are excellent, especially for edge-leaning deployments.
Where PandaStack fits
PandaStack hosts Nuxt two ways. For static Nuxt (nuxi generate), deploy it as a static site — auto-detected, built in pandastack.ai microVMs, served via Kong ingress with custom domains and automatic SSL. For SSR Nuxt, use the Node Nitro preset and deploy the .output server as a container:
# SSR build with the Node preset
NITRO_PRESET=node-server npm run build
# Produces .output/server/index.mjs — run it as a container
node .output/server/index.mjs # listens on $PORTFROM node:22-slim
WORKDIR /app
COPY .output ./.output
ENV PORT=3000
CMD ["node", ".output/server/index.mjs"]The consolidation win is real for Nuxt: your /server/api routes can talk to a managed Postgres/MySQL/MongoDB with DATABASE_URL injected automatically — no separate database provider, no manual connection wiring. You also get live logs, metrics, analytics, rollbacks, and deploy history.
Honest comparison: Vercel, Netlify, and NuxtHub have purpose-built Nuxt presets and edge networks that PandaStack doesn't match for pure edge/serverless Nuxt. If your Nuxt app is edge-shaped or you want NuxtHub's integrated D1/KV, those are the better tools. PandaStack is the strongest fit when you run SSR Nuxt as a Node server with a managed SQL database, and want the database, server, and any companion services on one platform. For production SSR, run a warm instance to avoid free-tier cold starts.
Tip: choose the preset deliberately
Nitro defaults to a Node preset for generic Node hosts, which is exactly what you want on PandaStack. Don't accidentally ship an edge preset to a Node container or vice versa — set NITRO_PRESET explicitly in your build.
Decision guide
- Edge/serverless Nuxt → Vercel / Netlify / NuxtHub.
- SSR Nuxt as a Node server + managed SQL DB → PandaStack (warm instance for prod).
- Static Nuxt → any CDN host, including PandaStack static sites.
References
- Nuxt deployment docs: https://nuxt.com/docs/getting-started/deployment
- Nitro deploy presets: https://nitro.build/deploy
- NuxtHub: https://hub.nuxt.com/docs
- Nuxt server routes: https://nuxt.com/docs/guide/directory-structure/server
- Vercel Nuxt guide: https://vercel.com/docs/frameworks/nuxt
---
Running SSR Nuxt with server routes that hit a database? PandaStack runs the Node server and injects DATABASE_URL from a managed DB automatically. Start free at https://dashboard.pandastack.io