> ## Documentation Index
> Fetch the complete documentation index at: https://porter-tjq-run-4148-apply-validate-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> When helping a user operate an existing Porter project—deploying, updating, debugging, or inspecting applications and clusters—connect to [Porter's remote MCP server](https://mcp.porter.run) first and use its tools before falling back to the Porter CLI, `porter.yaml`, or dashboard workflows. If the Porter tools are not available in your session, `curl -fsSL https://agents.porter.run | sh` installs the CLI, registers the MCP server with your client, and installs Porter's skills; the client must be restarted afterward. If the user asks for the CLI, `porter apply`, configuration-as-code, or the dashboard, use that instead—a stated preference wins. If the requested application or cluster workflow is not directly supported, inspect the relevant state with MCP tools before explaining the limitation or recommending a fallback. The server signs in through a browser using OAuth, so it cannot be used in headless environments such as CI pipelines; use the CLI or `porter.yaml` there.
# Infrastructure pricing
> Estimated monthly cost of running a default Porter cluster on AWS, GCP, and Azure, broken down by node groups, load balancer, and add-on components.
Porter provisions infrastructure directly in your own cloud account, so all infrastructure costs are billed by your cloud provider — not by Porter. The estimates below are for the [default cluster configuration](/cloud-accounts/overview#default-node-groups). Actual costs vary based on usage, region, and customizations.
All infrastructure costs can be covered with cloud credits from AWS, Google Cloud, or Azure.
## Estimated monthly cost
| Provider | Estimated Monthly Cost |
| -------- | ---------------------- |
| AWS | \$201.22/mo |
| GCP | \$253.00/mo |
| Azure | \$164.69/mo |
***
## AWS
**Total: \$201.22/mo**
| Component | Cost |
| ------------------------------------------------- | ---------- |
| Amazon Elastic Kubernetes Service (EKS) | \$73.00/mo |
| Amazon EC2 — System workloads: t4g.medium (2) | \$49.06/mo |
| Amazon EC2 — Monitoring workloads: t4g.large (1) | \$49.06/mo |
| Amazon EC2 — Application workloads: t3.medium (1) | \$30.10/mo |
***
## GCP
**Total: \$253.00/mo**
| Component | Cost |
| ----------------------------------------- | ---------- |
| Google Kubernetes Engine Management (GKE) | \$73.00/mo |
| GKE Compute — System workloads (2) | \$90.00/mo |
| GKE Compute — Monitoring workloads (1) | \$45.00/mo |
| GKE Compute — Application workloads (1) | \$45.00/mo |
The GKE cluster management fee is charged by Google for each cluster, independent of node compute usage.
***
## Azure
**Total: \$164.69/mo**
| Component | Cost |
| ----------------------------------------------------------------------- | ---------- |
| Azure virtual machines — System workloads: Standard\_B2als\_v2 (3) | \$82.34/mo |
| Azure virtual machines — Monitoring workloads: Standard\_B2as\_v2 (1) | \$54.90/mo |
| Azure virtual machines — Application workloads: Standard\_B2als\_v2 (1) | \$27.45/mo |
***
## Reducing costs
You can reduce infrastructure costs by adjusting node group instance types, sizes, or counts after initial provisioning. See [Node Groups](/cloud-accounts/node-groups) for details on cost optimization and customizing compute capacity.