MuleSoft price and vCore costs, explained for buyers. Why unused capacity costs more than the uplift.

MuleSoft vCore subscriptions price by tier and committed capacity, roughly $8,000 per production vCore a year at Platinum. The largest cost is unused vCore that a multi year deal locks in, so size to measured peak before you negotiate the rate.

How is MuleSoft priced in 2026?

MuleSoft is sold on two models. Most enterprises that bought Anypoint before usage based pricing arrived hold a core based subscription: one of three platform tiers set for the whole contract, committed vCores, premium connectors and support. New contracts are quoted in Mule Credits, a shared consumption pool that MuleSoft lists from $2,000 a month.

This guide concentrates on the vCore subscription, because most renewals we see still run on it and that is where the overspend sits. Its pricing works differently from the rest of the Salesforce portfolio, so procurement teams routinely underestimate the renewal. The metric rules are in our MuleSoft licensing guide and the Salesforce knowledge hub.

What does one vCore buy?

One vCore is roughly one virtual processor core of CloudHub runtime. CloudHub 1.0 workers come in fixed sizes of 0.1, 0.2, 1, 2, 4, 8 and 16 vCores, and every running application draws its full worker size from your pool whether it is busy or idle. Two workers for one application draw twice.

Two habits inflate the count. Teams deploy on 1 vCore workers by default when a 0.2 vCore worker would carry the load, and they run two workers per application for availability without checking which applications need it. Subscriptions usually list production and sandbox vCores separately, so the same habits repeat outside production.

Where does Composer fit?

Composer is sold by the Salesforce account team and priced per flow, with no vCore involved. In a typical Anypoint organization a meaningful share of deployed applications are low code integrations that never needed a runtime vCore. Deciding which workloads need CloudHub runtime and which belong on Composer is a sizing exercise for before the tier conversation.

What changes on the Mule Credits model?

Mule Credits replace vCores as the unit you buy. Credits are drawn down by metered usage such as Mule flows, Mule messages, managed API instances and gateway requests, and the per credit rate falls as volume grows.

MuleSoft offers three buying options: Pre-Purchase, where credits are bought upfront, Pre-Commit with a $50,000 minimum annual commitment, and Unlimited at a custom fixed annual price.

• Flows still follow worker counts. Flows are billed on the highest number deployed in any single hour of the month, multiplied by workers or replicas, so two workers per application still doubles the count.
• Over commitment survives. A Pre-Commit sized on a growth forecast leaves unused credits in the same way an oversized vCore pool leaves unused cores.

What does over committed vCore cost?

Every committed vCore that production never uses costs the full annual production rate. The gap between committed and consumed capacity is the largest single number in a MuleSoft contract, and it is easy to price once you have the usage data.

How does a three year term multiply the excess?

A multi year deal charges the same excess again every year, with the annual uplift on top. The table below takes the two 100 vCore cases and applies the low and high end of the uplift range from the pricing table.

Compare those totals with the uplift itself. On a 100 vCore commitment at $800,000 a year, a 7 percent uplift adds $56,000 in the second year, and the unused capacity costs four to six times that figure.

Why do multi year MuleSoft deals lock in the excess?

Because the ramp structure that caps the annual uplift also fixes the committed quantity for the whole term. In the deals we reviewed, the multi year ramp came without a usage true down, so an oversized commitment could not be reduced until the term ended. The contract presented the rate cap as the benefit and said nothing about the quantity.

Why is vCore bought on forecast?

Integration growth is hard to predict, and a platform team that runs out of vCores blocks project delivery. The incentive therefore runs toward buying headroom, and that headroom is billed at the full production rate from the first day.

How does the Salesforce bundle hide the unit price?

Salesforce often folds MuleSoft into a Sales Cloud or Service Cloud renewal, which hides the MuleSoft unit price inside a larger discount. When no one can see what a vCore costs, the unused vCores never get priced either. The carve out makes every other saving measurable, so it comes first (see multi cloud Salesforce negotiation).

Why we would sign the multi year cap last

The usual advice on a MuleSoft renewal is to sign three years early to cap the uplift. We think that reverses the order. A cap on a quantity that is already too large, with no right to reduce it, protects the smaller number and locks in the larger one.

In the 100 vCore example above, the unused capacity costs more each year than the uplift the cap is meant to limit. Settle the quantity and the reduction right first, and treat the cap as the last term you agree.

The most expensive decision in a MuleSoft contract is the quantity, and it is usually made before anyone argues about the rate.

What have we seen in recent MuleSoft negotiations?

Put together, the pattern is an oversized quantity held in place by a term that gives no way to reduce it.

Salesforce acquired MuleSoft in 2018, and its pricing model never converged with the rest of the portfolio. The costliest assumption we see is treating MuleSoft as one more Salesforce line item. It is a separate integration platform with its own metrics, and it needs its own negotiation.

How do you measure your real vCore peak?

Pull a full year from the Anypoint Usage Report, then check worker sizing in Anypoint Monitoring. The usage report shows what you deployed at peak. Monitoring shows whether those deployments needed their size. Both numbers belong in a documented report before the renewal quote arrives.

