Run multiple frameworks in one project with Vercel Services

You can now deploy multiple frontends and backends together within a single Vercel project.

Vercel Services is now available, allowing you to deploy full stack apps with multiple frameworks on a shared domain, where services talk to each other privately and deployments build, preview, and roll back together.

Services are defined in vercel.json:

1
{
2
  "services": {
3
    "my_frontend": {
4
      "root": "frontend/",
5
      "framework": "nextjs"
6
    },
7
    "my_backend": {
8
      "root": "backend/",
9
      "entrypoint": "main:app"
10
    }
11
  },
12
  // my_backend has no public route
13
  // it is only reachable from my_frontend internally
14
  "rewrites": [
15
    { 
16
      "source": "/(.*)", 
17
      "destination": { "service": "my_frontend" }
18
    }
19
  ]
20
}

From there, your services show up across the dashboard and CLI:

• The Deployments panel visualizes the services graph

• The Logs UI filters by individual service

• vercel dev runs every service locally for a production-like environment

Link to headingService bindings

Services talk to each other internally with the new bindings key, without routing through the public internet:

1
{
2
  "services": {
3
    "my_frontend": {
4
      "root": "frontend/",
5
      "framework": "nextjs",
6
      "bindings": [
7
        {
8
          "type": "service",
9
          "service": "my_backend",
10
          "format": "url",
11
          "env": "BACKEND_INTERNAL_URL"
12
        }
13
      ]
14
    },
15
    "my_backend": { ... }
16
  },
17
  "rewrites": [ ... ]
18
}

The frontend reaches the backend privately through the URL in BACKEND_INTERNAL_URL:

1
export async function GET() {
2
  const url = new URL("/users", process.env.BACKEND_INTERNAL_URL);
3
  const res = await fetch(url);
4
  const users = await res.json();
5
  return Response.json(users);
6
}

Link to headingFramework-defined infrastructure

Most frameworks run with zero configuration. Framework-defined infrastructure means each service's framework is auto-detected and auto-provisioned, from FastAPI and Flask to Express and Hono, with first-class support for Go and Rust. Services run on Fluid compute with Active CPU pricing, so you only pay for the time your code is actually running.

Read the documentation to get started.