Skip to main content
IDYL accounts are global. A single account can manage members, profiles, namespaces, subnets, fleets, and workload access from one account context. Regions are where a subnet’s control plane is domiciled. When you create a subnet, you choose a region such as us-east or ca-west. Workloads deployed to that subnet are managed by that regional control plane; their actual execution happens on admitted data-plane capacity, which may be outside the region depending on the subnet’s provider capacity and admission policy.

​
What is global

Global services manage the account and the resources that define how the account is used. Use idyl whoami to see the current account, profile, namespace, and subnet selected by the CLI.

​
What is regional

Regional resources define where subnet control-plane state and workload orchestration live. They do not guarantee where data-plane nodes physically run. Create a subnet in a region:
List available regions:

​
Account deployment policy

Approving a subnet and enabling a region are separate account decisions. New workload creation requires both:
  • the subnet is approved for the account
  • the subnet’s region is enabled for the account
Disabling a region blocks new workload creation in subnets whose control plane is domiciled in that region. It does not delete existing workloads.

​
Choosing a region

Choose the region that matches the subnet’s control-plane, governance, and operational needs. After a subnet exists, target the subnet rather than the region when deploying workloads:
Regions are selected when creating subnets. Subnets are selected when running workloads. Data-plane locality is governed by the provider capacity admitted to the subnet, not by the region flag alone.