# Vercel — A sandbox without a network boundary is only half a sandbox

- Company: Vercel (vercel.com)
- Announced: 2026-08-11
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://vercel.com/blog/a-sandbox-without-a-network-boundary-is-only-half-a-sandbox
- Record: https://forck.live/items/20676-a-sandbox-without-a-network-boundary-is-only-half-a-sandbox
- Subject: v0 / AI SDK / AI Gateway

Vercel published a technical post arguing that sandbox security requires both compute isolation and network egress control, because untrusted code can exfiltrate data or attack external systems without escaping the VM. The post describes how Vercel's sandbox firewall enforces domain and CIDR policies by inspecting TLS handshakes and filtering DNS traffic on the host, outside the microVM.

## Evidence

Verbatim from https://vercel.com/blog/a-sandbox-without-a-network-boundary-is-only-half-a-sandbox:

> A complete sandbox therefore needs both compute isolation and control over the authority available through its network: where code can connect, which credentials it can use, and how those permissions change throughout the workload’s lifecycle.

---

Record: https://forck.live/items/20676-a-sandbox-without-a-network-boundary-is-only-half-a-sandbox
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md