# mulesoft Anypoint Platform Control Planes - Full Documentation --- product: Anypoint Platform Control Planes --- # Anypoint Platform Control Planes Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Platform control planes are the MuleSoft-managed environments where you design, deploy, and manage APIs and Mule apps. Each Anypoint Platform organization lives in exactly one cloud. Sign in to that control plane and deploy Mule apps to the runtime planes it supports. For the full catalog of control planes (including MuleSoft Government Cloud and Anypoint Platform Private Cloud Edition (PCE)) and the control plane and runtime compatibility matrix, see [Anypoint Platform Hosting Overview](https://docs.mulesoft.com/hosting-home/). ## Control Plane Clouds MuleSoft hosts a control plane in each supported geography and names that regional control plane a cloud, for example US Cloud or EU Cloud. US Cloud is the US control plane. EU Cloud is the EU control plane. _Cloud_ is the product name of that isolated Anypoint Platform instance (login URL, organization, and data residency). _Control plane_ is the management layer in that instance, as distinct from the [runtime plane](https://docs.mulesoft.com/hosting-home/#control-plane-and-runtime-plane), where apps run. You choose one cloud for your organization. You don’t choose a cloud and a control plane as two separate products. - To create and deploy a Mule app, see [Creating and Deploying Mule Apps](https://docs.mulesoft.com/control-planes/creating-and-deploying-mule-apps). - If you host Mule, or the app must use API gateway on a non-US Cloud, also see [Control Plane Hostnames and Allowlists](https://docs.mulesoft.com/control-planes/control-plane-hostnames-allowlists) and [Configuring Mule to Access Anypoint Platform Control Planes](https://docs.mulesoft.com/control-planes/configuring-mule-control-planes). For data residency and compliance notes for each control plane, see [Control Plane Hosting Options](https://docs.mulesoft.com/hosting-home/#control-plane-hosting-options). ## Sign In to the Control Plane Sign in to the Anypoint Platform control plane that holds your organization. Use the platform URL for that cloud. Organizations and user accounts are not shared across clouds. MuleSoft adds new regional clouds over time. 1. Go to the platform URL for your cloud:
Geographic RegionControl PlanePlatform URL

Americas

US Cloud

https://anypoint.mulesoft.com

Canada Cloud

https://ca1.platform.mulesoft.com

Europe

EU Cloud

https://eu1.anypoint.mulesoft.com

United Kingdom Cloud

https://gb1.platform.mulesoft.com

Asia Pacific

Japan Cloud

https://jp1.platform.mulesoft.com

India Cloud

https://in1.platform.mulesoft.com

Australia Cloud

https://au1.platform.mulesoft.com

