What's Blocking Fully Autonomous Vibe Coding?
18m
AI can generate code faster than ever, but running that code in production is still the hard part. Alan Shimel talks with Assaf Sauer, founder and CTO of Stacktic.io, about what is blocking fully autonomous vibe coding and operations, and how Stacktic aims to close the gap.
From presales architect to founder
Assaf spent years as a presales architect for a US-based vendor before leaving to file a patent and start Stacktic. When AI became widely accessible, he realized that years of automation code could be rebuilt in days. However, he also spotted a gap between what AI generates and what it can safely automate, and that gap is what holds back vibe coding today.
Why vibe coding struggles in production
The core problem, Assaf says, is relationships. A single Kafka topic connected to a database brings code, infrastructure, connector versions, mTLS, secrets, Kubernetes settings, RBAC and observability. Change one piece and you may break compliance somewhere else. As a result, AI gives inconsistent answers and can't yet be trusted to run things on its own.
Mapping every relationship
Stacktic sits between GitHub and production as a framework that AI clients reach through MCP. It maps and stores the relationships across an application, so every AI change is governed and checked against standards such as PCI DSS or HIPAA. Furthermore, both humans and AI can see the full topology and validation status before anything ships. That validation is what makes vibe coding production ready.
Vibe coding without vendor lock-in
Because every session runs through the same platform, it doesn't matter whether developers use Claude Code, ChatGPT Codex or a local model. In addition, Stacktic packages each stack as open source and cloud agnostic, so teams can move it between clouds, on-premises or air-gapped environments.
Production-ready vibe coding depends on trust, governance and validation. Explore more DevOps coverage and the latest Techstrong TV interviews.
For more information please visit stacktic.io