MuleSoft pricing 2026,
quote-only by design.
MuleSoft (Salesforce) publishes no prices: its pricing page lists edition names and a feature matrix, then ends at a contact-sales form. Rather than invent a number, this sheet documents what MuleSoft actually publishes, the metering model and CloudHub 2.0 vCore sizing, and the drivers that decide what your quote comes back as. If you only need an API gateway, the six providers that do publish prices are a better place to start.
Δ Quick verdict
MuleSoft is an integration platform with an API gateway attached, sold through negotiated enterprise contracts with no published price. For the gateway function alone it costs orders of magnitude more than the per-request providers on this site. Buy it for hundreds of integration flows, never for the gateway alone. If you only need a gateway, run the calculator against the six providers that do publish prices.
Verified 22 August 2026. MuleSoft and Salesforce pricing pages (mulesoft.com/anypoint-pricing, salesforce.com/mulesoft/anypoint-platform/pricing) list editions and feature matrices but publish no dollar figures. The only pricing-relevant facts MuleSoft publishes are the metering model and the CloudHub 2.0 replica sizing, both from the official documentation:
- [S1] MuleSoft / Salesforce pricing page: confirms editions are listed without prices; every path ends at a contact-sales form.
- [S2] MuleSoft pricing documentation: usage-based metering model (flows, messages, throughput) and the shared resource pool.
- [S3] CloudHub 2.0 architecture documentation: the full replica-size table (mule.nano to mule.2xlarge.mem) with vCore and memory values.
This sheet states no contract dollar figure, because MuleSoft publishes none and third-party contract-benchmark aggregates are not a source we treat as authoritative. Your quote is set by the drivers below.
The pricing model: editions without price tags
Since 2024 MuleSoft has been shifting new contracts from capacity-based vCore licensing to usage-based packages metered on three entitlements: Mule flows (active integrations), Mule messages (volume processed), and data throughput in GB [S2]. The public edition lineup has three packages plus a 30-day trial. None carries a published price, and MuleSoft does not publish the entitlement counts per edition either.
| Edition | Published price | Metered on [S2] | Intended for |
|---|---|---|---|
| Free trial | $0 | 30 days, full platform | Evaluation only; no permanent free tier |
| Anypoint Integration Starter | Not published | Flows · messages · throughput | First integration projects, small and mid-size teams |
| Anypoint Integration Advanced | Not published | Flows · messages · throughput | Enterprise integration estates, multiple environments |
| API Management Solution | Not published | APIs under management | Gateway / governance only, no full integration runtime |
Both Integration packages include Runtime Manager, Design Center, DataWeave, CloudHub deployment, and API support. The specific flow, message, and throughput entitlements per edition are set in the quote, not published, so this table names the metering axis rather than a number MuleSoft does not disclose.
What a vCore is, and why contracts still hinge on it
A vCore is MuleSoft's unit of compute for running Mule applications on CloudHub: a slice of CPU and memory that each deployed app reserves. Capacity-based contracts (the Gold, Platinum, and Titanium tiers) were sold as vCore pools per environment, and most existing customers still renew on vCore counts. Accounts on the newer usage-based packages see flows, messages, and throughput entitlements instead of vCores in Access Management [S2].
| Replica size | vCore | Memory |
|---|---|---|
| mule.nano | 0.05 | 1 GB |
| mule.small | 0.2 | 2 GB |
| mule.large | 1.0 | 4 GB |
| mule.2xlarge.mem | 4.0 | 15 GB |
Selected points from the published range (11 sizes in total). Every always-on integration reserves capacity around the clock, so idle flows still consume paid vCores.
- On capacity-based contracts, the number of vCores you commit to is the primary line item, so right-sizing replicas and retiring idle apps is the most direct cost control.
- CloudHub generally carries a higher per-vCore cost than self-managed Runtime Fabric at scale, so deployment model is a real lever.
- MuleSoft does not publish a per-vCore rate; the price per vCore is set in the negotiated contract and varies with volume, term, and bundling.
The practical consequence: a modest deployment of 2 to 4 production vCores plus matching non-production capacity, across dev, test, and prod environments, multiplies quickly. Environments are the quiet cost driver, since each one needs its own capacity allocation.
What actually drives your quote
With no list price, the only honest way to anticipate a MuleSoft bill is to size the drivers the sales team prices against. There is no shortcut number here, and a benchmark median from a procurement aggregator tells you nothing about what your workload will cost. Model these instead:
| Driver | Why it moves the quote |
|---|---|
| Capacity | vCore pool on capacity contracts, or flows / messages / throughput on usage-based packages. The single largest line item. |
| Environments | Dev, test, and prod each need their own allocation. Idle non-prod capacity still bills. |
| Edition | Integration Starter vs Advanced vs API-Management-only changes both the runtime scope and the metering entitlements. |
| Deployment model | CloudHub vs self-managed Runtime Fabric vs hybrid; Runtime Fabric is generally cheaper per vCore at scale. |
| Support tier & term | Premium support and multi-year commitments trade off against price locks and discounting. |
| Salesforce bundling | MuleSoft can be negotiated inside a wider Salesforce agreement, which widens the discount band. |
The subscription is only part of the bill
Year-one spend is rarely just the licence. MuleSoft does not price any of the following, so treat them as cost categories to scope and quote for your own project rather than as published figures:
| First-year cost component | What to scope |
|---|---|
| Implementation / integration build | Statement of work from MuleSoft services or a partner; often the largest year-one item. |
| Professional services | A meaningful share of first-year software cost; get it quoted alongside the licence. |
| Developer training | Per-developer enablement to reach productivity on Anypoint and DataWeave. |
| Specialist staffing | MuleSoft developers are a scarce, premium-salary skill set to hire or contract. |
| Implementation timeline | Commonly several months before the platform delivers value; budget for the ramp. |
Negotiation levers that move the quote
- Competitive evaluation. Running a live alternative (Apigee, Kong, Boomi) gives you real leverage on price.
- Volume commitment. Larger vCore or capacity counts unlock better per-unit rates.
- Multi-year terms. Trade term length for price locks and capped uplifts at renewal.
- Salesforce bundling. Negotiating MuleSoft inside a wider Salesforce agreement, especially at quarter-end, widens the discount band.
- Deployment model. Self-managed Runtime Fabric is generally cheaper per vCore than CloudHub at scale.
The initial quote is a starting point, not a price. Because nothing is published, the seller sets the anchor; a genuine competitive process and a clear capacity model are what move it.
Renewals deserve the same scrutiny: capacity you bought for a migration year rarely matches steady-state usage, and unused vCores renew at full rate unless you cut them.
MuleSoft vs the rest of this site
Comparing MuleSoft to per-request gateways is comparing a freight contract to a stamp, but the scale of the gap is the useful information:
| Provider | Published entry price | Pricing transparency | Detail sheet |
|---|---|---|---|
| MuleSoft Anypoint | None (quote-only, negotiated contract) | Quote-only, negotiated | This sheet |
| Google Apigee | PAYG $20/M + environment from $365/mo; subscriptions quote-only | Tiers published, Enterprise negotiated | /apigee |
| AWS API Gateway | $1.00/M calls (HTTP API), no base fee | Fully published | /aws |
| Kong Konnect | Free tier, then per-service / per-request plans | Published, Enterprise negotiated | /kong |
When MuleSoft earns its price
- Dozens to hundreds of integration flows across SAP, Salesforce, databases, and legacy systems
- B2B/EDI, batch processing, and ETL alongside APIs
- A large pre-built connector catalogue saves real engineering months
- You are already deep in the Salesforce estate and can bundle
When it does not
- You need an API gateway: auth, rate limiting, routing. AWS, Cloudflare, or Kong do this for a fraction of the cost
- Your integrations are cloud-native services talking over APIs anyway
- You cannot staff or train scarce MuleSoft specialists
- Year-one budget cannot absorb implementation and services on top of the subscription
Model your actual workload: the cost calculator ranks the six providers with published pricing against your request volume and payload size, and the main comparison sheet shows where each one breaks even.