VercelVercel
Menu

Services

Last updated March 14, 2026

Services are available in Private Beta to all plans with access granted by request.

Services let you deploy multiple backends and frontends within a single Vercel project. For example, a Next.js frontend and a FastAPI backend in the same repository deploy together with shared routing, environment variables, and a unique domain, replacing the need to split monorepos into separate Vercel projects.

A service is an independently built unit within your project that is 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.

A project can contain multiple services across different frameworks or runtimes, such as:

  • A Next.js frontend at /
  • A Python FastAPI backend, e.g. at /backend
  • A Go server, e.g. at /svc/go

All services share the same deployment URL.

Services are valuable when you have:

  • A polyglot monorepo: A JavaScript frontend and a Python backend in the same repository that you want to deploy as one project.
  • Multiple backends: Several API services, each with its own dependencies and build step.

If your project uses a single framework (for example, a Next.js with API routes), you don't need services. If your monorepo contains separate applications that you would prefer to mount under separate domains, consider deploying them as separate projects in a monorepo instead.

Define services in vercel.json using the experimentalServices key:

vercel.json
{
  "experimentalServices": {
    "web": {
      "entrypoint": "apps/web",
      "routePrefix": "/"
    },
    "api": {
      "entrypoint": "backend/main.py",
      "routePrefix": "/server"
    }
  }
}

To deploy a project that uses multiple services, your project framework setting must be set to Services and experimentalServices must be present in vercel.json.

FieldTypeDescription
entrypointstringPath to the service entrypoint file or directory.
routePrefixstringURL path prefix for routing. Required for web services.
frameworkstringOptional: framework slug (for example, "nextjs", "fastapi", "express"). Pins the framework configuration. If not set, framework is automatically detected on every build.
memoryintegerOptional: max available RAM in MB (128 to 10,240).
maxDurationintegerOptional: execution timeout in seconds (1 to 900).
includeFilesstring | string[]Optional: glob patterns for files to include in the deployment.
excludeFilesstring | string[]Optional: glob patterns for files to exclude from the deployment.

Run all services together locally, without authenticating with the Vercel Cloud, by adding the -L flag (short for --local):

Terminal
vercel dev -L
  • Routing and communication: How request routing, route prefixes, environment variables, and cross-service communication work.

Was this helpful?

supported.