comparar · Deployment
Both work with Next.js. In a kit you pick one, and your agent gets the rule to use only that one.
| Docker | Vercel | |
|---|---|---|
| What it is | An image ready for any server or container platform. | Deployments with a preview for every PR. |
| Frameworks | Next.js, Node.js | Next.js |
| Paquetes | — | — |
| Skill oficial | — | vercel-labs/agent-skills@deploy-to-vercel |
| How your agent uses it | Build with `docker build -t app .` and run with `docker run -p 3000:3000 --env-file .env app`. Keep `.dockerignore` up to date so secrets and `node_modules` aren't copied. | 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. |
| Kits that offer it | api-fastify, api-hono, api-nestjs, docs-fumadocs, landing-next, saas-ai-next, saas-next-better-auth, saas-next-supabase, saas-t3, waitlist-next | docs-fumadocs, landing-next, saas-ai-next, saas-next-better-auth, saas-next-supabase, saas-t3, waitlist-next |
| Chosen in | 0 installs | 0 installs |