Independent MuleSoft support

MuleSoft Support for CloudHub, Runtime Fabric and On-Premise Mule Runtimes

Last reviewed by Tyler Eastridge

AceMQ gives integration teams 24/7 support for Mule applications on CloudHub, Runtime Fabric and on-premise runtimes, alongside your MuleSoft subscription. Most calls start with one of three problems: out-of-memory errors on large payloads, workers restarting with no application error, or DataWeave transformations that take minutes. Compare the options in MuleSoft support options.

24/7 MuleSoft support with response targets from 15 minutes, by plan.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ MuleSoft consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Problems we fix every week on MuleSoft

Eight Mule failures that come up again and again, each with the Runtime Manager view, connector setting or DataWeave pattern an engineer checks first.

Common MuleSoft production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
OutOfMemoryError on large payloadsRead heap in the Runtime Manager or JMX against payload size. Loading a whole file into memory as a byte array defeats streaming; use repeatable streams with a bounded buffer and maxInMemorySize.
CloudHub worker restarts without an app errorCheck worker CPU and memory against the vCore size and the Runtime Manager restart reason. Container memory is smaller than the JVM heap sizing suggests.
DataWeave transformation takes minutesLook for reduce and nested map on arrays, repeated filter inside loops and flatten on large inputs. Streaming with deferred=true and lookups built once change run time by an order of magnitude.
Backend calls time out with the backend idleCheck HTTP connector pool size, response timeout and keep-alive. An exhausted pool, not the backend, produces timeouts.
VM queue depth grows in the process layerCompare the flow's max concurrency with queue consumers and the thread pool strategy.
Runtime Fabric deploy never readyCheck the readiness probe, resource requests against node capacity and the image pull path.
Duplicate messages after a restartUse idempotent message validators with a persistent object store and look at redelivery settings on JMS or Anypoint MQ.
API Manager policy has no effectConfirm the policy applies to the right API instance and that the gateway synced; check policy ordering.

Every P1 report names the flow, connector or runtime setting that failed and the change that keeps it from repeating.

Orders waiting behind a stalled Mule flow? Request a quote and a senior engineer replies inside the hour.

Contact Us

Deployment coverage

Which Mule deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat MuleSoft coversExcluded
CloudHub and CloudHub 2.0App behaviour on workers, replicas and vCores, networking, Runtime Manager diagnosticsThe cloud platform and product defects, per your subscriptionPlatform faults inside MuleSoft's cloud
Runtime Fabric (EKS, AKS, GKE, OpenShift, self-managed)Deployment readiness, resource sizing, ingress, upgrade planningProduct defectsYour Kubernetes control plane
On-premise Mule runtimes and clustersStandalone and cluster operation, JVM tuning, logging, upgradesProduct defectsOS and hardware faults
Mule 3 and Mule 4 applicationsDay-to-day operation, tuning, incident response on versions you runPer your MuleSoft entitlement and version policyProduct patches by third parties
Anypoint API Manager and policiesPolicy design, ordering, gateway syncThe productYour API design decisions
Anypoint MQ, VM, JMS and Kafka connectorsThroughput, redelivery, dead-letteringAnypoint MQ as a productBroker faults outside our scope

Support options

MuleSoft support vs independent support: an honest comparison

MuleSoft support is bought as part of your subscription. MuleSoft's own support page describes subscriptions that combine software with support and documentation but does not list response times; those sit in separate Salesforce legal documents (mulesoft.com/support, read 17 Nov 2026; MuleSoft subscription plans, effective 27 June 2025). Our full options write-up is at MuleSoft support options.

MuleSoft support
Independent support from AceMQ
Product defects and patchesYes; only MuleSoft ships product fixes
Product defects and patchesWe prove the defect, give the workaround and work the case with you
Application and DataWeave performanceNot the core of a product support case
Application and DataWeave performanceYes, named engineers who learn your flows
Cost and vCore reviewYour account team
Cost and vCore reviewA named deliverable
Where AceMQ is not the right fitEntitlement, licensing questions and platform defects stay with MuleSoft. Do not drop your subscription cases: open them there and bring us in for the operations work
Where AceMQ is not the right fit

What's Included

Everything in your MuleSoft support contract

