Story
HashiCorp
FiservFiserv Brings Infrastructure as Code onto HashiCorp
Fiserv, a financials organization in the United States, uses Consul from HashiCorp to support environment provisioning for platform engineers.
Fiserv runs environment provisioning on HashiCorp so ownership is obvious when work stalls.
“Financials work at Fiserv spans more than one site, even when headquarters sits in the United States.”
“Platform engineers asked for a shared way to run environment provisioning without freezing local judgment.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Fewer stalled items because infrastructure as code has a clear owner |
| Productivity | Handoffs in environment provisioning sit in a shared queue instead of a mailbox trail |
| Risk and compliance | Consul is the governed place platform engineers use for environment provisioning |
Story
Financials work at Fiserv spans more than one site, even when headquarters sits in the United States. Infrastructure as code was splitting across regional habits. Platform engineers asked for a shared way to run environment provisioning without freezing local judgment.
HashiCorp (Consul) is what they standardized on. HashiCorp (an IBM company) provides infrastructure automation software, including Terraform and Vault, for cloud provisioning and secrets. Fiserv uses it as the system of record for infrastructure as code, with platform engineers 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.
