Story
Snyk
ExelonHow Exelon Runs Continuous Delivery on Snyk Code
Exelon, a utilities organization in the United States, uses Snyk Code from Snyk to support continuous delivery for engineering teams.
Snyk is how Exelon keeps build and deploy visible to people who have to act on it.
“Utilities work at Exelon spans more than one site, even when headquarters sits in the United States.”
“Engineering teams asked for a shared way to run continuous delivery without freezing local judgment.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Handoffs in continuous delivery sit in a shared queue instead of a mailbox trail |
| Risk and compliance | Snyk Code is the governed place engineering teams use for continuous delivery |
| Capability | New joiners can see how continuous delivery actually runs |
Story
Utilities work at Exelon spans more than one site, even when headquarters sits in the United States. Build and deploy was splitting across regional habits. Engineering teams asked for a shared way to run continuous delivery without freezing local judgment.
Snyk (Snyk Code) is what they standardized on. Snyk helps developers find and fix vulnerabilities in code, open source, containers, and infrastructure as code. Exelon uses it as the system of record for build and deploy, with engineering teams as the primary operators and other groups coming in through the same queue.
Leaders get a picture they can actually walk. Teams get fewer mystery statuses. The story is about operating change, not an unpublished percentage.
