Anaconda Puts Guardrails on Agent Swarms
23m
AI agents now work side by side in swarms, and that raises new security questions. Alan Shimel talks with David DeSanto, CEO of Anaconda, about how the company brings guardrails, least privilege access and visibility to agent swarms.
From Python packages to an AI platform
DeSanto joined Anaconda as CEO a year ago after six years as chief product officer at GitLab. Anaconda started with Python packages and Conda, and it now serves more than 55 million users. Over the past year, it acquired Outerbounds for production AI, Kilo for agentic engineering and Encrypt AI for red teaming and guardrails. As a result, the platform now runs end to end, from building with agents to production.
Securing agent swarms
Anaconda's general availability release added agent swarms that run in parallel inside notebooks and IDEs. However, swarms raise real risks. So every agent runs with least privilege access, inside guardrails, and talks to other agents through a secure message board. In addition, an agent must ask for access to a specific file for a specific purpose, and a person can approve it once.
Agent swarms and the AI dev factory
DeSanto says traditional software development is giving way to the AI dev factory. Agents now write the code, so teams must test and secure it before it ships. For example, Encrypt AI scanned 25,000 MCP servers and found 143,000 vulnerabilities across 73% of them. That is why autonomous red teaming and guardrails matter as agent swarms spread.
A hopeful view of AI
Despite a rough month for security, both Shimel and DeSanto remain optimistic. DeSanto points to McGill University, which used Anaconda to find a $10 alternative to a $10,000-a-month cancer drug. Still, he urges teams to use secure open source, consider open-weights models and build security into every step.
Agent swarms can speed up development when they run safely. Explore more DevOps and AI videos and the latest Techstrong TV interviews.
For more information please visit anaconda.com