Vercel's Bring Your Own Cloud lets enterprises run functions in their own AWS accounts

Bring Your Own Cloud is generally available

Vercel has taken Bring Your Own Cloud (BYOC) on AWS to general availability. According to the company's changelog post, the feature lets enterprise teams run Vercel Functions inside their own AWS account, keeping both the function code and its execution inside the customer's security and compliance perimeter rather than on Vercel-operated infrastructure.

The pitch targets organisations that previously could not put workloads on a managed platform at all: the part that touches code and data — actually executing functions — stays on infrastructure the customer controls, while the deployment workflow remains Vercel's.

How the split works

Responsibilities are divided between the two sides. At deployment time, functions are provisioned into the customer's AWS account, and Vercel keeps serving everything around them: deployment orchestration, environment management, request routing and static asset delivery.

Control over execution stays with the customer. Vercel says teams apply their own IAM permissions, decide network access, and manage resource lifecycles through their own policies — meaning standard AWS governance tooling covers these functions instead of a shared, vendor-managed runtime.

What it supports

Per the announcement, BYOC allows teams to:

• Run Node.js and Python Vercel Functions inside their own AWS account
• Address strict compliance, security and isolation requirements
• Reach internal backends and services over private connections inside their VPC
• Count the work toward commitments they have already made to AWS

Only Node.js and Python are named in the announcement, so workloads written in other languages appear to be out of scope for now.

Availability

BYOC ships on Enterprise plans. Vercel directs interested teams to its sales organisation or their account team, and has published documentation plus a longer guide alongside the announcement.

Why it matters

Managed deployment platforms have long hit a ceiling in regulated industries — finance, healthcare, the public sector — where rules frequently require processing to happen inside an organisation's own accounts or approved regions. BYOC is Vercel's attempt to remove that blocker: the compliance perimeter is drawn around the customer's AWS account rather than around Vercel's platform.

There is also an economic dimension. Because functions run in the customer's account, the associated compute can be set against AWS commitments the customer already holds, which changes the cost calculus compared with paying a platform for fully managed execution.

For Vercel, the feature widens the pool of enterprises it can credibly sell into. For engineering teams inside those enterprises, it removes one of the most common reasons such a platform fails security review — at the cost of an Enterprise plan and, for now, a narrow set of supported runtimes.