The Challenge
As Watch Duty grew from a small startup into a high-profile nonprofit serving millions of users, security pressure increased from two directions at once. They needed SOC 2 compliance to support enterprise sales, and they were also facing real-world threats driven by their public visibility.
They ran into several challenges:
- Vendor sprawl vs. team size: The typical path to security and compliance meant adopting multiple vendors. For a team that started with just four engineers, managing several separate tools, contracts, and integrations felt like overkill.
- The dread of compliance overhead: CTO David Merrit saw a future where security and compliance work consumed a huge share of his time. Managing vendors, integrations, and day-to-day security tasks threatened to crowd out actual product development.
- High-profile threat exposure: Watch Duty operates in the public eye. As usage grew, so did malicious activity, including phishing attempts, fake apps, and domain squatting designed to exploit their brand.
- Avoiding security theater: The team wanted to avoid tools that simply produced green checkmarks for auditors. They needed real protection for their infrastructure and user data, not just compliance optics.




