Story
HashiCorp
Jack HenryHashiCorp at Jack Henry: Build and Deploy
Jack Henry, a financials organization in the United States, uses Boundary from HashiCorp to support continuous delivery for engineering teams.
When build and deploy outgrew homegrown tracking, Jack Henry brought in HashiCorp.
“From the United States, financials teams still had to serve customers and internal partners who expected a straight answer.”
“HashiCorp (an IBM company) provides infrastructure automation software, including Terraform and Vault, for cloud provisioning and secrets.”
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 | Boundary is the governed place engineering teams use for continuous delivery |
| Capability | New joiners can see how continuous delivery actually runs |
Story
Jack Henry grew build and deploy faster than the local tools around it. From the United States, financials teams still had to serve customers and internal partners who expected a straight answer. Engineering teams were the ones stitching the picture together by hand.
Rolling out Boundary put continuous delivery on HashiCorp. HashiCorp (an IBM company) provides infrastructure automation software, including Terraform and Vault, for cloud provisioning and secrets. Jack Henry keeps the product in the path where work already happens, so engineering teams do not context-switch into a graveyard system used only for audits.
The visible result is steadier continuous delivery. Build and deploy is easier to inspect, and adjacent groups can join engineering teams without a guided tour of someone's desktop.
