Anypoint Platform Pricing

When your organization opts into a usage-based pricing plan, such as the Anypoint Integration Advanced package, your apps must be redeployed. After redeploying your apps, your usage reports temporarily display both legacy vCore-based metrics and usage-based metrics for your apps. Usage reports cover an entire month, so usage reports appear for both the usage-based pricing packages and the legacy subscription-based vCore pricing for that month.

For CloudHub and CloudHub 2.0, apps are automatically redeployed during the monthly runtime patch update cycle. See CloudHub Runtime Continuous Updates and CloudHub 2.0 Operating System Patch Updates for more details.

For Runtime Fabric, you must redeploy apps manually. After you redeploy all RTF apps, usage reporting shifts from a mix of usage and vCore reports to all usage-based reporting. You must redeploy RTF apps in a timely manner to remain in compliance with your Anypoint Platform contract.

To benefit from the robust usage reports that accompany usage-based pricing plans, all of your applications (in production and sandbox) must use the following Mule versions:

After your organization onboards to usage-based pricing, you must redeploy your apps with a supported version, either manually or during the monthly patching cycle. The monthly patching cycle is applicable only for CloudHub 1.0 and CloudHub 2.0 applications. RTF customers must be using RTF agent version 1.13.112 or 2.1.30 or newer. You must also manually redeploy Runtime Fabric applications (with a supported date-patch version) after your organization is onboarded to usage-based pricing.

To roll back to a previous successful configuration of existing applications that use a Mule version that the usage-based pricing model does not support, choose a compliant version before deploying changes. After deployment, MuleSoft creates a new configuration with the previously chosen settings and a supported runtime.

Usage-based pricing packages and their usage reports are based on your organization’s use of allotted Mule components.

For information about pricing concepts within Anypoint Platform, see Usage and Pricing Metrics.

Root organizations provisioned with usage-based pricing receive a global pool of shared CPU and memory resources that is shared for deployments into CloudHub 1.0 and CloudHub 2.0 across all business groups and environments in the organization. This pool of resources is large enough to consume all of the purchased flows and messages without interruption. If an organization runs out of resources, actions that consume more resources such as deploying new applications or starting stopped applications are blocked until sufficient resources are available.

You can free up resources by stopping or deleting unused applications, or reducing the replica size or resources that an existing application consumes. You receive a warning each time your organization approaches the resource limit on the Applications List UI, Application Deployment UI, and Manage Application UI. To avoid hitting limits, allocate only what you need by using granular replica sizes in CloudHub 1.0 and CloudHub 2.0. Contact Support if you require an exception when you reach the limit.

For organizations provisioned with a usage-based pricing package, CloudHub 2.0 uses replica sizing for application deployment. You can choose from the following replica sizes based on the application profile or size and display the equivalent in terms of legacy vCores. Replica sizes with the suffix .mem are memory-intensive options with the same compute.

During the monthly patching cycle, your applications automatically migrate to an equivalent replica size. Application deployment through the Mule Maven Plugin is not yet supported. However, you can deploy using the Runtime Manager UI and the Application Manager Experience APIs by leveraging a new field under target.deploymentSettings called instanceType.

Accounts provisioned with a usage-based pricing package show flows, messages, and throughput entitlements instead of vCores on Access Management. These entitlements are available at the root organization level and cannot be allocated among business groups. Because vCores are no longer the purchased entity, they can no longer be tracked or allocated among business groups. To view your monthly usage of flows, messages, and throughput, access usage reports by using the Access Management UI.