IMCLZ compared with the alternatives
Infinitech LLC · Comparison note · November 2026
IMCLZ is for organizations that vend scopes in two or more of AWS, Azure, Google Cloud, and OCI and want one request format, one policy check before anything is created, and one evidence trail across them. If you run one cloud, the provider's own landing zone is free and you should start there; Infinitech also implements Control Tower, LZA, and Azure Landing Zones.
Side by side
| What it is | Clouds | Check before anything is created | Government regions | Price | Best fit | |
|---|---|---|---|---|---|---|
| IMCLZ | Terraform delivered into your repository, handed over by Infinitech | AWS, Azure, Google Cloud, OCI | OPA policy on every saved Terraform plan | GovCloud account pairs built; first live run in your environment. Azure Government, OCI Gov, Assured Workloads planned | Fixed fee. Launch prices: USD 28,875 for two clouds, discovery USD 4,200, USD 8,750 per added cloud | Two or more of the four clouds |
| AWS Control Tower (+ AFT) | Managed AWS service | AWS | SCPs at the OU; AFT can export a plan for review | Runs in GovCloud; can't create GovCloud accounts there | No charge; pay for the services it sets up | AWS only |
| Landing Zone Accelerator | Open-source AWS solution (CDK) | AWS | Config-driven SCPs and guardrails | GovCloud, Secret, Top Secret; FedRAMP, CMMC, NIST 800-171 configurations | Free; about USD 430 a month in AWS charges for AWS's sample setup | Federal work on AWS only |
| Azure Landing Zones | Microsoft accelerator (Terraform or Bicep) | Azure | Azure Policy at the management group | Not out of the box in Azure Government; Mission Landing Zone covers it | Free; pay for Azure resources | Azure only |
| Gruntwork | Subscription: module library, Pipelines, Account Factory | AWS, Azure, Google Cloud (account, subscription, and project vending) | Terragrunt plans in pull requests; OPA (Conftest) plan checks as an Enterprise hook, in beta | Modules deploy in GovCloud; Gruntwork holds no FedRAMP authorization | Team and Enterprise plans, quoted | A maintained module library and subscription service |
| Spacelift | IaC orchestration (SaaS or self-hosted) | Any | OPA policies | FedRAMP Moderate edition | Free tier; paid from USD 399 a month | Running Terraform you already have |
| HCP Terraform | HashiCorp's Terraform service | Any | Sentinel, OPA, Terraform policy | Not checked | Per managed resource | Teams standardized on Terraform |
IMCLZ's prices are launch prices for the first two Foundations, given in exchange for a reference: each is its estimated ceiling hours at USD 175 (165 h for the Foundation, 24 h for its discovery, 50 h for each cloud past two). Discovery is credited in full if you sign the Foundation within 60 days.
Sources and read dates for every non-IMCLZ cell are in the Infinitech claim matrix; each vendor's own page is the authority.
If you run one cloud
Infinitech implements the provider's own landing zone for a fixed fee. These are launch prices and estimates, ±30%: each is its estimated hours at USD 175, corrected once that service has been run end to end in Infinitech's accounts. A free 30-minute scoping call picks the tier. Paid discovery comes next, and its fee is credited in full to the build if you sign the build within 60 days.
| Service | Discovery | Fee | Run cost the provider estimates for the idle landing zone |
|---|---|---|---|
| Control Tower Essentials | USD 2,100 | USD 12,600 | Near zero; AWS's 10-account example bills USD 3.75 a month in AWS Config |
| Control Tower Standard, with Account Factory for Terraform | USD 2,800 | USD 22,225 | As Essentials |
| Landing Zone Accelerator, commercial regions | USD 4,200 | USD 25,200 | About USD 430 a month for AWS's sample setup |
| LZA in GovCloud: LZA plus GovCloud account pairs, AWS's GovCloud sample configuration, FIPS endpoints, and the first live GovCloud run, in your environment | USD 7,000 | Scoped after discovery; no live GovCloud run yet to price from | AWS's estimate covers us-east-1 only |
| Azure Landing Zones Essentials, small-business single region | USD 2,450 | USD 17,150 | About USD 690 a month |
| Azure Landing Zones Standard, single-region hub and spoke with Azure Firewall | USD 3,500 | USD 22,575 | About USD 5,640 a month |
| Azure Government: the Azure Landing Zones scope above, with the accelerator's code changed by hand, because Microsoft doesn't support its deployment there | USD 7,000 | Scoped after discovery, which sizes those changes | Microsoft's estimates are for westus |
Essentials is the starting point for a regulated buyer: one cloud now, with IMCLZ for more clouds or IRDP for a regulated data platform later. Fees don't include identity-provider, workload, or data migration, audit preparation, 24x7 operations, or the cloud bill. An existing AWS account that already has an AWS Config recorder needs AWS Support to allow-list it before Control Tower enrolls it, so it's quoted per account.
If you already run Control Tower or LZA
IMCLZ creates AWS accounts through AWS Organizations and gives each one its own baseline: an AWS Config recorder and delivery channel, GuardDuty, and Security Hub. Control Tower's standard enrollment expects an account with no AWS Config recorder. An account that has one, as IMCLZ-vended accounts do, needs AWS Support to allow-list it and its Config resources changed, and is then enrolled by re-registering its OU; the per-account Enroll account workflow and auto-enrollment don't apply. Until IMCLZ can enroll accounts itself (planned), that step is manual. Your OU's SCPs apply either way.
If you'd rather not do that per account, keep Account Factory, AFT, or LZA for AWS accounts and use IMCLZ for Azure, Google Cloud, and OCI, with the same request format and OPA policy for the Terraform you run in AWS.
If you already run Azure Landing Zones
They fit together. Azure Landing Zones build the management-group hierarchy and platform subscriptions. IMCLZ vends application subscriptions into a management group you name and adds its tags, policy assignment, Defender plan, and diagnostic settings to each one. Name the Azure Landing Zones "landing zones" management group as the target and both sets of Azure Policy apply.
If you already run Spacelift, HCP Terraform, env zero, or Scalr
Keep it for runs, state, approvals, and access control. IMCLZ's request schema and generator, its per-cloud modules, and its Rego rules carry over; its GitHub Actions plan, apply, and drift workflows are what the platform replaces. Each platform hands the plan to OPA in its own input document, so the rules need a small adapter, and HCP Terraform's tfpolicy language is HCL, so Rego rules would be rewritten for it. That adaptation is scoped in discovery; no platform integration ships with IMCLZ today.
If you're looking at Gruntwork
Gruntwork is the closest alternative: both hand you landing-zone code authored for you, and both vend scopes on AWS, Azure, and Google Cloud. Gruntwork sells a subscription to a maintained module library and its Pipelines service. Its pricing FAQ says Pipelines access ends when the subscription does, and Team-plan library modules need a buyout to keep using them. Its OPA plan check is an Enterprise hook in beta. IMCLZ is a fixed-fee engagement with no runtime of its own after handoff, also covers OCI, and includes the OPA plan gate in every delivery.
Government regions and approvals
GovCloud account-pair vending is built and tested with mocks. Its first live run happens in your GovCloud environment during the engagement, with access you grant. Azure Government, OCI US Government Cloud, and Google Assured Workloads are planned, not available.
IMCLZ uses separate plan and apply identities. In Infinitech's demo repository one operator dispatches both steps, because that repository's GitHub plan has no required reviewers for private environments. If your GitHub plan has them, the apply step can require a second approver.
Questions: hello@infinitechplatforms.com.