An IaC (Infrastructure-as-Code) resource represents an actual piece of infrastructure—such as a Kubernetes namespace, an AWS VPC, or a managed database instance—provisioned and managed through Planton Cloud’s platform. Just like Pulumi, Planton Cloud uses modules (Pulumi, Terraform) to define what will be deployed. When you run a deployment, these modules create underlying cloud resources. Each of these underlying resources counts as a single IaC resource in your organization’s usage.

In other words, IaC resources are a direct reflection of real infrastructure elements running in your environments. If you deploy a Redis service on Kubernetes, every resulting API object—config maps, services, deployments, ingresses—counts as one IaC resource each. Unlike some platforms, Planton Cloud doesn’t inflate resource counts or create “filler” components. We only count what’s truly needed for your deployments, and you have full control: the complexity and quantity of resources depend entirely on the infrastructure you choose to define and deploy.

This approach makes IaC resources a meaningful metric for understanding how much infrastructure you’re operating and the value you’re getting from Planton Cloud. It also ensures a straightforward comparison to the Pulumi model—every Planton Cloud deployment maps cleanly to a Pulumi stack, and every cloud object created within that stack maps to a countable IaC resource.

An IaC (Infrastructure-as-Code) resource represents an actual piece of infrastructure—such as a Kubernetes namespace, an AWS VPC, or a managed database instance—provisioned and managed through Planton Cloud’s platform. Just like Pulumi, Planton Cloud uses modules (Pulumi, Terraform) to define what will be deployed. When you run a deployment, these modules create underlying cloud resources. Each of these underlying resources counts as a single IaC resource in your organization’s usage.

In other words, IaC resources are a direct reflection of real infrastructure elements running in your environments. If you deploy a Redis service on Kubernetes, every resulting API object—config maps, services, deployments, ingresses—counts as one IaC resource each. Unlike some platforms, Planton Cloud doesn’t inflate resource counts or create “filler” components. We only count what’s truly needed for your deployments, and you have full control: the complexity and quantity of resources depend entirely on the infrastructure you choose to define and deploy.

This approach makes IaC resources a meaningful metric for understanding how much infrastructure you’re operating and the value you’re getting from Planton Cloud. It also ensures a straightforward comparison to the Pulumi model—every Planton Cloud deployment maps cleanly to a Pulumi stack, and every cloud object created within that stack maps to a countable IaC resource.

An IaC (Infrastructure-as-Code) resource represents an actual piece of infrastructure—such as a Kubernetes namespace, an AWS VPC, or a managed database instance—provisioned and managed through Planton Cloud’s platform. Just like Pulumi, Planton Cloud uses modules (Pulumi, Terraform) to define what will be deployed. When you run a deployment, these modules create underlying cloud resources. Each of these underlying resources counts as a single IaC resource in your organization’s usage.

In other words, IaC resources are a direct reflection of real infrastructure elements running in your environments. If you deploy a Redis service on Kubernetes, every resulting API object—config maps, services, deployments, ingresses—counts as one IaC resource each. Unlike some platforms, Planton Cloud doesn’t inflate resource counts or create “filler” components. We only count what’s truly needed for your deployments, and you have full control: the complexity and quantity of resources depend entirely on the infrastructure you choose to define and deploy.

This approach makes IaC resources a meaningful metric for understanding how much infrastructure you’re operating and the value you’re getting from Planton Cloud. It also ensures a straightforward comparison to the Pulumi model—every Planton Cloud deployment maps cleanly to a Pulumi stack, and every cloud object created within that stack maps to a countable IaC resource.

An IaC (Infrastructure-as-Code) resource represents an actual piece of infrastructure—such as a Kubernetes namespace, an AWS VPC, or a managed database instance—provisioned and managed through Planton Cloud’s platform. Just like Pulumi, Planton Cloud uses modules (Pulumi, Terraform) to define what will be deployed. When you run a deployment, these modules create underlying cloud resources. Each of these underlying resources counts as a single IaC resource in your organization’s usage.

In other words, IaC resources are a direct reflection of real infrastructure elements running in your environments. If you deploy a Redis service on Kubernetes, every resulting API object—config maps, services, deployments, ingresses—counts as one IaC resource each. Unlike some platforms, Planton Cloud doesn’t inflate resource counts or create “filler” components. We only count what’s truly needed for your deployments, and you have full control: the complexity and quantity of resources depend entirely on the infrastructure you choose to define and deploy.

This approach makes IaC resources a meaningful metric for understanding how much infrastructure you’re operating and the value you’re getting from Planton Cloud. It also ensures a straightforward comparison to the Pulumi model—every Planton Cloud deployment maps cleanly to a Pulumi stack, and every cloud object created within that stack maps to a countable IaC resource.

An IaC (Infrastructure-as-Code) resource represents an actual piece of infrastructure—such as a Kubernetes namespace, an AWS VPC, or a managed database instance—provisioned and managed through Planton Cloud’s platform. Just like Pulumi, Planton Cloud uses modules (Pulumi, Terraform) to define what will be deployed. When you run a deployment, these modules create underlying cloud resources. Each of these underlying resources counts as a single IaC resource in your organization’s usage.

In other words, IaC resources are a direct reflection of real infrastructure elements running in your environments. If you deploy a Redis service on Kubernetes, every resulting API object—config maps, services, deployments, ingresses—counts as one IaC resource each. Unlike some platforms, Planton Cloud doesn’t inflate resource counts or create “filler” components. We only count what’s truly needed for your deployments, and you have full control: the complexity and quantity of resources depend entirely on the infrastructure you choose to define and deploy.

This approach makes IaC resources a meaningful metric for understanding how much infrastructure you’re operating and the value you’re getting from Planton Cloud. It also ensures a straightforward comparison to the Pulumi model—every Planton Cloud deployment maps cleanly to a Pulumi stack, and every cloud object created within that stack maps to a countable IaC resource.

An IaC (Infrastructure-as-Code) resource represents an actual piece of infrastructure—such as a Kubernetes namespace, an AWS VPC, or a managed database instance—provisioned and managed through Planton Cloud’s platform. Just like Pulumi, Planton Cloud uses modules (Pulumi, Terraform) to define what will be deployed. When you run a deployment, these modules create underlying cloud resources. Each of these underlying resources counts as a single IaC resource in your organization’s usage.

In other words, IaC resources are a direct reflection of real infrastructure elements running in your environments. If you deploy a Redis service on Kubernetes, every resulting API object—config maps, services, deployments, ingresses—counts as one IaC resource each. Unlike some platforms, Planton Cloud doesn’t inflate resource counts or create “filler” components. We only count what’s truly needed for your deployments, and you have full control: the complexity and quantity of resources depend entirely on the infrastructure you choose to define and deploy.

This approach makes IaC resources a meaningful metric for understanding how much infrastructure you’re operating and the value you’re getting from Planton Cloud. It also ensures a straightforward comparison to the Pulumi model—every Planton Cloud deployment maps cleanly to a Pulumi stack, and every cloud object created within that stack maps to a countable IaC resource.