• Anypoint Usage Report. Shows vCore Peak per application, meaning the highest hourly vCore consumption in the period, plus the organization wide maximum with a timestamp. It breaks down by business group and covers CloudHub, CloudHub 2.0 and Runtime Fabric.
• Runtime Manager. Lists each application's worker size and worker count. Export it to a sheet with one row per application.
• Anypoint Monitoring. The built in dashboards show CPU and memory per worker. An application that never approaches the capacity of the next size down is a candidate to move.
• Access Management. Shows your vCore entitlement split into production, sandbox and design, and how it is allocated to each business group. That is the committed side of the gap.

A worked right sizing example

Say you commit 100 production vCores and the usage report shows a peak of 71. That first gap of 29 vCores is capacity you never deployed. A second gap sits inside the 71, and the worker inventory finds it.

Add headroom you can tie to named projects, say 4 vCores, and the renewal requirement is 56 vCores against a commitment of 100. At $8,000 each, the 44 vCores you stop paying for are worth $352,000 a year before any uplift. Test the smaller worker sizes in sandbox under production load before you commit to the lower number.

Which MuleSoft tier should you renew on?

Renew on the lowest tier whose features your team uses, tested feature by feature. The tier is fixed for the whole term, so the test has to happen before renewal, when a downgrade can still change the price.

What does Titanium add over Platinum?

MuleSoft's monitoring documentation lists the capabilities that need a Titanium subscription on the core based plans. If none of them are in regular use, Platinum is the likely fit.

• Telemetry Exporter for real time export of audit logs and traces
• Custom metrics sent to Anypoint Monitoring
• Monitoring data retained for more than 30 days
• Log management across applications, including log points and raw data downloads
• Advanced alerts, custom dashboards and reports
• Dedicated infrastructure for monitoring data processing and storage

For Gold against Platinum, take the entitlement schedule from your order form and ask the platform team which items they used in the last 12 months. Anything unused is a reason to price the lower tier.

How do premium connectors raise the MuleSoft price?

Premium connectors add 15 to 40 percent on top of the platform tier, and MuleSoft requires each one to be licensed for every deployment environment. Production, staging, test, sandbox, development and disaster recovery each count, so one integration can carry several connector licenses.

Each connector looks small at signing. Over the term the stack grows, it is rarely reviewed as a whole, and at renewal the uplift applies to all of it. List every premium connector with the environments it is licensed in and the applications that call it. Retire duplicates and unused environment licenses before the renewal quote is built.

What will the MuleSoft account team say, and how should you answer?

These are the lines we hear most often in MuleSoft renewals, with the reply that keeps the negotiation on quantity and terms.

• "Buy the headroom now, because vCores added mid term will cost more." Ask for a price hold on additional vCores at the renewal unit rate for the full term. Then headroom can be bought when a project needs it.
• "True down is not available on a ramp deal." Ask for a reduction right at each anniversary, measured against the Anypoint Usage Report. If that is refused, shorten the term.
• "MuleSoft is already discounted inside your Salesforce agreement." Ask for the MuleSoft lines quoted separately, with a unit price per vCore, per connector and for the tier. A discount you cannot see cannot be compared with a benchmark.
• "Mule Credits will be simpler and cheaper." Ask for both options priced against the same workload, using your flow and message counts from the usage report. Move only when the credit quote is lower for your measured usage.
• "You need Titanium for the monitoring your team relies on." Ask which Titanium features the platform team used in the last 12 months, then price Platinum if the list is empty.

What contract terms should you ask for in a MuleSoft renewal?

Ask for the terms that let the quantity follow your usage. The rate matters less once these are in place.

• True down right. The right to reduce committed vCores at each anniversary, based on the usage report. This is the term that makes a multi year cap safe to sign.
• Written uplift cap. A maximum renewal increase stated as a percentage of the prior year's net price. Without it the next renewal can be quoted from list.
• Price hold on additions. Additional vCores and connectors at the renewal unit rate for the whole term.
• Reallocation. The right to move vCores between production and sandbox, and between business groups, without a new order.
• Tier change at anniversary. The right to move down a tier if its features go unused.
• Connector swap. The right to exchange a premium connector you no longer need for another of the same list price.
• Separate order form. MuleSoft on its own order form, so its price stays visible at every renewal.

When should you start a MuleSoft renewal?

Start 12 months out. The usage data needs a full year to be representative, and the carve out has to be requested before Salesforce builds a bundled quote. Salesforce's fiscal year ends January 31, so pressure peaks in its fourth quarter; see how fiscal year end timing affects Salesforce deals.

What to do next

1. Pull a year of usage data. Export measured peak production vCore from the Anypoint Usage Report, never the provisioned figure, and match it to the Runtime Manager worker list.
2. Price the gap. Multiply the difference between committed and peak vCore by your production rate, so the over commitment carries a dollar figure before talks open.
3. Right size and test the tier. Move oversized workers down in sandbox and check which Titanium or Platinum features the team uses.
4. Clear out the extras. Move low code flows to Composer and consolidate premium connectors by environment.
5. Carve MuleSoft out of the Salesforce bundle. Get the vCore, connector and tier prices on separate lines so each can be benchmarked.
6. Take the multi year cap last. Sign it only with a true down right attached. The Salesforce practice runs the vCore review with you, and our MuleSoft renewal service covers the full negotiation.

Frequently asked questions