Organizations and Environments
Organizations and environments define the two primary scopes in the AISIX Cloud control plane. The organization establishes ownership and shared administration. The environment establishes which AISIX gateways receive projected configuration.
This separation keeps account administration separate from traffic behavior. Members, billing, and provider credentials belong to the organization. Models, caller API keys, policies, and cache policies belong to the environment that serves traffic.
For live traffic, the environment is usually the scope that matters first. A saved environment resource affects live traffic only when it belongs to the environment attached to the target AISIX gateway.
Members, billing, shared administration, and provider credentials.
Holds resources for a development gateway.
Holds resources for a production gateway.
Scope Model
The AISIX Cloud control plane can manage more than one gateway and more than one set of gateway resources. Organizations and environments make it clear which team owns the deployment and which AISIX gateway receives each environment-scoped resource.
Organization Scope
An organization is the top-level ownership boundary. It is the scope for members, billing, shared administration, and provider credentials.
Use organization scope to reason about account ownership and shared administration. It is usually not the first scope to check when a saved gateway resource does not affect live traffic.
Environment Scope
An environment is the unit that groups gateway resources and projects them to the attached AISIX gateway or gateways.
Environment scope turns saved control-plane state into live gateway behavior. A resource can exist in the control plane and still not affect the gateway you are testing if it belongs to another environment.
When a resource does not affect traffic as expected, confirm first that the resource belongs to the same environment as the target AISIX gateway. For provider keys, also confirm that the provider key is allowed in that environment.
Create or Select an Environment
Open Environments in the dashboard. If your account does not belong to an organization yet, the dashboard first prompts you to create one.
To create an environment, select New environment, enter a display name, and select Create environment. The confirmation shows the environment ID and links to its Data planes view. Copy the ID for provider setup examples, which use it as ENV_ID.
To use an existing environment, select it from the environment list. The environment ID appears below its display name.
Next Steps
Continue with Admin Tokens to create the organization-scoped credential used by the provider setup examples. After creating a token, connect an AISIX gateway to the environment that should receive the configuration.