Flows, connectors, DataWeave scripts, worker sizing and API Manager policies fall under one contract, whichever Mule runtime hosts them.

  • 01

    Emergency Incident Response

    Workers restarting, integrations stalled, queues backing up, or a deployment that will not come healthy. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.

  • 02

    vCore & Worker Cost Governance

    Worker sizing against measured heap and throughput, consolidating over-provisioned apps, and identifying integrations whose vCore consumption is driven by a fixable memory or streaming problem rather than real load.

  • 03

    Performance & Memory Tuning

    Streaming strategy selection, DataWeave profiling and rewrite, connection pool sizing, thread and concurrency configuration, and heap analysis against real production payload profiles.

  • 04

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the flow, connector, or runtime change that prevents recurrence. Delivered as standard, not on request.

  • 05

    Connectors & Backend Integration

    JMS, Anypoint MQ, database, SAP, Salesforce, and HTTP connectors configured for the delivery semantics, retry behaviour, and error handling your integrations actually need under failure.

  • 06

    Upgrades & Deployment Models

    Mule runtime upgrades, migration between CloudHub, CloudHub 2.0, Runtime Fabric, and on-premise runtimes, and moving integrations off MuleSoft entirely where that is the right commercial call.

Why AceMQ

Why integration teams add AceMQ to their MuleSoft subscription

  • We Treat vCore Spend as an Engineering Problem

    Worker sizing is usually set once, during a project, and never revisited. We measure real heap and throughput, fix the memory behaviour that forced the oversizing, and document the change so the reduction survives the next release.

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your flows, your connectors, and your backend systems — so a P1 call starts with diagnosis, not twenty minutes of you explaining your integration estate.

  • Deep on the Messaging Behind the Flows

    Most Mule incidents are really messaging incidents — acknowledgement modes, transaction boundaries, redelivery, ordering, and queue backpressure. Enterprise messaging is our core discipline, not adjacent knowledge.

  • No Tier-1 Triage Layer

    You reach a senior engineer directly by phone, email, or Slack. No help desk collecting information to pass along, and no escalation approval standing between you and someone who can actually fix it.

  • We Debug the Layers the Vendor Won't

    MuleSoft supports the Anypoint Platform. Your flows, DataWeave, connector configuration, streaming strategy, worker sizing, and the backend systems you integrate are yours — and that is where incidents originate.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am incident is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

Mule runtimes we support

CloudHub 2.0 workers, Runtime Fabric clusters, Mule runtimes on your own servers, and backends that are only reachable through a restricted network path.

  • CloudHub & CloudHub 2.0
  • Anypoint Runtime Fabric
  • On-premise Mule runtime
  • Mule 4.x runtimes
  • Kubernetes & OpenShift
  • AWS (EC2, EKS)
  • Microsoft Azure (AKS)
  • Google Cloud (GKE)
  • Anypoint MQ & JMS brokers
  • Bare metal & on-premise
  • Air-gapped / restricted egress backends
  • Hybrid cloud

Version coverage

Versions we support

Versions we support
ComponentWhat we support
Mule runtimeMule 4.x releases you run, and Mule 3.x applications still in production
Anypoint Studio and Maven buildsThe tooling your CI uses
DataWeaveDataWeave 2.x scripts and DataWeave 1.0 in Mule 3 apps
ConnectorsHTTP, Database, JMS, Kafka, Salesforce, SFTP and other connectors you use

Mule runtime

Mule ESB (Mule runtime community edition) support

AceMQ supports the Mule runtime on premise: standalone runtimes and clusters, Mule 3 and Mule 4 applications, on the version you run, 24/7 with response targets from 15 minutes, by plan. Cover is operations: JVM tuning, logging, upgrades and incident response. If you run a community edition runtime, name that build when you ask for a quote so we can confirm scope.

Common calls on Mule runtimes are out-of-memory errors on large payloads, workers restarting with no application error, and DataWeave transformations that take minutes. Where you hold a MuleSoft subscription, entitlement questions and product defects stay with MuleSoft.

For runtime upgrades or a move between deployment models, see MuleSoft consulting.

Escalation Path

Your first hour of a MuleSoft outage

Whoever answers has read Mule logs before, so the opening question is which flow, connector or policy misbehaved rather than how your Anypoint organization is laid out.

  1. From 15 min (by plan)first responseEmergencyProduction outage: CloudHub workers in a restart loop, Runtime Fabric deployments never turning ready, core APIs returning errors to customers
  2. 1 hourfirst responseCriticalSerious degradation: out-of-memory restarts on large payloads, VM or Anypoint MQ queues backing up, backend calls timing out while the backend is idle
  3. 4 hoursfirst responseHighDuplicate messages after a restart, API Manager policy not applying, DataWeave transformations that take minutes
  4. Next Dayfirst responseStandardQuestions on streaming strategy, vCore sizing, connector settings, moving between deployment models and runtime upgrades

Targets are set per plan, so a stalled production API and a DataWeave question never share a clock.

Rather have a named Mule engineer who already knows your Anypoint estate? Ask for a quote or book a call.

Contact Us

