Tom Lienard

@dominikkoch i’m biased but triangle co

hey gang what sandbox provider would yall recommend (not e2b)

@cramforce hey i recognize this chart

just-bash is the lowest latency option to give bash and a filesystem to your agent. But tbh, I'm much more excited about the Vercel Sandbox team absolutely cooking on latency reduction on the full VMs.

@gerynugrh > Using sandbox does help but the dx suck. Are you referring to Vercel Sandbox? If yes, what could we improve on the DX side?

Why is there no cloud provider that allow us to host an on demand long running agent? Vercel limit execution time to 15 min, cf kills your runtime on every deployment. Using sandbox does help but the dx suck. I feel like this is a big gap waiting to be solved

@mikepunzano @rauchg We’re working on it, more improvements coming soon

@rauchg Improve sandbox spawn time. I love sandboxes and we use them heavily with opencode, but the spawn time is a bit slow particularly when using snapshots.

What service should we build next, with deep care and investment into its security, availability, and durability?

nice

@nicoalbanese10 @i_am_brennan @hp_arora It’s based on the average size in GB of all your snapshots, per month. You can still delete snapshots that you don’t need anymore, which would stop contributing to your bill

@i_am_brennan good question! cc @hp_arora

Let's go! Huge update from previous 7 day limit

@__morse @tobiaslins On Sandboxes we support from 4GB to 16GB of memory. We allocate 2GB of memory per vCPU: #resource-limits" target="_blank" rel="nofollow noopener">vercel.com/docs/vercel-sa…

@tobiaslins is the limit still 2GB of RAM? increasing that to something like 8 would be amazing

Huge unlock - incredible work from the team

@sionemart @vercel_dev Not immediately but in the future yes

@tomlienard @vercel_dev nice. will try and circle back, do you guys plan on increasing the 5hr limit?

Vercel Sandboxes now support filesystem snapshots. Capture complete state with 𝚜𝚊𝚗𝚍𝚋𝚘𝚡.𝚜𝚗𝚊𝚙𝚜𝚑𝚘𝚝() to skip repeatedly slow setup steps like git clone and dependency installation. vercel.com/changelog/file…

@sionemart @vercel_dev $0.08/GB/month. Let us know what you think! #pricing" target="_blank" rel="nofollow noopener">vercel.com/docs/vercel-sa…

@vercel_dev wow this is huge. any information regarding pricing? only reason i was using daytona over vercel sandbox was persistent storage

@skovorodan @MattIPv4 @vercel Looking at the last Node.js releases, it seems this hasn’t be released yet. It’s currently staged for v25.4.0: github.com/nodejs/node/pu…

@tomlienard @MattIPv4 @vercel See also github.com/nodejs/node/pu… This is now marked stable in the current form. The reasoning why this was disabled in AWS no longer holds.

Why on earth am I hitting `ERR_REQUIRE_ESM` errors (`Error: require() of ES Module abc.js from xyz.js not supported.`) on @vercel with their Node.js 24.11.0 runtime? Are they actively setting a flag to opt out of default functionality (#loading-ecmascript-modules-using-require" target="_blank" rel="nofollow noopener">nodejs.org/docs/v24.11.0/…)?

Bypass token is only for deployment protection, doesn’t affect the firewall. You can whitelist specific IPs on pro, but I’d recommend just running 10 RPS for a few minutes to get a good baseline The underlying infra for Node.js and Bun on Vercel is the same, so any difference in performance would be from the runtimes themselves

@tomlienard @_pi0_ Any recommendations / settings for wrk to not be as stressful for the system? I'm not planning to stresstest this often but when changing the main arch/approach to check if it's viable.

1. Why is bun trying to write on a read-only fs? 2. Why is bun not respecting it's own TMPDIR when doing so 3. Why does this happen randomly on Vercel? 4. And why does this happen after not changing a single line of code?

@tomhacks @_pi0_ Were they all 200 responses? You've likely tripped the firewall (vercel.com/YOURTEAM/YOURP…), we won't allow un-approved load tests

wrk -t12 -c400 -d30s Node.js 22.x -> ~6,800 req/s Bun -> ~5,400 req/s Architecture x86_64, ARM64 - Repro: tanstack start bare example & conf: nitro: { preset: "vercel", vercel: { functions: { runtime: "nodejs22.x", // switching to "bun" architecture: "arm64", // environment: { ...bun_vars } }, }, compressPublicAssets: { brotli: true, gzip: true, }, minify: true, },

@_pi0_ @tomhacks +1, def not expected. Happy to help look into it if we have a repro

@tomhacks It is not normal. Would be nice if you can benchmark nitro+bun alone on vercel. Perf should be close to native bun as there is no wrapper added by nitro. Also feel free to report an issue/repro for us to investigate. /cc @tomlienard

@pariscestchiant @vercel @rauchg @cramforce Quick update, it's been released for builds and is currently rolling for functions. Feel free to DM me your team id if you want to get the update immediately

@tomlienard @vercel @rauchg @cramforce you rock

@vercel would it be possible to bump the Bun version used in the function runners to 1.3.6 (latest) please? all of our function executions are crashing atm, and the fix is in that version 🫠 cc @rauchg @tomlienard @cramforce

@samuelcook @rauchg @vercel Soon, cc @ecklflorentin

@rauchg @vercel Nice. When native Go on Fluid?

We've completed the acquisition of the 𝟷𝟺𝟹.𝟷𝟹.𝟶.𝟶/𝟷𝟼 and 𝟷𝟻𝟻.𝟷𝟸𝟷.𝟶.𝟶/𝟷𝟼 IPv4 blocks for @vercel CDN and Fluid compute. Fun fact: these are a piece of internet history, which we acquired from P&G, as part of the "legacy space". ARIN legacy IPv4 ranges are address blocks originally issued before the inception of the regional Internet registry system in 1997. These larger blocks were originally given to corporations like Procter & Gamble and Ford (!) with fewer restrictions and regulations. These days the world is transitioning to the much larger IPv6 space, but IPv4 is still incredibly valuable for interoperability with billions of devices and huge amounts of infrastructure. High quality and high reputation IPs like these are scarce and expensive. They're like a rare, borderless PSA 10 Charizard. Each day there's fewer of them. Security and availability are the top priority at @vercel. Our teams do a lot of work behind the scenes to make sure your visitors get the best global access to your projects, with your infra on autopilot 🫡

@simonfarshid @rauchg Elysia/TypeBox for example use the Function constructor, which I believe isn't required but would still be a breaking change on our side

@tomlienard @rauchg I wonder, any popular libs that depend on dynamic evals? 😯

That’s technically already possible if you pass it via NODE_OPTIONS, but it breaks during build and very likely at runtime because many libs depend on dynamic evals That’s also why Workers now support it during the init phase. We might be able to do the same but it would be opt in

@rauchg @tomlienard That’d be great! I sleep happy knowing workerd / Cloudflare Workers doesn’t support string evals at all — would be good to have it on our Vercel compute endpoints as well

@MattIPv4 @vercel Quick update, I have a fix for this that will be rolled out over the next few business days This was a regression for those two specific options (--experimental-require-module, --experimental-detect-module) when used within NODE_OPTIONS

@MattIPv4 @vercel Definitely not expected. I’ll take a look