01
It's a platform, not a gateway
The Anypoint Platform
Mulesoft is not just an API gateway. It's an integration platform where the gateway is one component. Get this right before evaluating: you're buying ESB-class integration tooling, with API management layered on top.
| Component | What it is | Why you care |
|---|---|---|
| Design Center | Visual API design (RAML/OpenAPI) + Mule flow builder. | Specs live alongside flows. RAML is preferred but OpenAPI 3 is fully supported. |
| Anypoint Studio | Eclipse-based IDE for Mule developers. | The serious dev work happens here, not the browser. |
| Exchange | Internal marketplace for APIs, templates, connectors, assets. | Reuse engine — APIs are products, connectors are LEGO bricks. |
| API Manager | Apply policies, manage SLA tiers, route to upstreams. | The "API management" of Anypoint API Management. |
| Runtime Manager | Deploy + monitor Mule applications (apps = APIs + flows). | Operational pane of glass for production. |
| Anypoint Monitoring | Dashboards, alerts, log search, custom KPIs. | Built-in observability — no separate ELK setup needed. |
| Anypoint MQ | Managed message broker (Mulesoft's own SQS-like). | For async integrations between Mule apps. |
| Connectors | Hundreds of pre-built integrations — 500+ across the ecosystem, 250+ in Anypoint Exchange (Salesforce, SAP, NetSuite, JDBC, etc.). | The reason mid-market enterprises buy Mulesoft. |
▸ Critical framing
If you only need to put a gateway in front of REST services, Mulesoft is over-platformed for the job.
The platform's strength is integrating systems that don't speak HTTP: Salesforce, SAP, mainframes, file shares, JDBC, AS400. If your APIs are all clean REST/gRPC microservices already, Kong or Apigee will be a better fit at a fraction of the cost.
02
Where Mule apps run
Deployment targets
Four supported runtimes, each with different operational tradeoffs and pricing units. Pick the wrong one and you'll regret it at renewal.
CloudHub Legacy
CloudHub
The original SaaS runtime
- Hosted by Salesforce
- Pricing unit vCore
- Region choice Limited
- Status Migrate to CH 2.0
CloudHub 2.0 Current
CloudHub 2.0
K8s-based managed runtime
- Hosted by Salesforce
- Pricing unit Replica
- K8s under the hood Yes (managed)
- Multi-cloud regions 20+
Runtime Fabric
RTF
Mule runtime on YOUR K8s
- Hosted by You
- Required for data residency
- Operates your K8s cluster
- Control plane Anypoint SaaS
Flex Gateway
Flex Gateway
Envoy-based gateway-only mode
- Built on Envoy
- Runs anywhere (K8s, Docker, Linux)
- No Mule app server Lightweight
- Use for API GW only, no integrations
▸ Decision heuristic
CH 2.0 for new SaaS work. RTF for on-prem or strict residency. Flex Gateway if you only want the gateway, not the integration platform.
Flex Gateway changed Mulesoft's competitive position. Before it, Mulesoft was over-platformed for pure API gateway use cases. With Flex Gateway (Envoy-based, K8s-native), they can now compete with Kong on lightweight gateway deployments while keeping the option to scale up to full Anypoint later.
03
The secret weapon
DataWeave
DataWeave is Mulesoft's transformation language. It's the single biggest reason mid-market enterprises pick Mulesoft over alternatives. Once you've written DataWeave, every other gateway's transformation story feels primitive.
| Capability | Detail |
|---|---|
| Format support | JSON · XML · CSV · YAML · Java · Avro · Protobuf · COBOL copybook · fixed-width · multipart · Excel |
| Type system | Strong, with schema inference and conversion. Catches errors at design time. |
| Functional model | Map, filter, reduce, group-by, etc. Pure functions, no side effects. |
| Streaming | Process multi-GB files without loading into memory. |
| Performance | Compiled to bytecode; very fast vs interpreted XSL / JS. |
| Reusability | Function libraries + custom data types shared across flows. |
| Tooling | Anypoint Studio has a DataWeave playground with live preview. |
▸ Strategic note
If you have many "integrate two systems with different data models" use cases, DataWeave is the answer no other vendor matches.
Apigee has JS + XSL. Kong has plugins. AWS has VTL. None of them touch DataWeave for transformation-heavy work. If you're doing ETL-meets-API patterns, this is the differentiator.
04
Less abundant than Apigee, still complete
API Policies
Mulesoft uses a policy model on API Manager. Fewer policies than Apigee's library, but covers the essentials. Custom policies are written as Mule modules.
| Policy | Category | Notes |
|---|---|---|
| Client ID Enforcement | Security | API key + secret validation against Anypoint client app. |
| OAuth 2.0 Access Token Enforcement | Security | Validate OAuth tokens from external IdP or Anypoint OAuth provider. |
| JWT Validation | Security | JWKS-based validation. Configure issuer, audience, claims. |
| Basic Authentication | Security | Username/password from LDAP or Mule config. |
| IP Allowlist / Blocklist | Security | CIDR-based at gateway. |
| Rate Limiting | Traffic | Per API or per SLA tier. |
| Spike Control | Traffic | Short-window throttle to smooth bursts. |
| Cross-Origin Resource Sharing | Web | CORS handling at gateway. |
| HTTP Caching | Performance | Response cache with configurable TTL. |
| Header Injection / Removal | Mediation | Add or strip headers in/out. |
| Compliance — Threat Protection | Security | JSON/XML threat protection, SQL injection, payload size limits. |
| Custom Policy | Anything | Mule module — full Mule flow as a policy. |
05
vCore and the CloudHub 2.0 replica
Pricing units
Mulesoft pricing is by capacity unit, not API calls. The unit changes between CloudHub (vCore) and CloudHub 2.0 (replica). Both translate roughly to "how much Mule runtime are you running concurrently".
| Unit | What | Indicative cost | Where used |
|---|---|---|---|
| vCore | 0.1 / 0.2 / 0.5 / 1.0 / 2.0 — Mule runtime capacity unit. | Negotiated — no public list price; deal-dependent estimate | CloudHub (legacy) |
| Replica | vCore-equivalent replica of Mule runtime (CloudHub 2.0), sized small/medium/large. | Negotiated — no public list price | CloudHub 2.0 |
| RTF cores | Capacity on your K8s, billed by Anypoint license. | Negotiated | Runtime Fabric |
| Flex Gateway nodes | Per-node licensing for standalone gateway mode. | ~$5k / node / yr | Flex Gateway only |
| Anypoint MQ | By message volume + storage. | Tiered | Async use cases |
▸ Pricing reality
Mulesoft is enterprise-priced. Total spend typically $200k–$2M+ / year for mid-market deployments.
Salesforce account teams negotiate Titanium / Gold / Platinum bundles. List price means little. Real deals depend on co-term with other Salesforce products. Budget 12+ months for procurement on net-new deals.
06
The honest summary
Strengths & Gotchas
What it does well
- DataWeave. Best-in-class transformation across heterogeneous data formats.
- Hundreds of connectors (500+ across the ecosystem) — Salesforce, SAP, NetSuite, JDBC, AS400, mainframes. The mid-market ESB story.
- Strong SLA tier management with Client ID enforcement and rate limiting per tier.
- Anypoint Exchange for asset reuse is mature and well-loved by API platform teams.
- Salesforce ecosystem integration — natural fit if Salesforce CRM is already in place.
- Flex Gateway as standalone Envoy-based gateway competes credibly with Kong.
What to watch for
- Very expensive. Often 5–10× the cost of Kong/Apigee for similar throughput.
- Learning curve steepens fast. Anypoint Studio + DataWeave + Mule DSL requires real upskilling.
- The platform is best when used holistically. Buying just the gateway = paying for too much.
- Vendor lock-in via DataWeave and connectors. Migration costs are very high.
- vCore → CloudHub 2.0 replica migration is real work; pricing isn't a clean 1:1.
- RAML — strongly preferred by Mulesoft tooling, but the rest of the industry has converged on OpenAPI.
07
In and out
Migration paths
| Direction | Path | Effort |
|---|---|---|
| CloudHub → CloudHub 2.0 | Re-package as CloudHub 2.0 replica deployments. Reconfigure object stores, schedulers. Most Mule code ports cleanly. | Medium |
| CloudHub → Runtime Fabric | Need K8s + RTF installer + cluster operations. Mule apps deploy similarly. | High |
| Anypoint → Kong / Konnect | Hard. DataWeave has no equivalent — must rewrite transformations in Lua or external service. Connector reuse is lost. | Very high |
| Anypoint → Apigee | Policies map roughly. Connectors don't. Transformation rewrite to JS/XSL. Plan multi-year program. | Very high |
| API Manager-only → Flex Gateway | If only using gateway features, Flex Gateway is cheaper. Drop CloudHub runtime, redeploy policies on Flex. | Medium |