Prompt
Can you help me choose an infrastructure as code tool for multi-cloud with drift detection and policy enforcement?
Latest observation
Yes — for multi-cloud + drift detection + policy enforcement, the best choice depends on how much you want managed workflow, open source, and policy-as-code depth.
Quick recommendation
If you want a strong default:
- Terraform + a policy layer is the most common and broadly supported choice.
- Add Terraform Cloud/Enterprise or Spacelift for:
- drift detection
- policy enforcement
- approvals / workflow controls
If you want a more Kubernetes-native / GitOps-style approach:
- Crossplane is strong for managing cloud resources from Kubernetes
- but drift detection and policy enforcement usually require more platform engineering effort.
If you want cloud-agnostic but simpler and developer-friendly:
- Pulumi is excellent for multi-cloud and general-purpose programming languages
- policy support exists, but ecosystem maturity for enterprise governance is usually strongest around Terraform.
Best options by category
1) Terraform
Best for: broadest multi-cloud support, largest ecosystem, easiest hiring/support
Pros
- Mature support for AWS, Azure, GCP, and many SaaS providers
- Huge module ecosystem
- Strong state-based workflow
- Good integrations for drift detection and policy enforcement via:
- Terraform Cloud / Enterprise
- Spacelift
- Atlantis + OPA/Conftest
- Checkov / tfsec / Sentinel
Cons
- State management adds operational complexity
- HCL is specialized
- Native drift detection is not enough by itself in many setups; better with a platform
Policy enforcement
- HashiCorp Sentinel in Terraform Cloud/Enterprise
- OPA / Conftest
- Checkov, tfsec, TFLint for static checks
Drift detection
- Terraform plan can detect drift when run regularly
- Better with scheduled plans in Terraform Cloud/Enterprise or Spacelift
2) Pulumi
Best for: teams that prefer real programming languages and want multi-cloud flexibility
Pros
- Use TypeScript, Python, Go, C#, Java
- Great for complex logic and reusable abstractions
- Works across major clouds
- Easier for dev teams who dislike HCL
Cons
- Smaller ecosystem than Terraform
- Governance/policy workflows are good, but usually less standardized than Terraform in enterprise environments
- Fewer off-the-shelf modules compared to Terraform
Policy enforcement
- Pulumi CrossGuard
- OPA-style policies possible depending on workflow
Drift detection
- Supports refresh/preview workflows, but platform integration matters
3) Crossplane
Best for: Kubernetes-centered platform teams building an internal platform
Pros
- Uses Kubernetes APIs and controllers
- Good for multi-cloud resource management
- GitOps-friendly
- Strong abstraction model for platform teams
Cons
- Steeper learning curve
- More operational overhead
- Drift detection/policy enforcement require more custom platform design
- Less ideal if you want a quick, straightforward IaC standard for all teams
Policy enforcement
- Usually via Kubernetes admission control / Kyverno / OPA Gatekeeper
- Works well in a Kubernetes governance model
4) AWS CloudFormation / Azure Bicep / Google Config Connector
Best for: single-cloud or cloud-specific teams
Pros
- Native to each cloud
- Deep integration with provider services
Cons
- Not multi-cloud
- Fragmented tooling and workflows
What I’d choose in practice
Option A: Most enterprise teams
Terraform + Terraform Cloud/Enterprise
- Best overall balance for multi-cloud
- Built-in workflow controls
- Drift detection via scheduled runs
- Policy enforcement via Sentinel and/or OPA
Option B: Open-source / platform-neutral
Terraform + Spacelift
or
Terraform + Atlantis + OPA/Conftest
- Good if you want more control and less vendor lock-in than Terraform Cloud
Option C: Developer-centric
Pulumi + policy tooling
- Great if your team is strong in Python/TypeScript/Go
- Good for complex infra logic
Option D: Platform engineering / GitOps
Crossplane + Kyverno/Gatekeeper
- Best if your org already runs Kubernetes as the control plane
Decision checklist
Choose Terraform if you need:
- strongest multi-cloud ecosystem
- many providers/modules
- easiest hiring and community support
- mature drift detection + policy stack
Choose Pulumi if you need:
- real programming languages
- more expressive code for complex infra
- developer-friendly abstractions
Choose Crossplane if you need:
- Kubernetes-based control plane
- GitOps-native infrastructure management
- platform-team ownership of infra APIs
My practical recommendation
If your requirements are specifically:
- multi-cloud
- drift detection
- policy enforcement
then I’d start with:
Terraform + Terraform Cloud/Enterprise
or
Terraform + Spacelift
That is the most proven combination for governance-heavy environments.
If you want, I can also give you:
- a side-by-side comparison table,
- a recommendation based on your team size and stack, or
- a shortlist of tools by budget / compliance level.