This week Vercel announced that Sandbox, their runtime for coding agents, is "now available globally." I read the announcement twice because the second paragraph didn't match the first. Global, it turns out, means four regions: Washington D.C., San Francisco, Cleveland, and Paris. Everywhere else is listed as "coming soon," with no date attached.
If you don't pick a region explicitly, your sandbox runs in Washington by default. So today, in practice, "global" means North America plus one European city. Nothing in Asia. Nothing in South America. Nothing in Africa. I don't think anyone at Vercel is lying, and I'm not writing this to dunk on a product I actually use pieces of. I'm writing it because I've made the mistake this headline sets up for, more than once, and I'd rather name the pattern than let it happen a third time.
What the announcement actually says once you slow down
Marketing copy compresses. That's its job. "Globally available" is nine syllables that are supposed to answer the question "can I put this in production for users anywhere" with a yes. The honest answer, buried in the region list a few lines down, is "yes, if your users are near the US East Coast or Western Europe, and maybe soon if they're not."
That gap between the headline claim and the region table isn't unique to Vercel. I've seen the same shape in CDN edge-network pages, in database read-replica docs, in queue services that advertise "multi-region durability" and then define region as three availability zones inside one country. The word doing the heavy lifting is always the same one: global. It's a claim about scope, and scope is exactly the dimension that's hardest to verify from a landing page, because verifying it means going and finding the actual list, which most people don't do. I almost didn't.
Why this isn't just a semantic nitpick
Here's the concrete version of why it matters. Say you're building something with users concentrated in Bogotá, São Paulo, or Lagos, and this week's announcement makes you consider moving a workload to Sandbox because "global" sounds like it solves your latency problem. You provision it, don't set a region because the docs imply it doesn't matter anymore, and it lands in Washington by default. Your agent calls now cross an ocean or two continents round-trip. You've traded a latency problem you understood for one you didn't know you had, because the word on the announcement told you the geography question was already solved.
I care about this specifically because LoteríaYa's audience is entirely in Colombia. Every infrastructure decision I've made for that project, from where the app deploys to how aggressively I cache, has had one question behind it: how far is this from Bogotá, actually, not how far is it from wherever the vendor's flagship region sits. When a provider says "global" I've learned to translate it in my head to "list the actual regions before you plan around this," because the two words mean different things and only one of them is a promise I can build on.
The checklist I actually run now
I didn't always do this. Early on I took "available worldwide" claims at close to face value, because checking felt like paranoia over a marketing headline nobody expected you to audit. What changed my mind wasn't one dramatic outage, it was a slower accumulation of small mismatches between what a page said and what the docs three clicks deeper actually listed. Now, before an infra announcement changes anything about how I design something, I run it through three questions.
First: what's the actual region list, not the adjective. If a page says "global" or "worldwide," I go find the table. If there isn't one, that's information too, it usually means fewer regions than the word implies.
Second: what happens if I do nothing. Defaults tell you where a vendor's actual center of gravity is. Sandbox defaulting to Washington tells you this is a US-built, US-first product extending outward, not a genuinely distributed one yet. That's not a criticism, most products start that way. It's just useful to know you're an edge case, not the default case, if you're building from somewhere else.
Third: is there a date attached to "coming soon," or is it a roadmap item with no commitment. A dated region is a plan. An undated one is closer to a wish, and treating a wish as load-bearing infrastructure for a decision you're making today is how you end up rearchitecting twice: once now, based on the promise, and once again in six months when the promise hasn't landed and you finally check.
None of these take more than the time it takes to read the docs page instead of the announcement post. That's the whole fix, honestly. It's not sophisticated. It's just the habit of reading past the sentence written to be quoted and into the sentence written to be accurate.
The part that's easy to miss if you're annoyed at the marketing
I don't think the instinct to reach for "global" is dishonest so much as it's a bet vendors make on velocity. Announcing four regions with a roadmap for the rest gets you the same headline as announcing forty regions, and the cost of being technically imprecise about it is close to zero, because almost nobody goes and reads the region table. The incentive to say "global" the day you have four regions and a plan is just stronger than the incentive to say "we're in four regions, more coming, no dates yet," even though the second sentence is the one that's actually useful to a person making an infrastructure decision this week.
That's not a Vercel problem specifically. It's what happens whenever a company's fastest path to good headlines and a customer's need for accurate planning information point in slightly different directions. The company isn't wrong to optimize for the headline. But the customer reading it has a different job than the company writing it, and it's on the customer, not the vendor, to notice the gap.
Where I landed
I'm still going to use Sandbox for things that work fine out of Washington or Paris. I'm not going to use it yet for anything where latency to Colombia is the thing the product depends on, and I wouldn't have known to ask that question if I'd stopped reading at "globally available."
The lesson I keep relearning isn't "don't trust announcements." It's narrower than that: treat the word describing scope as a claim to verify, not a fact to inherit, especially when the claim is the one thing standing between you and a decision that's expensive to reverse. Four regions with a roadmap is a perfectly fine place for a product to be. It's just not the same sentence as global, and the six words of difference are exactly the ones worth reading twice.
If you've shipped something on a "coming soon" region that never got a date, or picked a default region without realizing it wasn't the one closest to your users, I'd be curious how you caught it, and how long it took.