News for hackers. Stuff that matters.
Re:Vm0 by Severian on Monday January 19, 2026 @08:27AM (#46678747)
I cannot find anywhere in the documentation that shows exactly where or how this "cloud sandbox" is deployed or maintained.

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.

Re:Vm0 by cannonpalms on Monday January 19, 2026 @08:31AM (#46678781)
The canonical solution in this space so far is https://github.com/Dicklesworthstone/agentic_coding_flywheel..., and I would bet that this tool is just a paid version of the same, or worse, just a paid wrapper
Re:Vm0 by jstummbillig on Monday January 19, 2026 @08:54AM (#46678996)
I am also a bit confused by how this is all presented but it seems to be on GitHub too: https://github.com/vm0-ai/vm0
Re:Vm0 by scalemaxx on Monday January 19, 2026 @08:50AM (#46678954)
Especially with the wait list sign up.
Re:Vm0 by ushakov on Monday January 19, 2026 @10:34AM (#46680105)
Re:Vm0 by e7h4nz on Monday January 19, 2026 @09:48PM (#46687332)
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!