Azure API Management
First with 4.5 out of 5 and ahead of MuleSoft in every area. Best for teams on Azure.
Salesforce's platform was easy to learn and easy to leave in our test, but its gateway was average and plans start at $2,000 a month.
Most companies don't shop for MuleSoft because they want an API gateway. They buy it to make Salesforce, their finance system, their warehouse software and a dozen other apps talk to each other, and API management comes along in the package. We wanted to know how good that bundled gateway is, so we ran it through the identical routine our API management reviews all follow.
The answer: perfectly ordinary. Over 14 days, 18 of 30 gateway checks came back as expected, 10 of 15 usage limits held, and about 92 milliseconds were added to the slowest requests. Where it shone was getting started and getting out: a first working request in 110 minutes, solid documentation, and an export that needed just one piece of manual rework.
It earned 3 out of 5, third of seven. It makes sense for large organisations already using MuleSoft or Salesforce for integration. As a standalone gateway, its $2,000-a-month starting price is hard to justify.
Developer experience and features tie for its best marks at 3.5. Performance trails at 2, mainly because of the added delay.
Overall: 3 out of 5 (the five parts averaged, then rounded to the closest half).
Cheaper gateways matched or beat it in our test. Check them before signing a yearly contract.
Big companies run dozens of separate systems: a customer database, an accounting package, an online shop, a warehouse tool. Each holds part of the picture, and staff waste hours copying data between them. An integration platform is plumbing that connects them so information flows automatically. MuleSoft, owned by Salesforce since 2018, is one of the best-known.
Those connections are often built as APIs, the standard way one program requests data from another. Once you have many APIs, you need rules about who may use them and how often. MuleSoft's API Manager and its gateway provide that layer: they check credentials, apply usage limits and log traffic.
So MuleSoft is less a gateway than a whole workshop with a gateway inside. That's why it's priced and sold differently from the lighter developer tools we review, and why most buyers come to it through an enterprise sales team rather than a sign-up page.
In 2026 MuleSoft moved new customers to packages paid for with Mule Credits. Think of credits as a prepaid balance shared across MuleSoft's products: each package comes with some, and using features spends them. A dashboard shows what you've used, what's left and a forecast, and can alert you before you run out.
The package aimed at API work is called Govern APIs and AI. Others cover managing AI agents, connecting apps, processing documents, or everything at once. If you use more than your credits cover, you buy more, and the price per credit drops the more you buy.
Because much of the advice online predates this change, treat older price guides with caution.
Here's the path in four steps, as a newcomer would experience it.
1. Build or register. Either create an API in MuleSoft's Anypoint tools or point its gateway at an API you already run elsewhere.
2. Attach policies. In API Manager, add the rules: who needs a key, how many calls per minute, which requests to block.
3. Publish. List the API in Exchange, MuleSoft's catalogue, so other teams or partners can find and request access.
4. Track spending. Keep an eye on the credits dashboard, since gateway traffic and other features draw on the same balance.
These are the pieces that matter if you're evaluating MuleSoft for API work.
The single control screen for policies on your APIs, and on traffic from AI agents too.
The gateway that enforces those policies across environments; it replaces the older Flex Gateway.
Checks every API against your company's design and security rules before it goes live.
Tests an API before release to catch changes that would break apps already using it.
A searchable library of your APIs, with portals for internal teams and partners.
Handles traffic using the MCP and Agent2Agent standards that AI agents use to call tools.
MuleSoft was on our test bench from October 3 to October 16, 2026. All seven gateways guard an identical trio of sample APIs, and for each we record the same measures: time to a first working request, how many gateway checks pass, how well usage limits hold, the delay added and how easily you could leave. The testing method page has the details.
Set-up took 110 minutes following MuleSoft's documentation, slower than Azure's 67 but faster than the remaining five tools. Seven of ten documentation checks passed, and four of the five sample set-ups ran as printed, which made a big platform less daunting than we expected.
The gateway itself was middle of the road. It passed 18 of 30 checks, the same as four other tools. Of our 15 usage-limit rules, 10 behaved correctly and 5 needed fixing. It added about 92 milliseconds to the slowest 5% of requests. Your users won't notice that on a single page load, but Azure added a quarter as much.
Leaving was the pleasant surprise. MuleSoft passed 4 of 5 export checks and moving our set-up elsewhere needed only 1 manual rebuild, so the big contract doesn't lock you in as tightly as you might fear.
| Measure | Result | Plain-English meaning |
|---|---|---|
| First working request, docs only | 110 min | Plan an afternoon to get started. |
| Gateway checks, three APIs | 18/30 | Six in ten behaved as configured; test before going live. |
| Docs and sample set-ups | 7/10 doc checks; 4/5 samples work | Clear, mostly accurate documentation. |
| Delay added, slowest 5% | ≈92 ms | Unnoticeable to most users, but far from the best. |
| Export and leaving | 4/5 checks; 1 manual migration | Little rework if you move away. |
In short, MuleSoft is pleasant to work with and easy to leave, but its gateway performs no better than tools that cost a fraction as much.
Tested October 3, 2026 to October 16, 2026.
110 minutes to a first request and documentation that passed 7 of 10 checks. Large platforms are often far harder.
4 of 5 export checks and a single manual rebuild. You can leave without starting from scratch.
Design rules, pre-release testing and a catalogue come with the platform, which big organisations otherwise buy separately.
18 of 30 checks, 10 of 15 usage limits and about 92 ms of added delay put it in the middle of the pack.
$2,000 a month billed yearly for the API package, and the other packages aren't priced publicly.
Usage draws on a shared credit balance, so under-estimate and you'll be buying more mid-contract.
These figures come from MuleSoft's pricing page as we read it on November 3, 2026. The page blocked our automated recheck on November 11, so confirm them with MuleSoft before you budget.
There's no free plan. The Govern APIs and AI package starts at $2,000 a month, billed yearly, with credits included. Manage Agents, Connect Apps, Process Documents and Access Everything have no published prices. You also choose how you buy credits: Pre-Purchase with no minimum, Pre-Commit with a minimum of $50,000 a year paid monthly, or Unlimited at a custom yearly price. Per-credit rates fall by up to 90% at higher volumes.
A 30-day free trial covers the full portfolio; we couldn't confirm whether it needs a card. We found no published refund or cancellation terms, so get them in writing from sales.
Prices as read on November 3, 2026; MuleSoft's page couldn't be rechecked on November 11.
Azure API Management took first place on 4.5 out of 5 and is far cheaper to start: its Consumption tier includes the first million calls each month, and the Developer tier is $48.04 a month. It lacks MuleSoft's business-app connectors, though. Kong matched MuleSoft's 3 out of 5, with an open-source core and paid plans from $25 a month.
Apigee, Google Cloud's enterprise gateway, scored 2.5 and costs about $365 a month per region. For every score and price in one place, see our gateway ranking.
| Gateway | Entry price | Suited to |
|---|---|---|
| MuleSoft | $2,000 a month, billed yearly | Enterprises combining integration and API control |
| Azure API Management | Free tier; Developer $48.04 a month | Teams on Microsoft Azure |
| Kong | $25 a month | Platform teams on Kubernetes |
| Apigee | About $365 a month | Large organisations on Google Cloud |
MuleSoft is a mature product with Salesforce behind it, so it isn't going away. Its gateway supports zero-trust security rules across environments. We couldn't confirm certifications, data retention or whether customer data trains AI, so raise those in procurement if they matter.
The bigger risks are in the contract. Packages are billed yearly, overages mean buying more credits, and Pre-Commit commits you to at least $50,000 a year. Run a realistic credit forecast during the trial before you sign.
Set credit-usage alerts on day one, so a busy month doesn't turn into a surprise invoice.
Reviewers rate MuleSoft highly. On Gartner Peer Insights it had 4.6 out of 5 across 394 reviews, and on G2 the Anypoint Platform had 4.5 out of 5 across 774, both as read on November 3, 2026. We couldn't recheck them on November 11.
Praise centres on the huge range of connectors and on having one control plane that shows everything. Complaints focus on licence cost, a steep learning curve once you go past the basics, and the complexity that comes with such a large platform.
Our results fit both sides: the documentation made starting easier than expected, and the price is hard to defend when the gateway alone performs like cheaper rivals.
One tool beat MuleSoft, two matched its score and two finished below it.
First with 4.5 out of 5 and ahead of MuleSoft in every area. Best for teams on Azure.
Second on 3 out of 5, with the most usage limits enforced after Azure (11 of 15). Popular on Kubernetes.
Also 3 out of 5, with fewer features. Really a single API for email, calendars, contacts and tasks.
2.5 out of 5, behind MuleSoft on developer experience, features and value. Suits large Google Cloud users.
2.5 out of 5. Free open-source gateway, but slower to set up (140 minutes against MuleSoft's 110).
Only if you need the whole platform. For an enterprise connecting many business systems, especially around Salesforce, MuleSoft's gateway is a reasonable part of a larger purchase: easy to learn, easy to leave, with governance built in. Those strengths earned it 3 out of 5 and third of seven.
If all you need is a gateway, the numbers don't add up. It passed 18 of 30 checks and enforced 10 of 15 usage limits, no better than cheaper tools, at a starting price of $2,000 a month. Azure API Management did better for much less, and Kong matched it with public prices from $25.
MuleSoft suits large Salesforce-centred organisations buying integration and API governance together; teams that only need a gateway should look elsewhere.
Seven gateways protected the same three APIs. Compare their set-up times, checks, delay and prices.
If you use MuleSoft, or work there, and think we got something wrong, email us. Tell us what you saw and attach screenshots if you have them. We'll take another look and update the review if it changes our findings.
When we read MuleSoft's pricing page on November 3, 2026, the Govern APIs and AI package started at $2,000 a month, billed yearly, with Mule Credits included. Other packages had no public price, and the Pre-Commit buying option had a $50,000-a-year minimum. The page couldn't be rechecked on November 11.
There's no free plan, but there is a 30-day free trial covering the full portfolio. We couldn't confirm whether it requires a card. Use the trial to estimate how many credits you'd actually use.
They're a shared balance you spend across MuleSoft's products. Each package includes some, you can buy more if you run out, and the price per credit falls as you buy more, by up to 90%. A dashboard tracks use and forecasts what's left.
It's an average one. In our test it passed 18 of 30 gateway checks, enforced 10 of 15 usage limits and added about 92 ms to the slowest requests. Its strengths are documentation, governance features and low lock-in rather than raw gateway performance.
Salesforce bought MuleSoft in 2018. That's why it connects so closely with Salesforce products and why many of its customers already use Salesforce.
Our test lasted 14 days, starting October 3, 2026 and ending October 16, 2026. We followed MuleSoft's documentation to put three sample APIs behind its gateway, then timed the set-up, worked through 30 gateway checks plus 15 limit rules, measured delay and tried exporting everything.