Story
HashiCorp
CrowdStrike FalconCrowdStrike Falcon Brings Build and Deploy onto HashiCorp
CrowdStrike Falcon, an information technology organization in the United States, uses Consul from HashiCorp to support continuous delivery for engineering teams.
HashiCorp is how CrowdStrike Falcon keeps build and deploy visible to people who have to act on it.
“Inside CrowdStrike Falcon, continuous delivery used to depend on whoever still had the latest file.”
“Engineering teams needed a system that would still make sense after the original project team moved on.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | Build and deploy can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for build and deploy |
| Capability | Continuous delivery stays visible to adjacent teams through Consul |
Story
Inside CrowdStrike Falcon, continuous delivery used to depend on whoever still had the latest file. That pattern is common in information technology groups working out of the United States. Engineering teams needed a system that would still make sense after the original project team moved on.
CrowdStrike Falcon uses Consul from HashiCorp as the working layer for build and deploy. HashiCorp (an IBM company) provides infrastructure automation software, including Terraform and Vault, for cloud provisioning and secrets. The practical change is simple: continuous delivery has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What CrowdStrike Falcon gets from HashiCorp is a durable place to run continuous delivery and a way for engineering teams to see the same build and deploy at the same time.
