Join us as we explore what it takes to re-architect the entire software development lifecycle when the pipeline now serves agents, not just developers! In this episode, Ariel Nackash, Head of DevOps at SecuriThings, shares why he joined a ~100-person startup at the exact moment it's trying to become an AI-native organization, and how he's rebuilding the SDLC for a world where agents do the bulk of the coding — while developers level up to architects and the final approval gate where code meets the main branch ("the human never leaves the loop"). Discover why an agentic pipeline has to absorb 10x the load, why splitting into autonomous vs. human-in-every-iteration cycles matters, and why Ariel bets DevOps teams won't disappear in 2027 — they'll become "Agentic Platform Engineers." Ariel Nackash on LinkedIn - https://www.linkedin.com/in/ariel-nackash-8030601/ Miki Manor on LinkedIn - https://www.linkedin.com/in/mikimanor/ Ofir Stein on LinkedIn - https://www.linkedin.com/in/ofir-stein/ DevOps Leaders - https://www.linkedin.com/company/devops-leaders-il/posts/?feedView=all Key takeaways: SecuriThings is the only company that actually remediates and patches the vulnerabilities on the IoT/physical-security device itself — cameras, access controllers, and the thousands of unmanaged devices sprawled across enterprise data centers — not just detects them The first problem in IoT security isn't patching, it's inventory: most orgs have no idea what devices, vendors, or firmware versions are even on their network, with unaddressed CVEs running live compute on managed networks Physical security has no "IT team" to defend it — the wedge is connecting physical-security teams to IT, speaking in IT terms, and giving operators the single pane of glass they need for patching and compliance Going AI-native isn't buying Claude and Cursor licenses and letting people play — it's designing a custom SDLC where the pipeline now serves agents alongside your developers An agentic pipeline must absorb ~10x the load, handle new security risk, preserve quality, and stay tailored to the business — old problems, but far more extreme Build for two cycle types: free, autonomous cycles that need little human involvement, and tighter iterative cycles where a human sits on every iteration Developers don't disappear — they level up to architects who see the big picture, keep work custom to the business logic, and own the final approval gate where new code meets the main branch Ariel's open question for the next guest: how do you build a self-maintaining, always-current knowledge layer (from Confluence, Git, posts) that stays accessible as context to agentic flows — efficient and learning, never solving yesterday's problems We're recording live from the PlatforMa conference in Tel Aviv, featuring fascinating discussions on AI and more. Join our exclusive DevOps Leaders community with over 300 members, where we share knowledge and improve together.What's your biggest challenge in the DevOps field? Drop it in the comments! Subscribe for weekly insights and updates on the latest in DevOps!#DevOps #Podcast #Technology #AI #SecuriThings
