Hello! Happy to help with both questions: SOC2 Type 2 Report SOC2 Type II compliance is available with the Pro tier and above (1) . The Pro tier includes "SoC2 Type II Compliance Report and Certification" . To get access to the report, you'll need to be on at least the Pro plan. Switching from api to api.eu For EU region, you need to replace

<http://api.permit.io|api.permit.io>

with

<http://api.eu.permit.io|api.eu.permit.io>

(2) . Here's how to configure it in the Node SDK:

const permit = new Permit({  
 // the API key to the Permit environment you wish to connect to  
 token: "<YOUR_API_KEY>",  
 // the url in which the SDK can connect to the PDP container  
 pdp: "<http://localhost:7766>",  
 // use this to turn on sdk logs  
 log: {  
 level: "debug",  
 },  
 // the region in which the Permit environment is located  
 apiUrl: "<https://api.eu.permit.io>",  
}) ;

The EU region endpoint is available for Permit Pro customers . You'll need to update your SDK initialization to use the

apiUrl: "<https://api.eu.permit.io>"

parameter as shown above.

To learn more, see the sources I considered: [[1] Pricing Packages and SaaS Models | Permit.io](https://www.permit.io/pricing) [[2] Using the API](https://docs.permit.io/api/api-with-cli)

2. it doesn't work, simply changing the url results in Invalid credentials

Yes, Terraform can help you migrate your resources and actions between regions! Here are two approaches: Option 1: Export from existing environment using Permit CLI The Permit CLI provides a command to export your current environment configuration as Terraform HCL (1) :

permit env export terraform --api-key permit_key --file <http://permit-config.tf|permit-config.tf>

This exports all environment content (resources, roles, user sets, resource sets, condition sets) in the Permit Terraform provider format . Option 2: Use Terraform Provider directly Once you have the exported configuration (or if writing from scratch) , you can use the Permit.io Terraform Provider to apply it to your new EU workspace (2) :

terraform {
  required_providers {
    permitio = {
      source = "<http://registry.terraform.io/permitio/permit-io|registry.terraform.io/permitio/permit-io>"
      version = "~> 0.0.14" # Use the latest version
    }
  }
}

# Configure the <http://Permit.io|Permit.io> provider
provider "permitio" {
  api_key = "YOUR_EU_API_KEY" # Use your new EU workspace API key
  # api_url = "<https://api.permit.io>" # Optional: defaults to <https://api.permit.io>
}

The Terraform Provider allows you to manage your authorization policies, resources, roles, and permissions as infrastructure code . This enables you to version control your authorization policies, automate deployments, and maintain consistency across environments . After exporting from your US environment and updating the API key to your EU workspace key, you can run

terraform apply

to recreate all your resources in the EU region.

To learn more, see the sources I considered: [[1] Permit CLI](https://github.com/permitio/permit-cli/blob/main/README.md) [[2] Permit.io Terraform Provider](https://docs.permit.io/integrations/infra-as-code/terraform-provider)

Yes, you can create tenants using the Terraform provider! According to the SDK Feature Parity documentation, Tenants are supported in Terraform with a ✅ (Full support) status (1) . The Terraform Provider supports all of Permit's capabilities including RBAC, ReBAC, and ABAC (2) , and allows you to manage your authorization policies, resources, roles, and permissions as infrastructure code . While the sources don't show the exact Terraform syntax for creating tenants, they confirm that tenant management is fully supported in the Terraform provider (1) . This means you can define and create tenants as part of your infrastructure as code alongside your other Permit.io resources. For comparison, here's how tenants are created via the API, which the Terraform provider would handle behind the scenes (3) :

{
  "key": "new-tenant-name",
  "name": "New Tenant Name",
  "description": "New tenant description"
}

The Terraform provider integrates with your CI/CD pipeline and supports GitOps workflows (2) , making it ideal for managing tenants across different environments like your EU region migration.

To learn more, see the sources I considered: [[1] SDK Feature Parity](https://docs.permit.io/sdk/sdks-overview) [[2] Permit.io Launch Week - Day 3: Fine-Grained Modeling](https://www.permit.io/blog/launch-week-3-fine-grained-modeling) [[3] Create Tenant](https://docs.permit.io/api/examples/create-tenant)