Pricing

What does AceMQ MuleSoft support cost?

MuleSoft support from AceMQ typically costs $24,000–72,000 a year. Where a contract lands depends on how many production applications and vCores you run, the mix of CloudHub, Runtime Fabric and on-premise runtimes, and the response plan you pick.

All prices are in US dollars (USD). Response targets begin at 15 minutes by plan, 24/7, and quote requests get an answer within 1 hour. Covering more than one technology with us earns a multi-technology discount.

Support In Practice

Mule incidents we have worked through

MuleSoft support and remediation work from AceMQ. Each card links to the full write-up: the integration estate, what AceMQ diagnosed or changed, and the result.

1 / 4 case studies

All use cases

Support options

Four tiers of MuleSoft support.

AceMQ offers MuleSoft support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for the integrations your team runs, proactive monitoring that finds memory, pool and vCore problems first, Anypoint operated in your own MuleSoft tenant, and the runtimes and pipelines around Anypoint run on AceMQ infrastructure. Mule 3 and Mule 4 are covered.

  • Tier 1

    MuleSoft 24/7 Support & Incident Management

    Your developers own the flows, we take escalations

    Best for: Teams with Mule developers in place who want a senior engineer for incidents that start in flows, not in the platform.

  • Tier 2

    MuleSoft 24/7 Support with Proactive Monitoring

    Scheduled reviews of workers, flows and policies

    Best for: Teams paying for vCores they suspect are oversized, or learning about memory trouble only after a worker restarts.

  • Tier 3

    Managed MuleSoft on Your Infrastructure

    We operate your Mule runtimes where they sit

    Best for: Organizations running Runtime Fabric or on-premise Mule runtimes that have to stay inside their own network.

  • Tier 4

    Fully Managed MuleSoft on AceMQ Infrastructure

    AceMQ runs your Mule integrations as a service

    Best for: Teams that want integrations kept healthy without hiring runtime administrators of their own.

FAQ

MuleSoft support questions

Still have questions about MuleSoft? Email an Expert

Who provides enterprise support for MuleSoft?

MuleSoft provides support under your subscription. Independent providers such as AceMQ add 24/7 operational support for the runtimes and applications you run. AceMQ costs $24,000 to $72,000 a year (USD), set by SLA, scope and deployment.

Do we still open cases with MuleSoft if we use AceMQ?

Yes. Product defects, entitlement and licence questions stay with MuleSoft. We tell you when a case belongs there and bring the evidence.

Why does our Mule app run out of memory on large payloads?

Usually a payload read fully into memory, or a non-repeatable stream consumed twice. Bounded streaming and a correct buffer size fix it.

Our DataWeave transformation is slow. Is that fixable?

Often yes, by restructuring reduce and nested map patterns and streaming the input.

Can you reduce our vCore consumption?

We compare worker size with CPU and memory use per application and propose consolidation or right-sizing. See /blogs/mulesoft-support-options/ for how the options compare.

Do you support Mule 3 applications and older Mule 4 runtimes?

Yes. We work on the runtime version you actually run, so a Mule 3 application or an older Mule 4 runtime gets the same incident response, tuning and root-cause analysis as a current release.

Do you support on-premise and Runtime Fabric as well as CloudHub?

Yes. A Runtime Fabric deployment that never turns ready, an on-premise runtime running out of heap and a CloudHub 2.0 worker that keeps restarting are all handled under the same contract, whichever model hosts the application.

Who offers MuleSoft consulting and professional services?

AceMQ offers an application and DataWeave performance review, a vCore and cost review and an upgrade plan as named deliverables.

How fast will you respond?

Response targets begin at 15 minutes on the top plans, at any hour. Picture a Sev 1 where CloudHub workers restart every few minutes: an engineer joins a bridge, compares worker memory with the restart reason, and a written root cause follows. P2 is 1 hour, P3 4 hours, P4 the next business day.

Can we hire AceMQ for one Mule project instead of a contract?

Yes. A DataWeave performance review, a vCore sizing review or a runtime upgrade plan can be bought on its own. If incidents keep arriving, most teams then move to an annual plan with named engineers and 24/7 cover. Scope and price are agreed before any work starts.

How is MuleSoft support priced?

Plans run $24,000 to $72,000 a year (USD). We scope by the number of production Mule applications and vCores, whether they run on CloudHub, Runtime Fabric or your own servers, and how fast you need an answer. Describe the estate and a quote comes back within 1 hour.

Let's talk

When an Integration Stalls, Every System Behind It Waits

Send one failing flow and its Runtime Manager log and we will reply with the cause within 1 hour.

A senior MuleSoft engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email a MuleSoft Architect