Vercel Bring Your Own Cloud on AWS reaches general availability
Enterprise customers can now run Vercel Functions inside their own AWS account instead of Vercel's, while Vercel still handles deployment and routing.
Vercel made Bring Your Own Cloud (BYOC) for AWS generally available on 15 October. It lets Enterprise customers run their Vercel Functions inside their own AWS account rather than Vercel’s.
Node.js and Python functions execute as Lambda-backed code in the customer’s AWS account, under their own IAM permissions and network policies, and can connect privately to services in their VPC. Vercel still manages deployments, environments, routing and static assets, and TLS still terminates at Vercel’s CDN. Containers and Services aren’t covered, it’s AWS-only, and it doesn’t meet FedRAMP. It’s Enterprise-plan only; Vercel names Meta Superintelligence Labs as an existing user.
Why it matters: “all our code has to run inside our own cloud account” is a common blocker when a regulated or security-conscious team considers a managed platform like Vercel. BYOC lets function execution stay inside the customer’s existing AWS boundary and compliance posture while keeping Vercel’s deployment and routing workflow on top.
The caveat: it only covers two runtimes so far and stops short of FedRAMP, so it won’t satisfy every compliance checklist by itself.