MuleSoft Anypoint capacity and usage-based licensing covers how Salesforce sells MuleSoft, its integration and API management platform. Anypoint Platform is MuleSoft’s suite for creating, integrating, modeling, building and deploying services, APIs and Mule applications, and Mule is its runtime engine.[1] Three licensing constructs exist side by side:
- Capacity. Customers buy CloudHub vCores for MuleSoft-hosted runtimes and Cores for runtimes they host themselves, split into Production, Pre-Production and Design.
- Usage. Organizations provisioned with a usage-based pricing package are entitled to Mule flows, Mule messages and data throughput instead of vCores.[3]
- Credits. MuleSoft Automation is sold in Automation Credits, and current MuleSoft packages include Mule Credits, a single consumption unit shared across the portfolio.[5]
The contractual reference is the Subscription Plans document for purchases made from Salesforce on or after 27 June 2025, read together with the Order Form. MuleSoft Documentation explains how usage is metered.
Editions
The Subscription Plans document sells Anypoint Platform in three editions, each including the one below it. Gold is the entry edition, with a Premier Success Plan and a defined capacity bundle. Platinum adds High Availability, Business Groups, Global Cloud Deployment, Anypoint Runtime Fabric, Flexible Hybrid Deployment on request, and an EU control plane option that can be chosen only at initial purchase. Titanium adds Anypoint Monitoring features and Hyperscale Storage of 200 GB per Production vCore plus 50 GB per Pre-Production vCore.[1] For purchases or renewals on or after 29 June 2026, Titanium comes with the Premier Success Plan in place of Titanium level support.
| Offering (Gold Edition) | Runtime capacity | API management entitlement |
|---|---|---|
| Anypoint Platform Base Subscription | 2 Production, 4 Pre-Production and 4 Design Cores/vCores | 10 Production and 10 Pre-Production API Instances; 10 governed APIs; 20M Flex Gateway API Calls per year |
| API Management Solution | 1 Production and 2 Pre-Production Gateway Cores/vCores; 2 Design vCores | 15 Production and 30 Pre-Production APIs; 15 governed APIs; 20M Flex Gateway API Calls per year |
| Anypoint Starter for Industry Clouds | 1 Production, 1 Pre-Production and 1 Design vCore | 3 Production and 6 Pre-Production API Instances; 6 governed APIs |
Source: Subscription Plans.[1] The Base Subscription SKUs were already in the catalog. The API Management Solution SKUs (Anypoint Platform - API Management Solution - Gold Edition, Anypoint Platform - API Management Solution - Platinum Edition, Anypoint Platform - API Management Solution - Titanium Edition), MuleSoft - Anypoint Starter for Industry Clouds - Gold Edition, Anypoint MQ 500M Additional API Requests, Anypoint VPC and Anypoint DataGraph - Production are added here. An API Gateway deployed under the API Management Solution may use only HTTP/S, Web Services, JDBC and JMS connections, and may not be used for batch processing or polling.
MuleSoft Automation is sold separately. MuleSoft - Automation (57,000 Credits) includes 57,000 Automation Credits per year together with MuleSoft RPA and small vCore allowances. MuleSoft - Automation for vCore/Core includes 9,000,000 Automation Credits 2.0 per year together with MuleSoft Composer, MuleSoft for Flow: Integration and Flow Orchestration. Top-up packs such as Mulesoft - Additional Automation Credits (10,000) are also available.[1]
Metrics
| Metric | How it is counted | Source |
|---|---|---|
| vCore | One virtual core of CloudHub compute; up to ten Mule applications per vCore purchased | Subscription Plans |
| Core (MuleSoft Software) | Physical core or vCPU available to a self-hosted Mule runtime | Subscription Plans |
| Mule flow | Flows with an event source or APIkit routing; monthly maximum concurrent | Usage and Rates |
| Mule message | One unit per event-source trigger; monthly total | Usage and Rates |
| Data throughput | Bytes in and out of the Mule infrastructure; monthly sum | Usage and Rates |
| API Instance | APIs managed in API Manager on Flex Gateway, Mule Gateway or Service Mesh | Subscription Plans |
| API under Governance | APIs selected by at least one governance profile | Usage and Rates |
| API Call (Anypoint Flex Gateway) | Any request received by Flex Gateway, successful or not | Subscription Plans |
| Anypoint MQ API request | Requests to retrieve messages; all environments combined | Usage and Rates |
| Object Store API request | Up to 100 KB per request | Usage and Rates |
| Automation Credits / Automation Credits 2.0 | Spent as Composer Tasks, RPA Bot Minutes, RPA API Calls and (2.0 only) Flow tasks and runs | Subscription Plans |
| Mule Credits | Shared unit across eligible MuleSoft capabilities, with a rate per usage type | MuleSoft pricing |
Counting / floors
Capacity (vCores and Cores)
For runtimes the customer hosts, whether standalone or in containers, the count is based on logical or allocated cores. Allocated cores are the number of cores visible to the Java virtual machine that runs Mule. Where cores are not explicitly allocated, the logical cores the operating system reports for the machine or container are used. Physical cores are not considered. Several VMs or containers on one physical host are each metered for their own allocated cores, even though they share the same physical cores. Fractional cores always round up to the next whole number (rule).[1] Fractional capacity is a method of calculation only on CloudHub and Runtime Fabric.
Each Production Core purchase includes one Developer Workstation, and each Production vCore purchase includes two static IPs. Except for ELAs and No Cloud purchases, each additional Pre-Production Core/vCore comes with one additional Design vCore (rule).[1]
Usage-based pricing
Under a usage-based package, three Mule runtime metrics are aggregated over each month:[2]
- Flows use a Max Concurrent model. The month’s usage is the highest number of flows that existed in any single hour (rule).
- Messages are totalled. A message counts once when an event source triggers it (rule).
- Data throughput is the sum of all bytes. It includes internal operational traffic such as monitoring, logs and health checks, not only business payloads (rule).
A flow is billable only if it contains a Mule event source or routes APIkit requests. MuleSoft suggests subflows or private flows, which are not billable, as a way to reduce cost, and advises against deploying unused flows from accelerators. Anypoint Studio 7.20 and later can show the number of billable flows in a project (rule).[4]
For an organization provisioned with a usage-based package, Access Management shows flow, message and throughput entitlements instead of vCores, at root-organization level only. vCores can then no longer be tracked or allocated among business groups (rule). A shared global pool of CPU and memory serves CloudHub and CloudHub 2.0 deployments. When the pool runs out, new deployments are blocked until resources are freed. After opting in, apps must be redeployed. CloudHub apps are redeployed automatically in the monthly patch cycle, but Runtime Fabric apps must be redeployed manually “to remain in compliance” (rule).[3] CloudHub 2.0 replica sizes are shown with a legacy vCore equivalent, for example mule.micro at 0.1 and mule.medium at 0.5.[3]
API management and messaging
API Instances are counted as a maximum concurrent, with separate figures for production, pre-production and unclassified instances. An instance stays under management until it is deleted.[2] All versions of a governed API count as one governed API (rule). Anypoint MQ API requests are added up across all environments, including design and sandbox (rule). An Object Store request carries up to 100 KB, and a larger request counts as several requests with no fractional units (rule).[2]
The Subscription Plans document caps the API Calls, API Instances and governed APIs included in a plan. It states that these limits are contractual and not enforced by the service, and that Salesforce may review use at any time. Unused Flex Gateway API Calls are forfeited at each anniversary of the Order Start Date, or at the Order End Date if that comes first, and do not roll over (rule).[1]
Automation Credits
Automation Credits are allotted per year and prorated for Order Terms shorter or longer than twelve months. They are spent as Composer Tasks, RPA Bot Minutes or RPA API Calls; Automation Credits 2.0 can also be spent as Flow Integration Tasks and Flow Orchestration runs. MuleSoft - Automation for vCore/Core includes 9,000,000 Automation Credits 2.0 per year (rule). RPA Bot Minutes count every parallel session of a bot and every separate bot running the same process, and test runs count too.[1]
Virtualization & partitioning
Self-hosted Mule runtimes are licensed on the cores visible to Mule in each VM or container, not on the host’s physical cores. Placing several runtimes on one host therefore does not reduce the count (rule). Under Flexible Hybrid Deployment, available on request with Platinum and Titanium, a customer may use either Cores or vCores up to the capacity on the Order Form. It may exchange a Core for a vCore, or the reverse, no more than once per month through a Flexible Deployment Request, and must stop using the capacity it gives up (rule).[1]
Cloud / BYOL
On Amazon EC2, each EC2 vCPU counts as one core. The exception is t2 instances, where the core count is the number of CPU minutes available in 24 hours divided by the number of minutes in 24 hours (rule).[1] Government Cloud Deployment allows deployment into MuleSoft’s FedRAMP-configured AWS GovCloud environment, and access is limited during a provisioning period. Anypoint Platform Private Cloud Edition is listed as a separate offering, and a Monitoring for On-Premise Management license file may be used once per Private Cloud Edition installation.
Programs
- Anypoint usage-based pricing package, for example Anypoint Integration Advanced. Entitlements are counted in flows, messages and throughput rather than vCores.[3]
- Mule Credits buying models. Salesforce’s MuleSoft pricing page names three.[5] Pre-Purchase: a package and a block of credits bought up front, with no minimum credit purchase. Pre-Commit: a yearly baseline paid monthly, with a $50K minimum annual commitment (rule). Unlimited: uncapped credits for a custom fixed price. Each usage type has its own credit rate, and the rate falls as usage rises (rule). Credits can be topped up if usage exceeds the allocation.
- The Salesforce-wide Agentic Enterprise License Agreement is a separate unlimited-consumption agreement for Salesforce consumption services.
Out of scope
- List prices. The pricing page’s starting price of $2,000 per month for a package, billed annually, is a marketing figure.
- Salesforce CRM user licenses. CRM Users do not convert to vCores, Cores or Mule Credits.
- Anypoint Code Builder, Anypoint Studio and connector terms beyond their inclusion in the plans.
- The MuleSoft product versioning and back support policy, which governs support rather than licensing.