One license for your whole estate
Full Access covers every framework, bought on AWS Marketplace. Enterprise licenses your whole estate. Both start with a 30-day trial.
Where is your compliance work today?
Schedule of fees
- Between
- your org (you), with SOC 2 and CIS AWS v6.0 picked in this browser
- And
- compliance.tf, the Terraform control layer for AWS
Plans
Both plans serve the same terraform-aws-modules from the same private registry, with every framework enforced.
| Item | Full Access$1,000 a year | EnterpriseCustom |
|---|---|---|
| Frameworks | Every framework in the catalog | Every framework, plus custom frameworks and controls |
| Modules | terraform-aws-modules | terraform-aws-modules |
| Org console | Org endpoint, environments, snapshots, promotion log, members and tokens | The same, licensed for the estate: one baseline from one org endpoint |
| Registry access | No daily request limit | No daily request limit |
| Support | Email support | Priority support |
| How you buy | AWS Marketplace, on your AWS invoice | Talk to us |
| Action | Buy on AWS Marketplace | Talk to us |
The highlighted column is the plan that fits your compliance maturity.
Without a subscription after the trial, an account is on Free, at $0 with no card: module downloads cover CIS AWS v6.0 only (17 of 28 mapped controls enforced by modules), registry access has a daily request limit, and the org console tools lock. Deployed infrastructure is untouched.
Procurement reads this part.
Full Access is bought on AWS Marketplace, so it can ride an existing AWS agreement instead of a new vendor contract.
- SOC 2 Type II reportTrust Center
- Data processingDPA
- Uptime for paid subscribersSLA, 99.9% monthly
- Security overviewSecurity
Assurances about compliance.tf
Reports and terms
- SOC 2 Type II report, in the Trust Center.
- 99.9% monthly uptime for paid subscribers, under the SLA.
- A published DPA.
Where it runs
Infrastructure in two AWS regions: us-east-1 (US) and eu-west-1 (Ireland).
What stays yours
Your Terraform code, your state and your deployed resources. To leave, point the module sources back and re-plan.