Run multiple frameworks in one project with Vercel Services
By Steven Van ·
The beta feature works on all plans, letting services call each other privately through vercel.json bindings instead of the public internet.
Vercel Services is now available in beta on all plans, letting a project deploy multiple frontends and backends together, for example a Next.js frontend and a FastAPI backend, on one shared domain instead of splitting them into separate projects.
Services are defined under a services key in vercel.json, with rewrites routing public traffic to each one. A new bindings key lets one service call another directly through an internal URL, without the request going over the public internet.
- The Deployments panel visualizes the services graph, and the Logs UI can filter by individual service.
- vercel dev runs every service locally for a production-like environment.
- All services in a project build, preview, and roll back together.
- Frameworks are auto-detected and auto-provisioned, including FastAPI, Flask, Express, and Hono, with first-class support for Go and Rust.
- Services run on Fluid compute with Active CPU pricing, so billing applies only while the code is actually running.
See the announcement for details.