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 and run your application.

Those services run on a platform that includes everything any backend could need, whether you're building APIs, agents, or background workers: compute, data, networking, background work, and secure connections to external services.

Agents can read files, run commands, and write code. But that capability needs to be secure. gives each agent its own Linux computer: a filesystem, a shell, , and its own kernel, completely isolated from your deployments. Agents can execute code, grep files, and spin up Redis or Postgres as dependencies. Nothing inside the sandbox can touch your production environment.Vercel SandboxDocker support

With , state carries between sessions, and on Pro, sandboxes can run for up to 24 hours.automatic persistence

Vercel Functions handle persistent WebSocket connections in every Vercel runtime, whether your backend is written in Node.js, Python, or Go. They work with standard WebSocket libraries like , and because connections run on Fluid compute with Active CPU pricing, you only pay for the time spent processing messages, not the time a connection sits idle.Socket.IO

Agents and backends need to reach services outside your project (Slack, GitHub, managed databases), which usually means storing a long-lived secret in your environment. replaces that with a short-lived credential your app requests at runtime, scoped to the task in front of it. There is no long-lived secret left to leak.Vercel Connect

You can provision a database from the in a few clicks, with credentials injected for you, from providers like Neon, Supabase, and from AWS with Aurora PostgreSQL, Aurora DSQL, and DynamoDB. adds full-text and vector search, and handles object storage. You can any of it without leaving Vercel, and both Blob and the AWS integrations authenticate with short-lived OIDC tokens rather than stored secrets.Vercel MarketplaceAmazon OpenSearch ServerlessVercel Blobquery and manage

Vercel processes background jobs off the request path. Vercel handles durable multi-step processes that survive crashes and redeploys. And Vercel runs work on a schedule. This is the part of a backend that outlives a request, and it runs on the same platform as everything else, so the long-running side of your backend needs no separate infrastructure.QueuesWorkflowCron

When a backend needs to reach a private database or an internal network instead of a public service, , , and open that path.Secure Computestatic IPsVPC peering

Functions run for on Pro and Enterprise, and Python backends deploy with up to 500mb of dependencies.up to 30 minutes

Underneath all of it, is , and Active CPU pricing bills for the time your code is actually running rather than the time it waits, the right shape for idle-heavy backend and AI work.Fluid computethe default for new projects

Vercel Services brings your frontend, backend, and supporting services into one project. They build together, preview together, deploy together, and communicate internally by default.

Combined with Vercel's built-in primitives for compute, data, queues, workflows, cron, secure networking, and sandboxed agent environments, you can run the full stack without stitching together separate platforms.

To start composing services, read the and the . If you are new to running a backend on Vercel, the post is the place to begin.Vercel Services documentationrouting and communication guidezero-config backends

Read more

• Your frontend, backend, and other services stay in sync and deploy or roll back togetherAtomic deployments:

• See how any change affects all your servicesShared preview deployments:

• Services can talk to each other without routing through the public InternetInternal service communication:

• The Deployments panel shows a visualization of services graph

• The Logs UI allows filtering by individual service

• The CLI automatically runs all services giving you a production-like environment locallyvercel dev

Compose applications with Vercel Services

The full stack platform

A single platform for everything you ship

Service bindings

Framework-defined infrastructure

Isolated compute for agent services

Real-time backends with WebSocket support

Reach external services with Vercel Connect

Databases and storage for your services

Run durable workflows and background jobs

Connect privately and run on the right compute