comparar · Deployment
Both work with Nuxt. In a kit you pick one, and your agent gets the rule to use only that one.
| Docker | Vercel | |
|---|---|---|
| What it is | A standalone Nitro Node server in a container. | Deployments with a preview for every PR. |
| Frameworks | Nuxt | Next.js, Nuxt |
| Paquetes | — | — |
| Skill oficial | — | vercel-labs/agent-skills@deploy-to-vercel, vercel-labs/agent-skills@vercel-cli-with-tokens |
| How your agent uses it | Build with docker build -t app . and run with docker run -p 3000:3000 --env-file .env app. The production entry point is .output/server/index.mjs, not npm start. Keep secret files out of the build context. | Deploy by connecting the repository at vercel.com (every push to main goes to production and every PR gets its own URL) or with `npx vercel`. Set the variables from `.env.example` in the Vercel project. Nuxt is detected automatically by Vercel/Nitro; do not use a Next.js output preset. |
| Kits that offer it | landing-nuxt, saas-nuxt, web-nuxt | docs-fumadocs, landing-next, landing-nuxt, saas-ai-next, saas-next-better-auth, saas-next-supabase, saas-nuxt, saas-t3, web-next, web-nuxt |
| Chosen in | 0 installs | 0 installs |