Anypoint Platform Pricing | MuleSoft Documentation
# Anypoint Platform Pricing
The Usage Reports page supports pricing packages for integration. When your organization opts in to a usage-based pricing plan, such as the Anypoint Integration Advanced package, you must redeploy your apps. After redeploying your apps, your usage reports are shown.
For CloudHub and CloudHub 2.0, apps are automatically redeployed during the monthly runtime patch update cycle. For more information, see CloudHub Runtime Continuous Updates and CloudHub 2.0 Operating System Patch Updates.
For Runtime Fabric, you must manually redeploy apps to remain in compliance with your Anypoint Platform contract.
## Metrics Definitions
Usage-based pricing packages and their usage reports are based on your organization’s use of allotted Mule components.
To understand the technical aspects of metering and pricing concepts within Anypoint Platform, see Usage and Pricing Metrics Reference documentation.
## Global Resource Pool Limits
Root organizations provisioned with usage-based pricing receive a shared global pool of CPU and memory resources for CloudHub and CloudHub 2.0 deployments across all business groups and environments in the organization. This pool of resources is large enough to consume all 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.
When your organization approaches the resource limit on the Applications List UI, Application Deployment UI, and Manage Application UI, you receive a warning. To avoid reaching limits, allocate only the needed resources by using granular replica sizes in CloudHub and CloudHub 2.0.
Contact Support if you require an exception when you reach the resource limit.
This limit doesn’t impact applications configured with Configuring Horizontal Autoscaling (HPA) for CloudHub 2.0 Deployments. You can continue to deploy applications if Horizontal Pod Autoscaling is enabled even if you reach the global resource limits.   
---  
## CloudHub 2.0 Application Deployment
For organizations provisioned with a usage-based pricing package, CloudHub 2.0 uses replica sizing for application deployment. You can choose 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.
Offering | Equivalent vCore Size | Total Memory | Heap Memory | Storage  
---|---|---|---|---  
mule.micro.mem  
mule.medium  
mule.medium.mem  
mule.large.mem  
mule.xlarge  
mule.xlarge.mem  
mule.2xlarge.mem  
During the monthly patching cycle, your applications automatically migrate to an equivalent replica size.
## Access Management Entitlements
Accounts provisioned with a usage-based pricing package show flows, messages, and throughput entitlements in Access Management instead of vCores. These entitlements are available only at the root organization level. 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 in the Access Management UI.
## See Also
  *