Story
Disco Adopts Snyk for Environment Provisioning
Disco, an information technology organization in Japan, uses Snyk IaC from Snyk to support environment provisioning for platform engineers.
Value results
| Category | Value result |
|---|---|
| Capability | Named workflow replaces ad hoc routing for infrastructure as code |
| Capability | Environment provisioning stays visible to adjacent teams through Snyk IaC |
| Capability | Platform engineers work from the same Snyk IaC record for infrastructure as code |
Story
Inside Disco, environment provisioning used to depend on whoever still had the latest file. That pattern is common in information technology groups working out of Japan. Platform engineers needed a system that would still make sense after the original project team moved on.
Disco uses Snyk IaC from Snyk as the working layer for infrastructure as code. Snyk helps developers find and fix vulnerabilities in code, open source, containers, and infrastructure as code. The practical change is simple: environment provisioning has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Disco gets from Snyk is a durable place to run environment provisioning and a way for platform engineers to see the same infrastructure as code at the same time.