# Vercel Services: Run full stack on Vercel

DevFeed: [Vercel Services: Run full stack on Vercel](<https://devfeed.tech/articles/vercel-services-run-full-stack-on-vercel-787.md>)

Original publisher: [Read original article](<https://vercel.com/blog/vercel-services-run-full-stack-on-vercel>)

Author: Joe Haddad

Published: 2026-06-30T04:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [FastAPI](<https://devfeed.tech/topics/fastapi.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [rest](<https://devfeed.tech/tags/rest.md>), [routing](<https://devfeed.tech/tags/routing.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel Services is introduced in public beta as a way to run multiple frameworks in one Vercel Project. It supports coordinated deployments and previews, internal service communication, shared routing, service bindings, centralized logs, and local multi-service development for full-stack applications.

## Source excerpt

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. Compose applications with Vercel Services Declare your services under the services key in vercel.json keeping the routing configuration explicit: 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: The Deployments panel shows a visualization of services graph The Logs UI allows filtering by individual service The vercel dev CLI automatically runs all services giving you a production-like environment locally Service bindings Services can talk to other services internally, without routing through the public Internet. Here's an example how the new bindings configuration key enables that: Now the JavaScript frontend code can talk to the Python service internally via the URL stored in the BACKEND_INTERNAL_URL environment variable: 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. Framework-def