// the find
hashicorp/terraform-cdk
Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
CDKTF let you write Terraform infrastructure in TypeScript, Python, Java, C#, or Go instead of HCL. HashiCorp archived it on December 10, 2025 after concluding it never found product-market fit at scale. The code is frozen — no more compatibility updates, no bug fixes.
The `cdktf synth --hcl` escape hatch is genuinely useful: it generates readable HCL from your existing CDKTF project, so migration is mechanical rather than a rewrite. The construct model mapped cleanly onto AWS CDK patterns, which made it approachable for teams already in that ecosystem. Multi-language support via jsii was technically impressive — one TypeScript implementation published bindings for five languages simultaneously.
It's dead. Archived, read-only, no compatibility updates as Terraform itself evolves — adopting it now means you're immediately on your own. The provider bindings were auto-generated and enormous (the AWS provider package alone was hundreds of megabytes), which made dependency installs slow and IDE tooling sluggish. The abstraction also leaked constantly: Terraform's token system and the CDK synthesis model didn't compose cleanly, so you'd end up debugging what HCL the synth actually produced rather than reasoning in your chosen language. HashiCorp's own admission that it 'did not find product-market fit at scale' is a fair summary of the core problem — most teams found raw HCL with modules less painful than fighting two abstraction layers.