Cloudflare Sandbox SDK • Hacker News Board

Re: Cloudflare Sandbox SDK

#91

Post by ozeron » Fri, Oct 17, 2025, 5:15 PM UTC

Looking at pricing for this and especially for E2B. I've decided to work on a lightweight alternative to Cloudflare’s Sandbox because I ran into the same pain points with current solutions: - limited parallelization - expensive

My focus is: - simple SDK primitives for code execution, file ops, and git checkout—no boilerplate stacks - transparent pricing (per-second compute with monthly caps, no surprise egress) - price sandboxes for 50-60% less then competitors

Would love to get your feedback in https://usesandbox.dev/ Just finalized main pieces today

Re: Cloudflare Sandbox SDK

#92

Post by ZiiS » Fri, Oct 17, 2025, 10:28 PM UTC

ameliaquining wrote: post #83

ZiiS wrote: post #72

Earlier quoted context omitted.

This code has to run inside their Worker's platform; _technically_ you can compile Go to WASM and get it to run; but practically it is Javascript only.

IIUC this particular product runs in Linux containers, not in V8 isolates like Workers uses. The upside of this is broader ecosystem compatibility (you can use whatever language you want even if it doesn't compile efficiently to Wasm); the downside is that each container instance runs in a particular data center and you have to worry about the latency implications of that, whereas every Worker runs in every location.

This comment was complaining the example for launching the container was in JavaScript, this bit has to run in v8.

Re: Cloudflare Sandbox SDK

#93

Post by ZiiS » Fri, Oct 17, 2025, 10:32 PM UTC

alooPotato wrote: post #81

ZiiS wrote: post #71

Earlier quoted context omitted.

Sandbox is built on top of their Durable Objects; the underlying storage is $0.20/ GB-month.

You’re saying the file system in the container is persisted to the durable object storage? That doesn’t sound right.

Whilst it is in the idle state. Not whilst it is stopped.

Re: Cloudflare Sandbox SDK

#94

Post by aperture147 » Mon, Oct 20, 2025, 2:47 PM UTC

Neat feature to make use of Containers. I'm thinking of wrapping my video renderer in Containers and use sandbox to spawn the rendering job, but I'm not sure about the limitation of CF containers, such as how much vCPUs I have, how many capability I can get from containers (like SYS_NICE), how many RAM I have and how many jobs I can run at the same time, is there any built-in queue like Runpod (which I am using) to ratelimit the job, etc. I will give this a try.

Re: Cloudflare Sandbox SDK

#95

Post by freakynit » Wed, Oct 22, 2025, 1:11 PM UTC

chandureddyvari wrote: post #64

freakynit wrote: post #57

Earlier quoted context omitted.

Serously, what flexibility? I coud easily spin-up a firecracker VM on-demand and put it behind an API. It boots up in under 200 milliseconds. and I get to control it however I wish to. And also, all costs are under my control. I compared the costs with instances purchased from Hetzner or Contabo here: https://news.ycombinator.com/item?id=45613653 Bottomline: by doing this small stuff myself, I can save 35 times more.

In my case, it is ignorance. I am not familiar with how to wield firecracker VMs and manage their lifecycle without putting a hole in my pocket. These sandbox services(e2b, Daytona, Vercel, etc.) package them in an intuitive SDK for me to consume in my application. Since the sandboxing is not the main differentiator for me, I am okay to leverage the external providers to fill in for me. That said, I will be grateful…

Lol.. a full-fledged project just launched on Github using firecracker and giving cli/api interfaces: https://github.com/Katakate/k7