Run multiple frameworks in one project with Vercel Services
Vercel now supports deploying multiple frontends and backends together in a single project with auto-detected framework configuration, private internal communication via service bindings, and shared domain with coordinated deployments and rollbacks.
You can now deploy multiple frontends and backends together within a single Vercel project.
, 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.Vercel Services is now available
Services are defined in :vercel.json
From there, your services show up across the dashboard and CLI:
Services talk to each other internally with the new key, without routing through the public internet:bindings
The frontend reaches the backend privately through the URL in :BACKEND_INTERNAL_URL
Most frameworks run with zero configuration. 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 with Active CPU pricing, so you only pay for the time your code is actually running.Framework-defined infrastructureFluid compute
Read the to get started.documentation
The Deployments panel visualizes the services graph
The Logs UI filters by individual service
runs every service locally for a production-like environment
vercel dev
Service bindings
Framework-defined infrastructure
Source: original entry ↗