# Vercel Services: Run full stack on Vercel By Steven Van · 2026-06-30 The public beta runs multiple frameworks in one Vercel Project, with routing set via a services key in vercel.json. Vercel has introduced Services in public beta, letting a Next.js frontend, a FastAPI backend, or any other mix of frameworks run inside a single [Vercel]() Project instead of being deployed across separate clouds. Services are declared under a **services** key in vercel.json, and top-level rewrites route public requests to a named service rather than a URL, for example sending */api/(.\*)* to a backend service and everything else to a frontend service. Once a request is routed in, [that service handles its own routes](), and Vercel does not fall back to other rewrites if nothing matches. - Frontend, backend, and other services deploy and roll back together as one atomic unit - Preview deployments show how a change affects all services at once - Services can call each other internally without routing through the public internet - The Deployments panel visualizes the services graph, the Logs UI can filter by service, and the vercel dev CLI runs all services locally [![]()]() ![Vercel]() Vercel The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config. [View Vercel →]() Sources [Original source]() [Read Vercel Services: Run full stack on Vercel on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-vercel-services-run-full-stack-on-vercel