From the source
To a user, an app with a Next.js frontend and a FastAPI backend feels like one product, and the same should be true for the engineers who build it.
Instead, the two pieces are often deployed across different clouds with different development and deployment workflows.
Today we're introducing Vercel Services in public beta, which lets you run multiple frameworks in one Vercel Project.
This unlocks: Atomic deployments: Your frontend, backend, and other services stay in sync and deploy or roll back together Shared preview deployments: See how any change affects all your services Internal service communication: Services can talk to each other without routing through the public Internet Vercel handles the rest: routing, builds, deployments, and auto-scaling in production.
The developer experience you already know from Vercel now covers your entire application.
Copy link to heading Compose applications with Vercel Services Declare your services under the services key in vercel.json keeping the routing configuration explicit: …
