See Snyk in action

Spotify

"Spotify has thousands of engineers, so we were very intentional when implementing security testing automation, keeping developer needs top of mind and freeing up developers to focus on their own priorities. For some languages and frameworks, we’ve automatically embedded vulnerability scanning in CI/CD pipelines, so the adoption has been seamless and hasn’t required any action from developers… Now the number of scanned projects continues to increase.”

Edina Muminovic | Engineering Manager, Spotify

Pinterest

"At Pinterest, we use language-specific mono repos. Once you add a mono repo to Snyk, any new project that gets created in that repo gets automatically added. So there’s no additional work that needs to be done when a new project is created in that repo. Once code is merged to the repository and the Snyk scan happens, that’s when we understand what dependencies were introduced. [When a developer creates a project in their mono repo, the scan is] transparent to the developer. They don’t even need to know that Snyk is running."

Kalpesh Dharwadkar | Product Security Engineer, Pinterest

Reddit

“Snyk has helped shift Reddit away from a reactive security team initiated approach toward a developer-led approach for remediation. We like Snyk because of the ability to centralize some of our tooling and being able to touch things at scale within our developers’ workflows. Snyk is very dev-centric and was also easy for us to scale out without being disruptive. Automating some of these things has reduced the operational burden and lowered the total cost of ownership for adopting the Snyk platform."

Spencer Koch | Security Wizard, Reddit