Vercel Services: Run full stack on Vercel

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 , which lets you run multiple frameworks in one Vercel Project. This unlocks:Vercel Services 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. Declare your services under the key in keeping the routing configuration explicit:servicesvercel.json Services can be mounted to a shared routing table without the need for a reverse proxy or CORS. The services configuration is recognized at multiple levels of the Vercel platform: Services can talk to other services internally, without routing through the public Internet. Here's an example how the new configuration key enables that:bindings Now the JavaScript frontend code can talk to the Python service internally via the URL stored in the environment variable:BACKEND_INTERNAL_URL Service-to-service traffic stays on the Vercel network rather than egressing to the public internet. Many independent services can become one application connected by the same wiring, rather than separate deployments that you stitch together across hosts. Most frameworks run on Vercel with zero configuration. means that each service's framework is auto-detected and auto-provisioned, from and for Python to Express and for TypeScript, with first-class support for and servers.Framework-defined infrastructureFastAPIFlaskHonoGoRust Services run on Fluid compute, autoscaling with traffic, while you pay only for active CPU time. But framework-defined optimizations go even deeper. With Django, for example, we automatically detect where static assets live and serve them from the CDN. Vercel Services gives Vercel a structured way to build...