> ## Documentation Index
> Fetch the complete documentation index at: https://cdktn.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# CDK Terrain
> CDK Terrain (CDKTN) lets you use familiar programming languages to define and provision infrastructure.
export const PlatformDiagram = () => {
return ;
};
CDK Terrain (CDKTN) allows you to use familiar programming languages to define and provision infrastructure. CDKTN works with both Terraform and [OpenTofu](https://opentofu.org/). This gives you access to the entire Terraform ecosystem without learning HashiCorp Configuration Language (HCL) and lets you leverage the power of your existing toolchain for testing, dependency management, etc.
We support TypeScript, Python, Java, C#, and Go.
## How does CDK Terrain work?
CDK Terrain leverages concepts and libraries from the [AWS Cloud Development Kit](https://aws.amazon.com/cdk/) to translate your code into infrastructure configuration files for Terraform.
At a high level, you will:
1. **Create an Application:** Use either a built-in or a custom template to scaffold a project in your chosen language.
2. **Define Infrastructure:** Use your chosen language to define the infrastructure you want to provision on one or more providers. CDKTN automatically extracts the schema from Terraform providers and modules to generate the necessary classes for your application.
3. **Deploy**: Use `cdktn` CLI commands to provision infrastructure with Terraform or OpenTofu, or synthesize your code into a JSON configuration file that others can use with Terraform directly.
You can use every Terraform provider and module available on the [Terraform Registry](https://registry.terraform.io/) or the [OpenTofu Registry](https://search.opentofu.org/), and you can use CDKTN with [Atlantis](https://www.runatlantis.io/docs/custom-workflows.html#cdktf) with policy as code such as [Conftest](https://www.runatlantis.io/docs/policy-checking.html) or
even with Hashicorp offerings such as [HCP Terraform](https://cloud.hashicorp.com/products/terraform), [Terraform Enterprise](https://developer.hashicorp.com/terraform/enterprise), and any[Sentinel](https://www.hashicorp.com/sentinel).
## When to use CDK Terrain
CDKTN offers many benefits, but it is not the right choice for every project. You should consider using CDKTN when:
* You have a strong preference or need to use a procedural language to define infrastructure.
* You need to create abstractions to help manage complexity. For example, you want to create constructs to model a reusable infrastructure pattern composed of multiple resources and convenience methods.
* You are comfortable living on the cutting edge; CDKTN may still have breaking changes before our 1.0 release.
You can make this choice for each team and project because CDK Terrain [interoperates with existing Terraform providers and modules](/concepts/hcl-interoperability).
## Choosing a Language for your Project
Consider which of the supported languages you are most familiar with and which language best fits your organization's current tooling. We work towards providing feature parity and a good user experience across all supported languages, but there may be instances when new experimental features will not be available for all languages.
If you plan to create and package your own constructs, we recommend choosing TypeScript. Using TypeScript allows you to use the [cdktn constructs](https://github.com/projen/projen#getting-started) package generator to build and publish your constructs in multiple languages.
## Get Started
* [Install CDKTN](/tutorials/install) and set up your first project.
* Learn about [CDKTN application architecture](/concepts/cdktn-architecture).
* Learn how to use key CDKTN concepts like [providers](/concepts/providers), [modules](/concepts/modules), and [resources](/concepts/resources) to define infrastructure.