Crossplane vs Terraform
Terraform is a mature, portable CLI tool with explicit plan/apply and the largest ecosystem, but no continuous reconciliation. Crossplane manages infrastructure as Kubernetes resources with continuous drift correction and composable platform APIs, requiring a cluster. Choose by operating model.
Overview
Crossplane and Terraform both provision and manage cloud infrastructure, but they operate on very different models. Terraform is a standalone tool driven by a CLI, using declarative HCL with an explicit plan-and-apply workflow. Crossplane turns a Kubernetes cluster into a control plane for infrastructure, managing resources as Kubernetes objects that are continuously reconciled. The choice reflects whether you want a CLI-based tool or a Kubernetes-native control plane.
Key Differences
Terraform runs as a single binary anywhere, computing a plan and applying changes when you invoke it. It is mature, with the largest provider and module ecosystem in IaC, and fits naturally into any CI/CD pipeline. Drift can be detected when you run a plan, but Terraform does not continuously enforce desired state on its own; correcting drift requires running apply again. This explicit, on-demand model is predictable and widely understood.
Crossplane embeds infrastructure management into Kubernetes. Cloud resources are represented as custom Kubernetes resources, and Crossplane's controllers continuously reconcile actual state toward the declared state, automatically correcting drift the way Kubernetes does for pods. A powerful feature is composition: platform teams can define composite resources that bundle infrastructure into custom, higher-level APIs, enabling developer self-service through familiar Kubernetes interfaces. This makes Crossplane a strong foundation for internal developer platforms. The prerequisite is a Kubernetes cluster to host the control plane, and the ecosystem, while growing, is younger than Terraform's.
In essence, Terraform is a mature, portable, on-demand tool, while Crossplane is a continuously reconciling, Kubernetes-native control plane with custom platform APIs.
When to Choose Crossplane
Choose Crossplane when you want infrastructure managed through the Kubernetes API with continuous reconciliation and automatic drift correction. It excels for teams building internal developer platforms that expose self-service, composable APIs, and for organizations already standardized on Kubernetes and GitOps.
When to Choose Terraform
Choose Terraform when you want a mature, standalone tool with the broadest provider ecosystem and no requirement for a Kubernetes cluster. Its explicit plan-and-apply workflow is predictable and works in any pipeline, making it the safer default for most general infrastructure provisioning.
Verdict
Terraform remains the mainstream, portable choice with unmatched ecosystem breadth and a simple, explicit workflow. Crossplane is compelling when you want continuous reconciliation and a Kubernetes-native control plane that powers self-service platform APIs. Some organizations even use Crossplane to manage Terraform or run both, applying Crossplane for platform abstractions and Terraform for broad provisioning. Choose based on whether a Kubernetes-native, continuously reconciling model fits your operating approach.