My best guess is you're talking about sandboxing, specifically how we defend ourselves against malicious tenants. Indeed, a lot of how we defend against that is not in workerd, and fundamentally can't be, because it's more than just some code, it's a process requiring active management.
However, you only need that if you have untrusted tenants.
If you are using workerd to self-host your own applications on non-Cloudflare infrastructure, then this isn't a concern for you. You don't have untrusted tenants.
If you are hosting untrusted tenants, then you can put workerd in a micro VM, the same as you'd do with any other popular runtime.
My best guess is you're talking about sandboxing, specifically how we defend ourselves against malicious tenants. Indeed, a lot of how we defend against that is not in workerd, and fundamentally can't be, because it's more than just some code, it's a process requiring active management.
However, you only need that if you have untrusted tenants.
If you are using workerd to self-host your own applications on non-Cloudflare infrastructure, then this isn't a concern for you. You don't have untrusted tenants.
If you are hosting untrusted tenants, then you can put workerd in a micro VM, the same as you'd do with any other popular runtime.