@xfgong: Despite the abundance of open-source Sandbox services, none fully meet my needs. The two core requirements are: 1. The rootfs should not require snapshots, which means it should be cloud storage like virtual machines rather than local disks. This mainly addresses availability un…

Even though there are so many open-source sandbox services available, none of them fully meet my needs. The two most critical requirements are:

1. No snapshot needed for rootfs — the rootfs should be cloud storage rather than a local disk, much like a virtual machine. This is mainly to address availability concerns when a node fails, as well as latency issues when pausing a sandbox.

2. The /workspace file operations API should work even when a sandbox is not running — this significantly reduces the startup requirements for sandboxes, cutting costs.

Ideally, it should be built on top of Kubernetes. Some degree of customization is acceptable, but it should not merely use Kubernetes as a host machine (like OpenSandbox’s fast sandbox or how CubeSandbox is used). The talent pool and ecosystem around Kubernetes are far superior. Otherwise, you’d need to operate and maintain a dedicated sandbox cluster, which most companies can’t handle — and that’s exactly what E2B makes money from.