From 80 Days to 5: How Banco Bradesco Transformed Infrastructure Delivery with HCP Terraform Orchestration

<p>Banco Bradesco, one of Latin America's largest banks, faced a critical bottleneck: provisioning a fully compliant infrastructure product could take up to 80 days. The process required coordination across multiple teams—platform engineering, security, networking, and IT service management. Governance was strict, cloud adoption was accelerating, and complexity was rising. In the banking sector, such delays translate directly into lost business opportunities and increased regulatory risk. Reducing provisioning time became a strategic imperative. Bradesco turned to HCP Terraform not just as an automation tool, but as a central orchestration platform. By embedding Terraform into a governed, self-service operating model, the bank slashed provisioning time from 80 days to just 5. This article explores how Bradesco achieved this transformation through a series of key questions and detailed answers.</p> <h2 id="q1">1. What was the core infrastructure delivery challenge at Banco Bradesco before adopting HCP Terraform?</h2> <p>Before implementing HCP Terraform, Bradesco's infrastructure delivery process was slow and fragmented. Each new environment required extensive manual coordination across platform engineering, security, networking, and IT service management teams. Automation existed but was applied inconsistently—change management, CMDB registration, and policy validation were handled as separate, often manual, steps. Compliance checks relied on human oversight, introducing delays and errors. With over 20 internal producer teams contributing to a catalog of more than 500 Terraform modules, shared repositories alone couldn't enforce consistent governance. The result: provisioning a new fully compliant environment could take up to 80 days from request to production readiness. This bottleneck hindered the bank's ability to rapidly launch digital products and respond to market opportunities.</p><figure style="margin:20px 0"><img src="https://www.datocms-assets.com/2885/1776372596-diagram.png" alt="From 80 Days to 5: How Banco Bradesco Transformed Infrastructure Delivery with HCP Terraform Orchestration" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: www.hashicorp.com</figcaption></figure> <h2 id="q2">2. How did HCP Terraform enable Bradesco to reduce provisioning time from 80 days to just 5?</h2> <p>By positioning HCP Terraform as the control plane for platform engineering, Bradesco transformed infrastructure delivery from a fragmented process into a governed, scalable, self-service operating model. Instead of using Terraform as an isolated provisioning engine, the bank embedded it into a broader orchestration framework. This framework validated Sentinel policies before deployment, enforced approval requirements for production, integrated automatically with ServiceNow change workflows, and registered infrastructure assets in the CMDB. Every infrastructure request now flows through a consistent, automated model. The result: what once required 80 days now takes just 5. This dramatic reduction means new digital products and services reach the market in days instead of weeks, accelerating innovation without compromising mandatory controls.</p> <h2 id="q3">3. What is the difference between automation and orchestration in Bradesco's context?</h2> <p>Internally, Bradesco defined orchestration as the structured coordination of automated steps executed in a predefined, governed sequence—from validation through provisioning to post-installation workflows. Automation alone was insufficient because it only replaced individual manual tasks with scripts, leaving gaps in process integration. Fragmented automation meant that change management, CMDB registration, and policy checks still required handoffs or manual intervention. Orchestration, by contrast, ties these automated steps together into a single, coordinated workflow. Using HCP Terraform as the central backend, Bradesco connected developers, the private module registry, Sentinel policies, run tasks, self-hosted agent pools, and multi-cloud providers. This shift consolidated execution, governance, and visibility into one platform, enabling consistent delivery at scale.</p> <h2 id="q4">4. How did Bradesco embed Terraform into its platform engineering strategy?</h2> <p>Rather than treating Terraform as an isolated provisioning tool, Bradesco made it the centralized backend for platform engineering orchestration. The bank used Terraform not only for running plans and applies but also to standardize the platform structure itself. Organizations were segmented by environment, projects grouped workloads by domain and cost center, and workspaces followed strict naming conventions and metadata standards. Policy sets and variable sets were consistently applied across environments. Terraform became the glue connecting developer self-service, the private module registry, Sentinel policy enforcement, ServiceNow change management, and multi-cloud providers. This embedded approach turned Terraform into a control plane that enforces governance automatically, ensuring every infrastructure request follows a compliant, repeatable path.</p> <h2 id="q5">5. What specific governance controls did Bradesco implement using HCP Terraform?</h2> <p>Bradesco implemented a series of governance controls that run automatically as part of every infrastructure deployment. <strong>Sentinel policies</strong> validate compliance before any apply is executed. For production environments, <strong>approval requirements</strong> are enforced through HCP Terraform's run tasks. The platform <strong>automatically integrates with ServiceNow</strong> to manage change workflows, ensuring every deployment is tracked and approved. Additionally, infrastructure assets are <strong>registered in the CMDB</strong> without manual intervention. Environment segmentation ensures that development, test, and production follow distinct rules. Policy sets and variable sets are applied consistently across workspaces. These controls eliminated manual checkpoints and reduced regulatory risk, while enabling faster delivery. By embedding governance into the orchestration layer, Bradesco achieved compliance without sacrificing speed.</p> <h2 id="q6">6. How did Bradesco structure workspaces and projects for scalability?</h2> <p>To manage over 20 internal producer teams contributing more than 500 Terraform modules, Bradesco needed a structured governance model. They used HCP Terraform's organizational hierarchy: organizations were segmented by environment (dev, test, prod), projects grouped workloads by domain and cost center, and workspaces followed strict naming conventions and metadata standards. This structure ensured consistent application of policy sets and variable sets across environments. By standardizing the platform itself, Bradesco enabled teams to discover and reuse modules easily while maintaining compliance. The segmentation also allowed different governance rules per environment—for example, production required additional approvals. This scalable approach meant that as the number of teams and modules grew, governance and visibility remained intact.</p> <h2 id="q7">7. What business impact did the transformation have on time-to-market and agility?</h2> <p>The reduction from 80 days to 5 for infrastructure provisioning directly accelerated Bradesco's ability to launch digital products and services. Initiatives that once waited weeks for approved infrastructure can now go to production in days. This speed allows the bank to respond quickly to market opportunities and customer demands, while still adhering to strict banking regulations. The accelerated innovation cycle doesn't compromise mandatory controls because governance is embedded in the delivery pipeline. Bradesco's platform engineering team is now able to focus on strategic improvements rather than firefighting manual processes. The transformation turned infrastructure delivery from a bottleneck into a competitive advantage, enabling the bank to stay agile in a highly regulated industry.</p>