---
type: "raw_signal"
id: "bring-your-own-cloud-on-aws-is-now-d20cd3"
slug: "bring-your-own-cloud-on-aws-is-now-d20cd3"
title: "Bring Your Own Cloud on AWS is now generally available on Vercel."
description: "## Vercel brings AWS-hosted function execution to general availability"
retrieval_nugget: "## Vercel brings AWS-hosted function execution to general availability"
observed_at: "2026-10-15"
record_date: "2026-10-15"
date_kind: "observed_at"
why_it_matters: "The announcement describes a split operating boundary: execution stays in the customer’s AWS account, while Vercel retains the surrounding deployment and delivery functions. It does not say that the entire Vercel platform moves into the customer account."
novelty: "notable"
verification_level: "source-linked"
signal_type: "release"
source_platform: "vercel.com"
topics: []
entities: ["Vercel","Bring Your Own Cloud","AWS","Node.js","Python"]
related_patterns: ["agent-security-moves-to-runtime-boundaries"]
source_url: "https://vercel.com/changelog/bring-your-own-cloud-on-aws-is-now-generally-available"
source_urls: ["https://vercel.com/changelog/bring-your-own-cloud-on-aws-is-now-generally-available"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "signal:bring-your-own-cloud-on-aws-is-now-d20cd3"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/signals/bring-your-own-cloud-on-aws-is-now-d20cd3/","markdown":"https://newruntime.com/signals/bring-your-own-cloud-on-aws-is-now-d20cd3.md","json":"https://newruntime.com/signals/bring-your-own-cloud-on-aws-is-now-d20cd3.json"}
---

# Bring Your Own Cloud on AWS is now generally available on Vercel.

## Retrieval answer

## Vercel brings AWS-hosted function execution to general availability

## Vercel brings AWS-hosted function execution to general availability

Vercel says Bring Your Own Cloud (BYOC) on AWS is now generally available to Enterprise customers. Teams can run Vercel Functions in their own AWS account, keeping function code and execution inside their security and compliance boundary. The announcement lists Node.js and Python Functions as supported.

Vercel continues to handle deployments, environments, routing, and static assets. Customers control function execution through their own IAM permissions, network access, and resource lifecycle policies; the release also supports private connections to backends and services in a VPC. BYOC is available on Enterprise plans, and Vercel directs interested customers to sales or their account team.

The announcement describes a split operating boundary: execution stays in the customer’s AWS account, while Vercel retains the surrounding deployment and delivery functions. It does not say that the entire Vercel platform moves into the customer account.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- collection: [Signals](https://newruntime.com/signals.json): Open the signals and the raw-signal archive.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)
