A sandbox, a function, a build, a server. They're all expressions of the same underlying compute infrastructure on Vercel. Fluid Compute is one system that creates the machine your workload needs, on demand.

Vercel Sandbox now runs in more regions. Closer to your data, less latency on every call. 𝚊𝚠𝚊𝚒𝚝 𝚂𝚊𝚗𝚍𝚋𝚘𝚡.𝚌𝚛𝚎𝚊𝚝𝚎({ 𝚛𝚎𝚐𝚒𝚘𝚗: "𝚌𝚍𝚐𝟷", 𝚏𝚊𝚒𝚕𝚘𝚟𝚎𝚛𝚁𝚎𝚐𝚒𝚘𝚗𝚜: ["𝚒𝚊𝚍𝟷", "𝚌𝚕𝚎𝟷"] })

The Sandbox's bridge exploit minted unbacked SAND on Base and BSC. Upbit and Bithumb froze transfers under South Korea's user-protection rules, with Upbit also halting @ethereum deposits and withdrawals despite the chain being unaffected. Read more here:

Vercel Sandbox firewall can now proxy and filter outbound requests. ▪︎ Control all agent traffic from your own proxy ▪︎ More granular credential injection ▪︎ Log and audit outgoing traffic

I finally get the sandboxes use case. has nothing to do with security it’s unbounded resources (only limited by $) Now that I know how to use agents I’m constrained by a single device (3 typechecks at once bring it down) This clicked when I was wondering why our slack bot felt so frictionless and we started doing so much work there It’s because you don’t have to care at all where it’s working… so now I want that locally