The vCore is the unit. The bundle is the trap. The renewal is where the band gets loaded.
MuleSoft sells capacity in committed vCore pools that you pay for whether or not you consume them, bundles features into editions at different vCore floors, and now renews through the Salesforce account team on the Salesforce uplift playbook. The pricing model survived the acquisition. The renewal posture did not, and that is the change buyers are meeting for the first time in this cycle.
Prepared by Redress Compliance · August 10, 2026 · Salesforce advisory. Based on 15 to 25 MuleSoft renewals benchmarked or run, 2024 to 2025.
Executive summary
vCore over commitment against actual utilization averaged 28 to 44 percent across the estates we benchmarked. The pool is committed capacity, paid for whether or not it is consumed, and most enterprises had sized it to peak rather than to trailing average.
Right sizing against measured trailing 90 day utilization returned 22 to 38 percent of the platform line on estates that had not refreshed their commit in more than eighteen months, which is most of them.
The gateway release decoupled gateway capacity from platform vCores, and the lever moved with it.
Deploying the newer gateway for north south traffic separated that capacity from the committed pool on roughly two thirds of the estates we reviewed, and buyers who migrated recovered 18 to 32 percent of total vCore spend.
It is the rare case where an architectural change is also a licensing one, and estates that have not revisited the split are paying the old arithmetic.
Bundle edition mismatches drove the largest single source of unnecessary spend. The editions bundle features at different vCore floors, and most buyers sat on the top tier for a single capability that could have been procured as a discrete add on.
Scoring the estate against actual feature consumption and stepping down one tier returned 14 to 28 percent on most estates, without removing anything anybody was using.
Salesforce now owns the renewal, and the default uplift is negotiable. Post acquisition renewals run through the Salesforce account team and follow the Salesforce uplift playbook, with the default landing between five and twelve percent and anchored caps holding when they are asked for.
Salesforce also now expects a six month renewal preparation window, so the calendar is part of the negotiation rather than an administrative detail around it.
What the committed pool actually covers
| Element | How it works | Buyer note |
|---|---|---|
| vCore pool | Committed capacity bought at contract sign | Paid whether consumed or not |
| Workers | Each consumes a fraction of a vCore | Sizing is where the over commitment hides |
| Overage | Prices at the on contract rate outside the pool | The clause is negotiable |
| Runtime and API management | Bundled with the pool on most editions | Rarely the reason to step up a tier |
| Design and exchange | Bundled with developer seats and asset publishing | Check what the current edition already includes |
Two structural facts decide most of the bill, and both are set before any discount conversation.
The pool is committed rather than consumed, so an estate sized to a peak that occurred once is paying for that peak every month of the term, and in our file that gap averaged 28 to 44 percent against actual utilization.
And the edition floors mean the tier decision carries a vCore minimum as well as a feature set, so stepping up for one capability buys a floor alongside it.
Both are corrected by measurement rather than negotiation: trailing 90 day utilization for the pool, and actual feature consumption per team for the edition. The related integration cost mechanics sit in the MuleSoft licensing guide.
Three levers, measured before they are argued
- Right size the vCore pool against trailing 90 day utilization, not against peak, which returned 22 to 38 percent of the platform line on estates that had not refreshed in eighteen months.
- Migrate north south traffic to the decoupled gateway, which separated gateway capacity from the committed pool on two thirds of estates and recovered 18 to 32 percent of vCore spend.
- Score the edition against actual feature consumption, since most buyers sat on the top tier for one capability available as a discrete add on, and the step down returned 14 to 28 percent.
- Anchor the uplift cap, because the default sits between five and twelve percent under the current playbook and caps hold when they are asked for in advance rather than at signature.
- Negotiate the overage clause, which prices consumption outside the pool at an on contract rate that is itself negotiable rather than fixed.
The integration cost negotiation brief
vCore mechanics, the gateway decoupling, edition floors, and the renewal levers that move an integration platform contract.
Get the white paper →What changed when the renewal moved
The pricing model survived the acquisition and the renewal posture did not, which is the single most useful sentence for a buyer entering this cycle.
Renewals now run through the Salesforce account team and follow the Salesforce uplift playbook, which means the negotiation looks like a Salesforce negotiation rather than an integration platform one: a default uplift in the five to twelve percent range, anchored caps that hold when asked for.
A preference for multi year structures, and a six month preparation window the vendor now expects rather than tolerates.
Buyers who plan on the old timetable arrive with less runway than the process assumes and negotiate accordingly. One inherited concept travels with the ownership change and deserves attention.
External applications consuming your integration APIs can trigger downstream indirect access exposure on the Salesforce side, which turns an architecture decision made by an integration team into a licensing position owned by nobody.
Map which external consumers touch which APIs before the renewal, because that map is either evidence or a gap depending on when it is produced.
Underneath all of it, the order of work matters more than any individual lever: measure utilization and feature consumption first, migrate the gateway capacity second.
And only then open the commercial conversation, because each measurement removes quantity from the thing being priced rather than asking for a discount on a number nobody has tested.
The wider Salesforce context sits in the Salesforce practice.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across MuleSoft renewals, 2024 to 2025
Across roughly 15 to 25 MuleSoft renewals we benchmarked or ran between 2024 and 2025, three patterns recurred, and all three were measurement problems before they were negotiation problems:
Platform line returned by sizing the vCore pool to trailing 90 day utilization on estates that had not refreshed their commit in over eighteen months.
Total vCore spend recovered by moving north south traffic onto the decoupled gateway, which separates that capacity from the committed pool.
vCore over commitment against actual utilization averaged 28 to 44 percent, because most enterprises had sized to peak rather than to trailing average.
The gateway transition recovered 18 to 32 percent of the vCore envelope on estates that deployed it, decoupling gateway capacity from the platform pool on roughly two thirds of those reviewed.
And bundle edition mismatches drove the largest single source of unnecessary spend, with most buyers on the top tier for a single feature procurable as a discrete add on.
The buyer side move is to measure first and negotiate second, then anchor the uplift cap on a six month runway rather than a six week one.
Your first five moves
- Pull trailing 90 day utilization and size the vCore pool to it, not to the peak that justified the original commit, which returned 22 to 38 percent of the platform line in our file.
- Test whether north south traffic can move to the decoupled gateway, since that separation recovered 18 to 32 percent of vCore spend on the estates that deployed it.
- Score every team against actual feature consumption and step the edition down where the top tier is carried for one capability available as an add on.
- Map which external applications consume your APIs before the renewal, because downstream indirect access exposure is either evidenced or a gap depending on when the map is produced.
- Open the renewal on a six month runway and anchor the uplift cap, since the default sits between five and twelve percent and caps hold when asked for in advance. The Salesforce practice runs the sizing with you.
Frequently asked questions
How is MuleSoft licensed?
On committed vCore pools. A vCore is roughly one CPU core of platform capacity, buyers commit to a pool at contract sign, and the pool covers deployments across the term.
The pool is paid for whether or not it is consumed, and consumption outside it prices at an on contract overage rate that is itself negotiable.
How much over commitment is typical?
Between 28 and 44 percent against actual utilization across the estates we benchmarked, because most enterprises sized the pool to peak rather than to trailing average.
Right sizing against measured trailing 90 day utilization returned 22 to 38 percent of the platform line on estates that had not refreshed their commit in more than eighteen months.
What did the gateway release change?
It decoupled gateway capacity from the platform vCore pool, which moved the cost lever.
On roughly two thirds of the estates we reviewed, migrating north south traffic to the newer gateway separated that capacity from the commitment, and buyers who did so recovered 18 to 32 percent of total vCore spend.
Why do edition mismatches cost so much?
Because the editions bundle features at different vCore floors, so a tier decision carries a capacity minimum as well as a feature set.
Most buyers sat on the top tier for a single capability that could have been procured as a discrete add on, and scoring the estate against actual feature consumption returned 14 to 28 percent.
How has the renewal changed since the acquisition?
The pricing model survived and the renewal posture did not.
Renewals now run through the Salesforce account team on the Salesforce uplift playbook, with a default uplift between five and twelve percent, a preference for multi year structures, and a six month preparation window the vendor expects rather than tolerates.
Is the renewal uplift negotiable?
Yes. The default sits between five and twelve percent under the current playbook, and anchored caps hold when they are asked for in advance rather than raised at signature.
Plan the ask on a six month runway, because a cap requested late is a cap requested without the preparation that makes it credible.
Does MuleSoft usage create indirect access exposure?
It can. External applications consuming your integration APIs may trigger downstream indirect access exposure on the Salesforce side, which turns an architecture decision made by an integration team into a licensing position nobody owns.
Map which external consumers touch which APIs before the renewal, so the map is evidence rather than a gap.
5 Ways to Win Your Salesforce Negotiation
Agentforce 360, Data 360, and the early renewal play. Einstein 1 became the Agentforce editions and every quote now references the higher price book. What to separate, what to cap, and why the early renewal is their trade to pay for.
