E80: Securing Kubernetes With ARMO & Kubescape

Repositioning

ARMO's strategic repositioning from runtime security to DevOps-focused solutions marked a significant shift in the company's direction. Shauli Rozen explains that while they initially focused on runtime security, feedback from the market led them to pivot towards DevOps, which demanded simpler, open-source solutions 1. This transition was not without challenges, as it required admitting past missteps and overcoming the emotional hurdle of sunk costs. Rozen highlights the importance of having the right team to support such a shift, noting, "We had the right team. We had people who were drinking open source because they were developers on their own" 2.

   

User Feedback

Navigating user feedback was crucial in ARMO's repositioning efforts. Rozen discusses the challenges of filtering noise from user feedback and the importance of analytical processing to make informed decisions 3. They initially struggled with managing feedback on Discord, leading to a transition to a CNCF Slack channel for more meaningful interactions. Rozen admits, "Sometimes you follow the noise. You know, someone might be just more vocal than others in the requirements, and then you go there and we've sometimes made those mistakes" 3.

   

Decision-Making

Key decision-making at ARMO involved strategic choices around pricing and open-source commitments. Rozen emphasizes the importance of not hesitating to monetize valuable offerings, despite fears that users might only engage with free products 4. He also discusses the decision to maintain a strong open-source strategy, resisting the urge to quickly transition to closed-source models. "Whenever you run an open source company, constantly, constantly you get those tensions of, yeah, why are we giving this for free?" Rozen reflects on the challenges of balancing open-source ideals with business needs 5.