hi, I'm VM0's developer. Happy to answer your questions.
I fully agree, without clear architecture docs, I wouldn't trust an infra service either. We're working on technical documentation now.
Here is some quick summaris about our arch, we uses E2B's managed sandbox (Firecracker microVMs), and keep working on our own Firecracker runner implementation (independent of E2B) with experimental network firewall features.
We use E2B because easy to start, no infrastructure needed, but self-hosted give developer full control, custom security policies, run on your own infra.
We're at an early stage and planning to release end of Jan. Detailed architecture docs are coming soon. Feedback welcome!
Is this Docker, Kubernetes, KVM/Xen, AWS, Azure, GCP, Fly.io, some other VM tech, or some rando's basement ?
Very little detail and I don't trust this at all.