2. If you don’t have an account in that cloud, click **Sign Up** and create one. 3. Enter your username and password, then click **Sign In**. To sign in from Anypoint Studio, the Anypoint Code Builder desktop IDE, Anypoint CLI, or Maven, configure that product to use the same control plane as your organization: - [Configure Anypoint Studio for Control Planes](https://docs.mulesoft.com/studio/hyperforce-configuration) - [Configure Anypoint Code Builder for Control Plane](https://docs.mulesoft.com/anypoint-code-builder/start-acb#change-clouds) - [Configure Anypoint CLI for Control Plane](https://docs.mulesoft.com/anypoint-cli/latest/#default-options) - [Publish an Asset to Exchange Using Maven](https://docs.mulesoft.com/exchange/to-publish-assets-maven#publish-an-asset-to-exchange-using-maven) ## Runtime Planes and Feature Availability - Runtime plane support varies by control plane. See the [control plane and runtime plane compatibility matrix](https://docs.mulesoft.com/hosting-home/#support-matrix-control-plane), then [Creating and Deploying Mule Apps](https://docs.mulesoft.com/control-planes/creating-and-deploying-mule-apps). - Object Store capabilities vary by control plane. See [Object Store Features by Control Plane](https://docs.mulesoft.com/object-store/#os-features-control-plane). - MuleSoft product features vary by control plane. See [MuleSoft product features by Control Plane](https://docs.mulesoft.com/hyperforce/#features-supported-on-hyperforce). ## See Also - [Creating and Deploying Mule Apps](https://docs.mulesoft.com/control-planes/creating-and-deploying-mule-apps) - [Control Plane Hostnames and Allowlists](https://docs.mulesoft.com/control-planes/control-plane-hostnames-allowlists) - [Configuring Mule to Access Anypoint Platform Control Planes](https://docs.mulesoft.com/control-planes/configuring-mule-control-planes) - [Anypoint Platform Hosting Overview](https://docs.mulesoft.com/hosting-home/) - [Salesforce Hyperforce Overview](https://docs.mulesoft.com/hyperforce/) --- product: Anypoint Platform Control Planes --- # Configuring Mule to Access Anypoint Platform Control Planes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt A running Mule runtime engine (Mule) instance must know which Anypoint Platform control plane holds your organization. Mule uses that connection for API gateway and, on Hybrid Standalone, for the Runtime Manager agent. Mule connects to the US Cloud control plane by default. If your organization is in any other cloud, set `anypoint.platform.base_uri`, `anypoint.platform.analytics_base_uri`, and the [client ID and client secret](https://docs.mulesoft.com/access-management/managing-business-groups#client-id-and-secret) of the environment. You don’t do this before you create your first Mule app. Design the app in Anypoint Studio or Anypoint Code Builder; those IDEs don’t use these properties. Set them when you install and register a Hybrid Standalone instance, or when you deploy an app to CloudHub or CloudHub 2.0 that must use API gateway with a non-US Cloud control plane. If you leave the defaults, API gateway on Mule is disabled in those clouds. ## When to Configure Mule
RuntimeWhen to set anypoint.platform.base_uri and related propertiesWhy

CloudHub or CloudHub 2.0

When you deploy the app, in the Properties tab in Runtime Manager, if the app must use API gateway with a non-US Cloud control plane. See Configuring App Properties in Runtime Manager.

MuleSoft hosts Mule in that control plane. You don’t install it. Set these properties only if that app uses API gateway and your organization is not on US Cloud. Hosted Mule still defaults to US Cloud for the gateway connection.

Hybrid Standalone

When you install and register Mule, before you deploy apps onto that server. See Configuring a Hybrid Standalone Instance.

You host Mule. The instance cannot reach your organization until you point it at the same control plane and register the Runtime Manager agent. See Setting up Hybrid Standalone Instances.

Runtime Fabric

Don’t set anypoint.platform.base_uri, anypoint.platform.analytics_base_uri, or the client ID and client secret on Mule

The fabric connects to the control plane when you install it. Configure network access for the cluster instead of setting anypoint.platform.base_uri on each Mule. See Configuring Your Network to Support Runtime Fabric.

On-premises (not registered to Runtime Manager)

Don’t set anypoint.platform.base_uri, anypoint.platform.analytics_base_uri, or the client ID and client secret

Unregistered Mule doesn’t connect to a control plane, so anypoint.platform.base_uri has no effect. See Run Mule Runtime Engine On-Premises.

For the `base_uri` and `analytics_base_uri` values, prefix the Anypoint Platform URL and Analytics ingest hostname for your cloud with `https://`. See [Control Plane Hostnames and Allowlists](https://docs.mulesoft.com/control-planes/control-plane-hostnames-allowlists). ## Configuring a Hybrid Standalone Instance For Hybrid Standalone, set these properties on the Mule instance you installed, then register the server. See [Creating Servers](https://docs.mulesoft.com/hybrid-standalone/creating-servers). ### Configuring Mule Properties in the Wrapper.conf File To configure Mule in the `wrapper.conf` file, modify these properties, replacing `` with an integer value that is unique within `wrapper.conf`. Use `https://` plus the Platform URL and Analytics ingest hostname for your cloud. This example shows the `wrapper.conf` configuration for Canada Cloud: wrapper.java.additional.=-Danypoint.platform.client\_id= wrapper.java.additional.=-Danypoint.platform.client\_secret= wrapper.java.additional.=-Danypoint.platform.base\_uri=https://ca1.platform.mulesoft.com wrapper.java.additional.=-Danypoint.platform.analytics\_base\_uri=https://analytics-ingest.ca1.platform.mulesoft.com ### Configuring Mule Properties via the Command Line To configure Mule from the command line, pass these options when you start Mule. The `./` prefix applies only to Unix environments. Use `https://` plus the Platform URL and Analytics ingest hostname for your cloud. This example shows the command-line configuration for EU Cloud: ./mule -M-Danypoint.platform.client\_id= -M-Danypoint.platform.client\_secret= -M-Danypoint.platform.base\_uri=https://eu1.anypoint.mulesoft.com -M-Danypoint.platform.analytics\_base\_uri=https://analytics-ingest.eu1.anypoint.mulesoft.com ## Configuring App Properties in Runtime Manager When you deploy to CloudHub 2.0, or to CloudHub from US Cloud or EU Cloud, include these properties in the **Properties** tab in Runtime Manager if the app must use API gateway with that control plane. Use `https://` plus the Platform URL and Analytics ingest hostname for your cloud. This example shows the properties configuration for Japan Cloud: anypoint.platform.client\_id= anypoint.platform.client\_secret= anypoint.platform.base\_uri=https://jp1.platform.mulesoft.com anypoint.platform.analytics\_base\_uri=https://analytics-ingest.jp1.platform.mulesoft.com ## See Also - [Anypoint Platform Control Planes Overview](https://docs.mulesoft.com/control-planes/) - [Creating and Deploying Mule Apps](https://docs.mulesoft.com/control-planes/creating-and-deploying-mule-apps) - [Control Plane Hostnames and Allowlists](https://docs.mulesoft.com/control-planes/control-plane-hostnames-allowlists) - [Setting up Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/setting-hybrid-standalone) - [Download, Install, Configure, and Upgrade On-Premises Mule Runtime Engine](https://docs.mulesoft.com/on-premises/latest/runtime-installation-task) - [Configuring Your Network to Support Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/install-self-managed-network-configuration) --- product: Anypoint Platform Control Planes --- # Control Plane Hostnames and Allowlists > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use these hostnames when you allowlist outbound access to an Anypoint Platform control plane, when you pass `--region` to `amc_setup`, or when you set `anypoint.platform.base_uri` and `anypoint.platform.analytics_base_uri`. This table lists platform, analytics ingest, and Runtime Manager hosts for the commercial clouds. When you set `anypoint.platform.base_uri` and `anypoint.platform.analytics_base_uri`, prefix the Platform URL and Analytics ingest hosts with `https://`. See [Configuring Mule to Access Anypoint Platform Control Planes](https://docs.mulesoft.com/control-planes/configuring-mule-control-planes). For MuleSoft Government Cloud hostnames, see [Adding Ports, IPs, and Hostnames for Runtime Manager Agent](https://docs.mulesoft.com/hybrid-standalone/configure-ports-ips) and [MuleSoft Government Cloud Overview](https://docs.mulesoft.com/gov-cloud/). Anypoint Platform PCE uses the hosts you configure when you install PCE. See [Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/latest/). ## Control Plane Hostnames Allow outbound HTTPS (port 443) to these hosts, substituting the row for your cloud. For Hybrid Standalone deployments in Hyperforce regions (Canada, Japan, India, Australia, United Kingdom), the Runtime Manager endpoint uses port 8443.
CloudPlatform URLAnalytics ingestRuntime Manageramc_setup --region

US Cloud (default)

anypoint.mulesoft.com

analytics-ingest.anypoint.mulesoft.com

runtime-manager.anypoint.mulesoft.com

Omit, or prod

EU Cloud

eu1.anypoint.mulesoft.com

analytics-ingest.eu1.anypoint.mulesoft.com

runtime-manager.eu1.anypoint.mulesoft.com

eu1

Canada Cloud

ca1.platform.mulesoft.com

analytics-ingest.ca1.platform.mulesoft.com

runtime-manager.ca1.platform.mulesoft.com

Copy the command Runtime Manager generates when you add a server.

Japan Cloud

jp1.platform.mulesoft.com

analytics-ingest.jp1.platform.mulesoft.com

runtime-manager.jp1.platform.mulesoft.com

Copy the command Runtime Manager generates when you add a server.

India Cloud

in1.platform.mulesoft.com

analytics-ingest.in1.platform.mulesoft.com

runtime-manager.in1.platform.mulesoft.com

Copy the command Runtime Manager generates when you add a server.

Australia Cloud

au1.platform.mulesoft.com

analytics-ingest.au1.platform.mulesoft.com

runtime-manager.au1.platform.mulesoft.com

Copy the command Runtime Manager generates when you add a server.

United Kingdom Cloud

gb1.platform.mulesoft.com

analytics-ingest.gb1.platform.mulesoft.com

runtime-manager.gb1.platform.mulesoft.com

Copy the command Runtime Manager generates when you add a server.

### Hybrid Standalone Port Requirements for Hyperforce Regions For Hybrid Standalone deployments in Hyperforce regions (Canada, Japan, India, Australia, and United Kingdom), the Runtime Manager endpoint requires port 8443 instead of port 443. Ensure your firewall rules include: - `runtime-manager..platform.mulesoft.com:8443` (where `` is `ca1`, `jp1`, `in1`, `au1`, or `gb1`) These endpoints support mTLS and WebSocket connections, consistent with US and EU deployments. Don’t allowlist Anypoint Platform services by a single IP address. Some addresses are assigned dynamically and can change. ## Allowlists and Endpoints by Runtime Plane For ports, extra hostnames, and application endpoints, use the product topic for that runtime: - CloudHub 2.0: [Runtime Plane Regions and DNS Records](https://docs.mulesoft.com/cloudhub-2/ch2-architecture#regions-and-dns-records) and [Configuring Endpoints and Paths for Apps Deployed to a Private Space](https://docs.mulesoft.com/cloudhub-2/ch2-config-endpoints-paths) - CloudHub: [CloudHub Networking Guide](https://docs.mulesoft.com/cloudhub/cloudhub-networking-guide) and [Dedicated Load Balancer Allowlists](https://docs.mulesoft.com/cloudhub/lb-allowlists) - Runtime Fabric: [Configuring Your Network to Support Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/install-self-managed-network-configuration) - API gateway: [Ports, IPs, and Hostnames to Allow](https://docs.mulesoft.com/mule-gateway/mule-gateway-hostnames) - Hybrid Standalone: [Adding Ports, IPs, and Hostnames for Runtime Manager Agent](https://docs.mulesoft.com/hybrid-standalone/configure-ports-ips) ## See Also - [Anypoint Platform Control Planes Overview](https://docs.mulesoft.com/control-planes/) - [Creating and Deploying Mule Apps](https://docs.mulesoft.com/control-planes/creating-and-deploying-mule-apps) - [Configuring Mule to Access Anypoint Platform Control Planes](https://docs.mulesoft.com/control-planes/configuring-mule-control-planes) --- product: Anypoint Platform Control Planes --- # Creating and Deploying Mule Apps > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Create the Mule app in Anypoint Code Builder (with MuleSoft Vibes) or Anypoint Studio, then deploy it through the Anypoint Platform control plane that holds your organization. Runtime Manager in that control plane is the hub for CloudHub, CloudHub 2.0, Runtime Fabric, and Hybrid Standalone. Studio, Anypoint Code Builder, the Mule Maven Plugin, Anypoint CLI, and REST APIs can also deploy to a subset of those runtimes. Which runtime you can use depends on the control plane. See [Choose a Runtime Plane](#choosing-a-runtime-plane). If the app uses API gateway with a non-US Cloud control plane, set control plane properties when you deploy. See [Configuring Mule to Access Anypoint Platform Control Planes](https://docs.mulesoft.com/control-planes/configuring-mule-control-planes). ## Sign In to the Control Plane [Sign in to the control plane](https://docs.mulesoft.com/control-planes/#signing-in) that holds the organization. Runtime Manager, Anypoint Studio, the Anypoint Code Builder desktop IDE, and Anypoint CLI all use that same session. ## Create the Mule App Create the Mule app in Anypoint Code Builder with MuleSoft Vibes using natural language or use Anypoint Studio (Studio). These IDEs run on your computer and connect to Anypoint Platform. Optionally, design the API specification first in Anypoint Platform, publish it to Exchange, then implement it as a Mule app in Anypoint Code Builder or Studio.
Creation processProductDescription

Design the API specification in Anypoint Platform (optional)

API Designer

API Designer is the specification tool in Anypoint Design Center. You open it after you sign in to Anypoint Platform, author the RAML or OAS contract, and publish it to Exchange so Anypoint Code Builder or Studio can scaffold a Mule app from that spec.

Create the Mule app on your computer

Anypoint Code Builder

Anypoint Code Builder is the VS Code IDE for API specifications, implementations, and integrations in a Mule app. Install the desktop IDE, then connect it to the same control plane as your organization. See Sign in to Anypoint Platform from the IDE.

Create the Mule app from natural language

MuleSoft Vibes

MuleSoft Vibes is the assistant in Anypoint Code Builder. You describe the outcome in the IDE. It uses your Anypoint Code Builder session to create and configure applications. MuleSoft Vibes is available on US, EU, Canada, and Japan cloud hosts.

Create the Mule app on your computer

Anypoint Studio

Anypoint Studio is MuleSoft’s Eclipse-based desktop IDE for designing and testing Mule apps. Add your Anypoint Platform account in Studio so you can import assets from Exchange. See Adding Anypoint Platform User Accounts.

## Deploy Through the Control Plane Deploy the Mule app through the Anypoint Platform control plane that holds the organization. Choose a runtime plane that control plane supports, then deploy from Runtime Manager or from another tool that can target that runtime. ### Choose a Runtime Plane Choose a runtime plane that your commercial cloud supports. CloudHub is available only on US Cloud and EU Cloud. CloudHub 2.0, Runtime Fabric, and Hybrid Standalone are available on all commercial clouds. Follow the deploy topic for that runtime, or [deploy from a tool](#deploy-from-a-tool).
Runtime planeControl PlanesWhere to deploy

CloudHub 2.0

  • US Cloud

  • EU Cloud

  • Canada Cloud

  • Japan Cloud

  • India Cloud

  • Australia Cloud

  • United Kingdom Cloud

Deploying Mule Apps to CloudHub 2.0. For DNS and URL format, see Runtime Plane Regions and DNS Records.

CloudHub

  • US Cloud

  • EU Cloud

Deploying Mule Apps to CloudHub.

Runtime Fabric

  • US Cloud

  • EU Cloud

  • Canada Cloud

  • Japan Cloud

  • India Cloud

  • Australia Cloud

  • United Kingdom Cloud

Deploying Mule Apps to Runtime Fabric. For Canada Cloud, Japan Cloud, India Cloud, and Australia Cloud, contact your account manager to unlock Runtime Fabric.

Hybrid Standalone

  • US Cloud

  • EU Cloud

  • Canada Cloud

  • Japan Cloud

  • India Cloud

  • Australia Cloud

  • United Kingdom Cloud

Deploying Mule Apps to Hybrid Standalone Instances. Register the Runtime Manager agent with the control plane that holds the organization. A Mule instance that is not registered to Runtime Manager is an on-premises runtime, not a control-plane deploy. See Run Mule Runtime Engine On-Premises.

### Deploy from a Tool Use [Anypoint Runtime Manager](https://docs.mulesoft.com/runtime-manager/) to deploy to any runtime plane the control plane supports. Studio, Anypoint Code Builder, the Mule Maven Plugin, Anypoint CLI, and REST APIs can deploy without opening Runtime Manager first, with these limits:
ToolDeploys to

Runtime Manager

Anypoint Studio

Deploying a Mule Application to CloudHub. To deploy a Studio project to CloudHub 2.0, Runtime Fabric, or Hybrid Standalone, use Runtime Manager.

Anypoint Code Builder

Mule Maven Plugin

Anypoint CLI

REST APIs

## Manage the Deployed Mule App After you deploy, you manage, monitor, and secure the Mule app in the same Anypoint Platform control plane. Open these products from the Anypoint Platform UI. The table groups them by task. Feature availability varies by control plane. See [MuleSoft product features by Control Plane](https://docs.mulesoft.com/hyperforce/#features-supported-on-hyperforce).
CategoryProductDescription

Application management

Runtime Manager

After you deploy, use Runtime Manager to start, stop, update, and delete Mule apps. You can also view logs, set properties, manage schedules, and create alerts.

Monitoring

Anypoint Monitoring

Anypoint Monitoring provides visibility into integrations across your app network. Use it to view metrics, configure dashboards and alerts, and search logs.

API Visualizer

API Visualizer gives you a real-time, graphical view of your application network, including APIs, Mule applications, and the third-party systems they invoke.

APIs

API Manager

Anypoint API Manager enables you to manage, govern, and secure APIs. Apply policies, manage contracts and client applications, and track API instances that your Mule apps expose.

API Governance

Anypoint API Governance lets you apply governance rules to services, including APIs, as part of the service lifecycle.

API Functional Monitoring

Monitor APIs and endpoints at scheduled intervals. Receive reports about whether tests pass or fail, and view statistics about API and endpoint performance.

Data and messaging

Object Store v2

Object Store v2 lets Mule apps store data and state. You open the Object Store v2 UI from Runtime Manager.

Anypoint MQ

Anypoint MQ is a cloud-based messaging service for exchanging data asynchronously between applications. Create and monitor queues and message exchanges in the Anypoint Platform UI.

Access and security

Access Management

Access Management is the hub for users, authentication, and permissions in your Anypoint Platform organization. Use it to manage environments, business groups, and who can operate the deployed app.

Secrets Manager

Anypoint Security secrets manager stores and controls access to keys, certificates, passwords, and other secrets that supported Anypoint Platform services consume.

Catalog and usage

Exchange

Anypoint Exchange is a curated catalog of reusable assets. Catalog, share, and discover APIs, connectors, and other assets in the same control plane.

Usage Reports

Usage reports provide monthly and daily summaries of resource use across Anypoint Platform products, including Mule runtime and CloudHub vCore.

## See Also - [Anypoint Platform Control Planes Overview](https://docs.mulesoft.com/control-planes/) - [Control Plane Hostnames and Allowlists](https://docs.mulesoft.com/control-planes/control-plane-hostnames-allowlists) - [Configuring Mule to Access Anypoint Platform Control Planes](https://docs.mulesoft.com/control-planes/configuring-mule-control-planes) - [Anypoint Platform Hosting Overview](https://docs.mulesoft.com/hosting-home/) - [Salesforce Hyperforce Overview](https://docs.mulesoft.com/hyperforce/)