←back to thread

Show HN: Katakate – Dozens of VMs per node for safe code exec

(github.com)

120 points gbxk | 1 comments | 21 Oct 25 15:22 UTC | HN request time: 0.212s | source

I've built this to make it easy to host your own infra for lightweight VMs at large scale.

Intended for exec of AI-generated code, for CICD runners, or for off-chain AI DApps. Mainly to avoid Docker-in-Docker dangers and mess.

Super easy to use with CLI / Python SDK, friendly to AI engs who usually don't like to mess with VM orchestration and networking too much.

Defense-in-depth philosophy.

Would love to get feedback (and contributors: clear & exciting roadmap!), thx

Show context

re_spond ◴[22 Oct 25 06:14 UTC] No.45665429[source]▶

>>45656952 (OP) #

Looks like an interesting project. Do you have any comments on how it is different from running gVisor?

replies(1): >>45666785 #

1. gbxk ◴[22 Oct 25 09:44 UTC] No.45666785[source]▶

Thanks! Yes: Katakate provides much stronger isolation, since it uses hardware virtualization (via Kata Containers and Firecracker) while gVisor relies purely on software sandboxing in user space.

gVisor isolates containers by intercepting system calls in a user-space kernel, so it can still be vulnerable to sandbox escape via gVisor bugs, though not directly through Linux kernel exploits (since gVisor doesn’t expose the host kernel to the container).

Katakate also provides more than isolation: it offers orchestration through Kubernetes (K3s)

You could create a gVisor RuntimeClass in Kubernetes to orchestrate gVisor sandboxes, but that would require extra setup.