Compliance as code

Joopler is deployable and manageable as code, so getting to green is terraform apply and staying green is drift-detected like the rest of your infrastructure.

Baseline modules

Published Terraform modules deploy the security baseline Joopler continuously verifies, one per platform:

• AWS
• Azure
• GCP
• VMware vSphere
• A self-hostable AI egress gateway for your own network

Each resource maps to the control it satisfies, so deploy-as-code and verify-as-code stay paired. The modules are published to the public Terraform Registry under the joopler namespace, for example joopler/baseline/aws.

The Terraform provider

The joopler provider manages the scaffolding of your program as code: connectors, control and policy ownership, vendors and subprocessors, the audit target, and framework scope.

Browse it on the Terraform Registry: registry.terraform.io/providers/joopler/joopler. Pin it in your configuration:

terraform {
  required_providers {
    joopler = {
      source = "joopler/joopler"
    }
  }
}

By design, the provider cannot sign off on policies or attest evidence. Those are human acts. Terraform owns the structure of your program; a human owns the claims. Both stay auditable, the structure as code and the sign-offs as signed ledger records.

See the API for the underlying write surface.