Securing multiple tenants on a GPU is a really, really hard problem. As https://gpuweb.github.io/gpuweb/#malicious-use https://gpuweb.github.io/gpuweb/#maliciou

Securing multiple tenants on a GPU is a really, really hard problem. As https://gpuweb.github.io/gpuweb/#malicious-use https://gpuweb.github.io/gpuweb/#malicious-use notes, there's a tremendous surface for undefined behavior. Now, it does appear that the security model https://developers.cloudflare.com/workers/learning/security-model/ https://developers.cloudflare.com/workers/learning/security-... ensures that any nodes to which the GPU is connected aren't running the full JS Workers code, just the WebGPU functionality. So secrets that are maintained on the JS side aren't likely vulnerable to Cloudbleed-esque attacks: https://en.wikipedia.org/wiki/Cloudbleed https://en.wikipedia.org/wiki/Cloudbleed . But I'd be incredibly wary in sending sensitive information to the WebGPU calls themselves - assume any other WebGPU-using tenant can arbitrarily access data sent to any GPU and modify your outputs.