3 ms·
Show HN: Agyn, an open-source Kubernetes runtime for AI agents
- deleted 6mo ago[deleted]
- vitramir 6mo ago[flagged]
- islammidov 6mo agoso the core idea works only for Kubernetes?
- NBenkovich 6mo agoYes, Kubernetes only today. We're considering VM support given the demand we've seen, but no concrete plans yet. What is your use case?
- deleted 6mo ago[deleted]
- deleted 6mo ago[deleted]
- NBenkovich 6mo ago[dead]
- itchernetski 6mo agodefinitely gonna star for later check
- NBenkovich 6mo agoThanks a lot! Let us know if you have any questions!
- deleted 6mo ago[deleted]
- NBenkovich 6mo ago[dead]
- AccordionGuy 6mo agoCongrats on the launch! I’m happy to see OpenZiti in your networking stack alongside Istio. The combo of sandbox-per-agent and MCPs-in-separate-containers is exactly the kind of deployment that benefits from identity-based, zero-listening-port connectivity between components. If you're up for it, we'd love to have someone from Agyn on Ziti TV (our livestream) to talk about how you're using OpenZiti and what you're building on the agent-infra side. Drop me a line if you're interested — joey.devilla@netfoundry.io. Disclosure: As my email address implies, I work at NetFoundry, which created and sponsors OpenZiti. I’m their Developer Advocate and it’s my job to promote OpenZiti (and especially for AI tools and platforms), but either way, I really like what you're shipping here.
- NBenkovich 6mo agoThanks Joey! Really appreciate it. Zero-trust by default is a big part of how we’re designing Agyn, and OpenZiti fits that really well. We’re big fans of what you’re building. Would be happy to join Ziti TV and talk about how we’re using it. I’ll drop you a line.
- vzd3v 6mo agoNice work. Agents are quickly becoming infra, not just local dev tools. Keeping credentials inside the tool container feels much closer to how this should work. But in a lot of teams the starting point is not “we need an agent platform”. It is the CEO saying: "we give everyone Claude Code accounts, go use them ASAP!!!". Do you expect teams to jump from local Claude/Codex/Cursor usage straight into a k8s-native runtime?