Vercel Services
Configure one Vercel project to host multiple services—e.g. FastAPI or Go API beside a Next.js or Vite frontend in a monorepo.
Install
npx skills add https://github.com/vercel-labs/vercel-plugin --skill vercel-servicesWhat is this skill?
- Documents Vercel Services for monorepos combining Python/Go backends with JS frontends
- Path and bash signal detection for backend/main.py, go.mod, uvicorn, vercel dev -L
- Covers FastAPI, uv/pip, and Go run/build patterns in one project
- Explicit prompt signals for multi-service, backend+frontend, and FastAPI deploy scenarios
Adoption & trust: 44 installs on skills.sh; 187 GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Azure Kubernetesmicrosoft/azure-skills
Github Actions Docsxixu-me/skills
Deploy To Vercelvercel-labs/agent-skills
Vercel Cli With Tokensvercel-labs/agent-skills
Turborepovercel/turborepo
Docker Expertsickn33/antigravity-awesome-skills
Journey fit
Primary fit
Ship/Launch is where multi-service Vercel layout and deploy wiring matter; the skill targets getting backend and frontend live together. Launch subphase covers deployment configuration and going live on Vercel, not day-two monitoring.
Common Questions / FAQ
Is Vercel Services safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Vercel Services
# Deploy multi-service projects with Vercel Services let you deploy multiple independently-built units within a single Vercel project. The typical use case is combining different runtimes (e.g. Python + JavaScript) in one deployment with shared routing and environment variables, but services work for any combination — multiple services of the same runtime, different frameworks, or a mix. This skill covers **project structure and configuration**. For the actual deployment, defer to the **deployments-cicd** skill. ## How It Works A service is an independently built unit within your project, deployed to the same domain under a unique subpath. At build time, Vercel builds each service separately. At request time, Vercel routes incoming requests to the correct service based on the URL path prefix (longest prefix wins). - Services are enabled via the `experimentalServices` field in `vercel.json` (see reference project). - `vercel dev -L` auto-detects frameworks and runs all services locally as one application, handling routing automatically. The `-L` flag (short for `--local`) runs without authenticating with Vercel Cloud. - Only `vercel.json` lives at the root. Each service manages its own dependencies independently. ## Configuration Define services in `verce