{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/infrastructure.write-iac/",
    "json": "https://www.anchorterminal.com/niches/infrastructure.write-iac/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/infrastructure.write-iac/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/infrastructure.write-iac/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 4 | 12 | 14 | 5 |\n\n## What counts as done\n\nCode that validates against the current provider schema with versions pinned, and a plan summarised by resource and action (create, change, destroy) before any apply.\n\nHow agents ask for it: write the Terraform for this; use the latest provider version; review this plan before apply; add Terraform tests\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **AWS MCP Servers (Amazon Web Services, Inc.)**: The IaC server validates CloudFormation with cfn-lint and cfn-guard and analyses failed deployments, but no change-set or plan summary by resource and action is documented; Terraform schemas are not served.\n- **Azure MCP Server (Microsoft Corporation)**: Azure Terraform tools return azurerm and AzAPI arguments and Azure Verified Module versions and validate a plan file against policy, but no plan summary by resource and action is documented, and tools were renamed in prereleases.\n- **neckbeard (David Beale (individual, GitHub account bealesh))**: Modules come from a catalogue pinned in a hash-verified lockfile, and validate runs static checks, a V1 plan stage and a V2 deploy stage, each reported; but no plan summary by resource and action is documented, and the project is pre-alpha.\n- **Terraform MCP Server (HashiCorp, Inc. (an IBM Company))**: get_latest_provider_version, get_provider_capabilities and get_provider_details give current schemas, and plans are separate from applies; but provider docs come back whole, and plan JSON is too large for context per acc-15. acc-14 recommends it for grounding.\n\n- not this job: Cloudflare CLI (cf) (Cloudflare, Inc.): Not an infrastructure-as-code tool; no provider schema, plan or apply step.\n- not this job: Cloudflare MCP Servers (Cloudflare, Inc.): No infrastructure-as-code, plan or provider schema tools.\n- not this job: DigitalOcean MCP Server (DigitalOcean, LLC): No infrastructure-as-code, plan or provider schema tools.\n- not this job: Netlify API + MCP (Netlify, Inc.): No infrastructure-as-code tooling.\n- not this job: Railway MCP Server (Railway Corporation): No infrastructure-as-code tooling.\n- not this job: Render MCP Server (Render Services, Inc.): No infrastructure-as-code tooling in the MCP server.\n\n## What stops agents finishing\n\n- plan JSON too large for the context\n- provider docs returned whole with no section fetch\n\n## Around it\n\nBefore: infrastructure.cloud-docs. After: infrastructure.change-live-resources, code.open-pr.\n\n## Where this comes from\n\nWeight 14 of 100 in Cloud \u0026 infrastructure: 5 of 32 accounts; two are feature requests on the Terraform MCP\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/infrastructure.write-iac.json, or the MCP tool get_use_case with id infrastructure.write-iac. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Write or review infrastructure as code",
        "url": ""
      }
    ],
    "description": "Write or review infrastructure as code: 0 companies fully do it, 4 with a limit, 12 carry the tag. Every listing in Cloud \u0026 infrastructure with the reason and a source.",
    "facts": null,
    "h1": "Write or review infrastructure as code",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/infrastructure.write-iac/",
    "published": "",
    "section": "agents",
    "title": "Write or review infrastructure as code: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/infrastructure.write-iac/"
  },
  "tokens": {
    "markdown": 950,
    "slim": 280
  },
  "version": 1
}
