M

Mulesoft

Enterprise API management and integration platform

Overview

MuleSoft provides API management and integration software for enterprises. Its main offering, Anypoint Platform, lets organizations design, deploy, secure, govern, and monitor APIs and integrations at scale, connecting applications, data, and devices across environments. The product works through a unified platform that supports API design and development, data mapping, connectors, workflow orchestration, and governance, delivered as a subscription with various tiers and optional professional services. What sets MuleSoft apart is its API-led connectivity approach and emphasis on governance and scalability for large organizations, government agencies, and mid-sized businesses, enabling consistent connectivity and control across complex landscapes. The company aims to help customers accelerate digital transformation, improve productivity, and streamline operations by enabling seamless data and application integration across the enterprise.

Work here?Claim your company

About Mulesoft

Simplify's Rating
Why Mulesoft is rated
B-
Rated B on Competitive Edge
Rated B on Growth Potential
Rated C on Differentiation

Industries

Data & AnalyticsEnterprise Software

Company Size

1,001-5,000

Company Stage

IPO

Headquarters

San Francisco, CA

Founded

2006

Get referred to Mulesoft

See people who can refer or advise you

Simplify Jobs

Simplify's take

What believers are saying

  • October 27, 2026 added Agent Evals, API Evals, and triggered kill switches.
  • Akamai and F5 integrations expand MuleSoft's security footprint across more customer traffic.
  • Salesforce says Agent Fabric handles 1.2 billion daily requests, proving internal scale.

What critics are saying

  • Microsoft Agent 365 and ServiceNow AI Control Tower attack MuleSoft's governance wedge now.
  • Salesforce's fragmented stack risks SKU confusion and slow execution through 2027.
  • If governance commoditizes, MuleSoft becomes a feature inside Salesforce, not a standalone moat.

What makes Mulesoft unique

  • Agent Fabric unifies discovery, governance, and orchestration across non-Salesforce agents.
  • Open Policies federates controls across Azure, Apigee, Kong, and MuleSoft gateways.
  • FedRAMP High on Salesforce Government Cloud Plus strengthens federal deployment credibility.

Help us improve and share your feedback! Did you find this helpful?

Funding

Total Funding

$480M

Above

Industry Average

Funded Over

9 Rounds

Notable Investors:
Acquisition funding comparison data is currently unavailable. We're working to provide this information soon!
Acquisition Funding Comparison Coming Soon

Benefits

  • Health Insurance
  • Professional Development Budget

Growth & Insights and Company News

6 month growth

-4%

1 year growth

0%

2 year growth

0%
MuleSoft
Nov 3rd, 2026
Solace now connects directly inside MuleSoft for real-time, event-driven integration.

Solace now connects directly inside MuleSoft for real-time, event-driven integration. November 03, 2026 | 7 mins read MuleSoft and Solace have collaborated to launch a native, tightly integrated connection between the Solace Platform, with its leading event broker, and MuleSoft, the leading integration and API management platform. Starting today, customers can launch Solace directly from MuleSoft, move between both platforms with a single sign-on, and build event-driven Mule flows with the Solace connector from one environment. As enterprises move AI agents from pilots into production, agents need current data to act on. According to IDC's 2026 State of Real-Time Data study, 85% of organizations say live data is essential to their operations. Organizations with mature real-time data practices are nearly three times as likely to have multiple agents in production. Many enterprises run MuleSoft for integration and Solace for real-time event distribution, and have connected the two with custom code. This new integration connects Solace directly inside MuleSoft, so teams can use event streams in their MuleSoft projects without building and maintaining a separate messaging layer. The Solace integration builds on existing collaboration between the two companies, including full lifecycle AsyncAPI support for Solace in Anypoint Platform. How the integration works. The integration is built on MuleSoft's Anypoint home page. Teams add Solace to their existing integration environment without changing their current architecture. Teams connect to Solace through the Solace connector, which is available in the Anypoint Exchange. The connector lets developers build event-driven integrations directly in Mule flows. Single sign-on lets teams move between MuleSoft and Solace without logging in again. Solace link on Anypoint MQ home page. What this means for Anypoint MQ customers. Existing Anypoint MQ deployments will not be impacted. Solace adds guaranteed delivery and replay, multi-protocol support (MQTT, AMQP, JMS and REST), and an event mesh that routes events across on-premises, multi-cloud and edge environments. You can start with Solace right from the Anypoint home page. Benefits for MuleSoft customers. * Use real-time event streams in MuleSoft integrations without custom code * Run one event backbone across on-premises and multi-cloud environments * Scale beyond lightweight queuing without leaving MuleSoft * Give AI agents built on MuleSoft the context they need to react in real time Benefits for Solace customers. * Connect existing Solace event meshes to MuleSoft projects through single sign-on * Extend Solace event streams to applications and APIs connected through MuleSoft, without building custom code * Give integration teams self-service access to Solace events from the MuleSoft tools they already use Use case examples. Get started. The Solace Connector for MuleSoft is available today in Anypoint Exchange. New single sign-on lets teams move between MuleSoft and Solace Cloud without logging in again, and MuleSoft customers can start with Solace right from the Anypoint home page. The integration is built for teams that use both MuleSoft and Solace. * Get the connector: The Solace Connector for MuleSoft. * Explore more: Visit Solace.com for additional use cases, guidance, and customer stories. About solace. Solace is the real-time data platform for the enterprise. Its event mesh connects applications, clouds, partners and the edge across on-premises and multi-cloud environments, with guaranteed delivery, multi-protocol support and event governance built in. Working alongside API-led integration platforms like MuleSoft, the Solace Platform turns business events into real-time context for applications and AI agents in production. Enterprises including United Airlines, RBC Capital Markets, Bosch, Heineken and Schwarz Group rely on Solace to run mission-critical operations in real time. Solace is headquartered in Ottawa, Canada, with offices around the world. Learn more at solace.com.

VentureBeat
Oct 27th, 2026
Salesforce expands Agent Fabric with AI evaluations to trigger shutdowns when agents fail.

Salesforce expands Agent Fabric with AI evaluations to trigger shutdowns when agents fail. 11:54 am, PT, October 27, 2026 Salesforce is detailing the next phase of its Agent Fabric platform, with evaluations designed to identify malfunctioning AI agents and initiate corrective action, alongside expanded discovery capabilities and previously announced spending and governance controls. The October 27 announcement sets a November beta and January 2027 general-availability target for Agent Evals, which MuleSoft first announced at its annual Dreamforce conference in September. It also outlines API Evals, a forthcoming tool for testing the software connections agents depend on, starts a beta for custom agent scanners and schedules an evaluation-triggered agent kill switch for January. For enterprise buyers, the announcement combines forthcoming capabilities with extensions and existing tools. The basic kill switch became generally available in September, while MuleSoft outlined budget controls, spending dashboards and token-saving features over the summer. The September announcement also described connecting failed evaluations to corrective actions. The broader proposition is to shorten the distance between discovering a problem and addressing it. A company might know that an agent produces incorrect answers or consumes too many resources, but still need to identify its owner, navigate another platform and obtain permission to suspend it. In an interview with VentureBeat, Andrew Comstock, senior vice president and general manager of MuleSoft at Salesforce, described familiar problems behind the company's approach. "I have too many of them. The technologies are totally different. Nothing talks to each other. Everything runs in a silo," Comstock said, describing customer challenges that informed Agent Fabric. Salesforce wants to manage those agents even when customers build them on competing platforms. "I'll emphasize, it's not Salesforce specific. It's across everything," he said. Agent Evals moves toward beta. Salesforce had already described Agent Evals at Dreamforce in September, including generating tests, measuring outcomes against success criteria and connecting failures to remediation. The October announcement adds rollout dates and describes how evaluations can extend beyond testing before deployment to checking agents, language models and Model Context Protocol servers in production. The goal is to identify behavior that falls outside an organization's thresholds and initiate an appropriate response, including approval steps where policy requires them. In Salesforce's illustrative retail scenario, moving an agent to a cheaper model produces worse answers to order-status questions. Evaluations detect the decline and initiate a process to quarantine the agent, obtain approval where required, and revise and retest it. That is a hypothetical workflow, rather than a reported customer result. Comstock said evaluations can also help companies enforce expectations about how agents communicate. A customer-facing agent that should sound upbeat, for example, should not unexpectedly become sarcastic. The forthcoming API Evals tool addresses another part of the system: generating functional and performance tests from API specifications. Both evaluation products are scheduled to enter beta in November and become generally available in January 2027. The kill switch already exists; evaluation-triggered intervention is coming. The kill switch itself is not new to this announcement. MuleSoft introduced the concept in June and made the basic capability generally available in September. It uses gateway controls to block governed traffic, with options to scope an intervention to a request, session, agent or tenant and restore access afterward. That distinction matters: blocking an agent's access through a gateway does not necessarily terminate every process running in the external platform that hosts it. What Salesforce now puts on the January roadmap is a Triggered-Agent Kill Switch, connecting detected problems to policy-driven intervention. The September evaluation preview had already discussed linking failures to remediation; the October announcement supplies a more specific release target for the triggered capability. For buyers, the practical distinction is between an available control for stopping governed activity and a forthcoming mechanism that connects evaluation results to that response. Existing discovery gets a custom extension. Agent discovery also predates today's announcement. MuleSoft described its agent scanners in April as a way to identify agents across supported environments. The addition entering beta today is a Custom Agent Scanner, intended to extend discovery to internal systems, environments behind firewalls and additional platforms. General availability is planned for January. Comstock said the registry does not require customers to relocate their agents to Salesforce. "I'll emphasize, we're not moving the agent; the agent's still running there," he said. "We're just pulling the pointer so that you can get a universal registry across all of your agents." An administrator connects the relevant environments and brings their metadata into a shared registry. Customers do not have to use Agentforce, Salesforce's own agent platform, to use Agent Fabric, Comstock said. He also argued that the need depends more on the diversity of a company's agent deployments than its size. A business using several agent frameworks and providers may encounter coordination problems even without being a large enterprise. Spending controls build on the summer roadmap. The announcement also highlights a FinOps Dashboard, Model Wallet budgets and policies intended to reduce model consumption. These are not all newly introduced features. MuleSoft's August release overview outlined model access, cost optimization, wallets and dashboard improvements. A September explanation of Model Wallet described setting dollar or token budgets by provider or model, with daily, weekly or monthly limits. The controls address a familiar tension: an individual developer may choose an expensive model to get a task done faster, while the organization needs to understand the combined bill. Comstock said visibility should extend beyond reducing total spending to identifying the teams and projects responsible for it. "So it's not just about keeping the cost down. That's obviously part of it, but it's also making sure that you can correlate that with the right teams and projects who are actually driving changes in your organization," he said. Salesforce's October release describes semantic caching, payload compression and response trimming among its optimization techniques. It claims token reductions of up to 75% in test scenarios. That is a vendor test result, not a guaranteed reduction in a customer's overall AI bill. Cross-vendor gateway policies also predate today. Salesforce is also emphasizing Open Policies for applying governance across federated gateways, including Azure, Apigee and Kong. The underlying capability is not making its first appearance today. MuleSoft described Open Policies in September, while its October release notes document the renaming of Universal Policies to Open Policies and related enhancements. For enterprises, the attraction is applying common controls across infrastructure they already operate. Actual coverage still depends on the supported integrations and where traffic passes through enforceable controls. Comstock framed that governance as a prerequisite for broader deployment. "Nowadays, governance is your actual accelerant because you're governed. You can answer better questions. You can feel more confident and comfortable, and that makes you go faster," he said. MuleSoft lists a $2,000 starting price, but evaluation pricing remains unclear. Salesforce's public MuleSoft pricing page lists a starting price of $2,000 per month for the broader portfolio, with Mule Credits used across capabilities. The page's agent-management offering includes Agent Fabric functions such as discovery, orchestration, governance and budgets, but directs buyers to contact sales. The $2,000 figure should therefore not be presented as a confirmed standalone price for the specific Agent Fabric configuration described in this announcement. The pricing material outlines prepaid credit packages, a precommit option with a $50,000 annual minimum and a custom-priced unlimited option. It does not establish a separate public price for Agent Evals or API Evals, or enough detail to calculate what a particular evaluation workload would cost. The $2,000 project budget Comstock used as an example during the interview was hypothetical, not a product-price disclosure. Microsoft, ServiceNow and OpenAI compete for enterprise agent oversight. Agent Fabric sits in a growing market for managing agents across an organization, although competing products combine oversight and execution in different ways. Microsoft Agent 365 is a close comparison on enterprise administration. Microsoft describes an agent registry, access and lifecycle controls, analytics and security integrations with products such as Entra, Defender and Purview. ServiceNow's AI Control Tower similarly targets discovery, observation, governance, security and measurement across vendors. Its announced capabilities include controls for risky activity and visibility into AI costs and business outcomes. OpenAI Frontier is another relevant competitor, with a broader proposition that includes building and operating agents, connecting business systems and context, evaluating performance, and managing permissions. The overlap is in enterprise agent management, even though the scope is not identical to Agent Fabric's emphasis on governing agents across existing environments. Anthropic's Claude Managed Agents overlaps at the infrastructure layer but is a less direct comparison. It provides managed facilities for running agents, including execution environments and orchestration. Agent Fabric's central pitch is discovering and governing agents that may continue running elsewhere. Anthropic publishes a Managed Agents runtime price of $0.08 per active session-hour, in addition to applicable model and tool charges. That is not directly comparable with MuleSoft's portfolio starting price or a negotiated Agent Fabric contract. These distinctions are an interpretation of the vendors' published capabilities, rather than a claim that the products are interchangeable. An enterprise could need both an agent runtime and a separate governance layer, depending on integration support and its existing infrastructure. What buyers can use - and what remains ahead. The most immediate addition in this announcement is the Custom Agent Scanner beta. The basic kill switch and highlighted spending controls are already generally available. Agent Evals and API Evals are scheduled for beta in November, with general availability in January 2027. The custom scanner is also scheduled for general availability in January, alongside the Triggered-Agent Kill Switch. For buyers evaluating the announcement, the central question is whether Salesforce can connect discovery, testing, spending visibility and enforceable intervention across the agents they actually use. The forthcoming releases will determine how much of that workflow can operate as a connected system.

RAVA Global Solutions
Oct 26th, 2026
Salesforce consulting vs implementation vs integration:

Salesforce consulting vs implementation vs integration: Ask a few firms what a MuleSoft partner does and you will hear the same words in a different order: consulting, implementation, integration. Some firms treat them as three separate jobs, others as three names for the same one. If you are about to hire help, it is worth knowing which job you are actually buying. The short answer: a consulting partner decides what should be built and who owns it. An implementation partner builds and secures it. An integration partner connects it to the systems it has to talk to. Most firms do more than one, and most projects need all three. As a MuleSoft integration partner, Rava Global Solutions organize its own services around the same jobs, and a table further down shows how. Follow one API from idea to production. Say the sales team wants to see order status from the ERP inside the CRM, and the customer portal team wants the same information. Here is who does what. Who decides: the consulting partner. Before anyone builds anything, someone has to ask whether this should be one reusable API or two separate connections. That is the consultant's job. They agree what the API should return, who owns it, who is allowed to use it and what good looks like. They also check whether MuleSoft is the right tool at all. Its post on MuleSoft versus traditional integration tools covers that question. A good consultant sometimes decides not to build something: if only one team and one system are involved, a simpler tool may do. The result is a short plan and a design the builder can work from. Who builds: the implementation partner. The implementation partner builds the API on MuleSoft's Anypoint Platform, following the layered approach MuleSoft calls API-led connectivity. They write the specification first, build the flows, apply the security rules (who may call the API and how often), test it with realistic data, and deploy it through test and production environments. The result is a working, secured, documented API, with the code stored somewhere you control. Who connects: the integration partner. An API on its own doesn't move any data. The integration partner connects it to the ERP, the CRM and the portal, and maps the fields so that an order number or a status means the same thing everywhere. They plan for the awkward moments, such as the ERP being down for maintenance, and set up alerts so someone is told when a flow fails. Common ways of doing this are covered in its guide to the top integration patterns in MuleSoft. After launch, someone has to keep it all healthy. That is support, covered below. The three partner types at a glance. | Partner type | The question they answer | Typical deliverables | What breaks if you skip it | | Consulting | What should Rava Global Solutions build, who owns it, and is MuleSoft the right tool? A plan, an API design, ownership and security rules, a cost estimate | Duplicate or throwaway APIs, and a platform nobody owns | | Implementation | Is it built properly, secured and tested? Working APIs, security rules, tested flows, environments, documentation | APIs that work in a demo and fail in production | | Integration | Is the right data reaching the right systems, correctly? Connections to each system, mapped fields, error handling, alerts | APIs with nothing behind them, or data that doesn't match between systems | What MuleSoft consulting services cover. Consulting is for the questions that come before the build, and for the point when integrations start multiplying. It typically covers strategy, API design, a review of what you already have, and a cost estimate. You need it before your first project, when each new integration seems to start from scratch, or when a project has stalled. Ask the firm to put its recommendation in writing, including what it would leave out for now. What a MuleSoft implementation partner does. Implementation is the hands-on build: designing and coding the APIs and flows, applying security rules, testing, and deploying through your environments. The question to ask is about reuse. Can the next project use what has been built, or is every API a one-off? Also ask who owns the code at the end and how it will be tested. What a MuleSoft integration partner does. Integration is the connecting work: linking each system, mapping fields so data matches, handling errors and setting up alerts. Look for experience with the systems you actually run, such as your ERP and CRM, not just with MuleSoft in general. Ask how a failed flow is noticed, and who is told. The usual weak point is that nobody watches the connections once the project ends. Where support and training fit. Two things matter after launch, and they cut across all three jobs. Support means watching for failures, handling upgrades and making small changes. Training means your own people can read, change and monitor what was built. If every small change needs a call to the firm that built it, the project hasn't really been handed over. | Your situation | Start with | | Rava Global Solutions is not sure MuleSoft is the right tool | Consulting | | Rava Global Solutions know what Rava Global Solutions want built and need it done properly | Implementation | | Its systems don't share data and people re-key it | Integration | | Rava Global Solutions has APIs, but nobody knows who owns them or whether they are reused | Consulting (a review), then support | | Its integrations break and nobody notices | Support, with an integration review | | Rava Global Solutions still run an older Mule version | Consulting for the plan, then implementation | One firm or several? One firm for all three gives you a single team to hold accountable and fewer gaps between stages. Specialists can bring deeper skill in one area, but you carry the hand-offs. Either way, ask each firm how it will hand over: who owns the code, what documentation you receive, and who can maintain it if you change partners. How its MuleSoft services map to each type. | Service | Partner type | What it covers | | MuleSoft consulting | Consulting | Planning, API design, platform fit and cost estimate | | MuleSoft implementation | Implementation | Building, securing, testing and deploying APIs and flows | | MuleSoft integration | Integration | Connecting systems, mapping data, error handling and alerts | | MuleSoft support and managed services | Ongoing, across all three | Monitoring, fixes, upgrades and training after launch | Its advice before you start. Before you hire anyone, write down the three systems that cause the most manual re-entry in your business. A partner can only tell you whether you need one API or three, and who should own each, if it can see the real list. It also gives you something concrete to compare proposals against. Talk to RAVA. If you are looking for a MuleSoft partner in the USA to plan, build or connect, Rava Global Solutions can start with the systems that cause you the most pain. Talk to its MuleSoft team and Rava Global Solutions will help you work out which type of help you need. Frequently asked questions. What does a MuleSoft partner do? A MuleSoft partner helps you decide what to connect, then designs, builds, secures and supports the APIs and integrations on MuleSoft's platform. Depending on the firm, that can include planning, building, connecting your systems, monitoring and training your team. What is the difference between a MuleSoft implementation partner and an integration partner? An implementation partner builds and secures the APIs on the platform. An integration partner connects those APIs to your systems and makes sure the data arrives correctly. Most projects need both, and many firms offer both. Do I need a MuleSoft partner, or can my developers handle it? A capable in-house developer can handle a small, single integration. A partner earns its fee when many systems are involved, when security and reuse matter, or when you need results faster than hiring allows. A good middle route is to have a partner build the first integrations and train your team to look after them. Who owns the APIs a partner builds? You should. The code, documentation and settings should sit in accounts and repositories you control. Ask this before signing, and make it part of the contract. Enter Name* Enter Email* Enter Website* Enter Your Comment* Search. Tag cloud.

Benzinga
Oct 20th, 2026
v4c promotes Michael Gibson to Chief Executive Officer.

v4c promotes Michael Gibson to Chief Executive Officer. Promotion follows 765% year-over-year revenue growth, investment from Databricks Ventures, and recognition as the 2026 Databricks C&SI Emerging Partner of the Year as v4c continues to expand its world-class Databricks practice v4c.ai, a strategic boutique pure-play Databricks services partner, today announced the promotion of Michael Gibson from Chief Revenue Officer to Chief Executive Officer. Gibson's appointment builds on his leadership in scaling v4c's global sales organization and expands his responsibilities to leadership across the business as the company continues to strengthen its market-leading position in the Databricks ecosystem. As Chief Revenue Officer, Gibson helped scale v4c's global sales organization during a period of 765% year-over-year revenue growth and a 350% increase in its worldwide client base. Central to that expansion has been his focus on aligning v4c's go-to-market strategy with Databricks, building relationships across its field organization, and connecting enterprise customers with the expertise needed to advance their Databricks initiatives. Gibson brings experience on both sides of the enterprise technology relationship: building sales teams within a global software organization and leading growth within technology services. Having been a driving force behind v4c's success, he will build on that foundation with broader responsibility for the company's continued growth and evolution. As CEO, he will work closely with the Board to define v4c's strategy and vision, uniting leaders across all functions to translate that direction into company-wide execution. His focus will span business performance, leadership development, and a culture of collaboration and accountability, while advancing customer success and delivery excellence as v4c enters its next chapter in the Databricks ecosystem. "Mike has been a key driving force behind v4c's meteoric rise, translating our vision into a pace of growth that we believe is unprecedented in the Databricks ecosystem," said Vijay Rao, Founder and Board Member of v4c. "He has built an organization that earns the confidence of Databricks leaders and field teams, wins the trust of enterprise customers, and turns those relationships into shared success. His understanding of where Databricks is going - and how v4c can help our mutual customers get there - will be critical as we continue to expand our capabilities within the ecosystem. The Board is confident that Mike is the right leader to build on this momentum and advance our vision of becoming the world's best Databricks SI." Previously, Gibson served as Senior Area Vice President at MuleSoft, where he led nationwide sales teams serving enterprise customers across banking, retail, consumer goods, and manufacturing. His leadership and performance earned him multiple MuleSoft Owner's Awards for management and culture building, two AVP of the Year honors, and Chairman's Club recognition. His tenure spanned the company's initial public offering and subsequent acquisition by Salesforce, giving him firsthand experience navigating rapid growth and organizational change. That experience also shaped his understanding of how platform providers and services partners work together to earn customer trust, support complex technology decisions, and expand enterprise adoption. Gibson transitions into the CEO role following two major milestones in v4c's relationship with Databricks: an investment from Databricks Ventures and recognition as the 2026 Databricks C&SI Emerging Partner of the Year. Together, these milestones reinforce the strategic alignment between the organizations and provide a foundation for further investment in Databricks expertise, joint field engagement, and global delivery capabilities. "I'm proud of what this team has built and grateful to Vijay, Venkat and the Board for the opportunity to lead v4c," said Gibson. "Databricks is at the heart of our go-to-market, and our vision is to become the world's best Databricks SI partner. That means earning the confidence of Databricks teams in every market we serve and delivering for the customers who trust us with their data and AI priorities. As CEO, I'll focus on deepening those relationships and investing in the people and capabilities that make v4c a partner Databricks can count on as we grow together." In this new role, Gibson will lead v4c's global strategy and execution, deepening strategic alignment with Databricks and guiding investments in the people and capabilities behind the company's growth. His leadership will focus on scaling the business while preserving its culture, advancing delivery excellence, and strengthening the trust v4c has earned with customers and partners. v4c.ai is a premier IT services consultancy specializing in Databricks, helping organizations modernize their data platforms and build enterprise AI capabilities. As a Databricks Ventures portfolio company and the 2026 Databricks C&SI Emerging Partner of the Year, v4c brings expertise across data engineering, AI strategy and governance, generative AI, and machine learning. Learn more at www.v4c.ai. Posted In:

Forrester
Oct 14th, 2026
Why MuleSoft, not Agentforce, is Salesforce's most strategic AI asset.

Why MuleSoft, not Agentforce, is Salesforce's most strategic AI asset. Oct 14 2026 MuleSoft Agent Fabric is MuleSoft's recent enhancement to deliver an agentic AI control plane. During the Dreamforce keynote, I noticed something subtle but significant. I didn't see "MuleSoft Agent Fabric." Instead, I saw "Agent Fabric," with the MuleSoft branding dropped and the Salesforce logo replacing the Mule logo in the UI. Forrester sees agentic AI consisting of three planes: the build plane, the orchestration plane for runtime, and the control plane for governance. Long term, I believe the first two will converge: Where you build an AI agent often dictates where you can run it. But it will be impossible to shoehorn all your agents into one build-and-orchestrate platform, resulting in multiplatform sprawl for that part of the agentic AI stack. In contrast, the need for one central place to govern AI agents will push agentic AI control planes to be multiplatform - just like how API management governs APIs across any number of API runtime platforms. That makes the control plane more strategic than the other two. For Salesforce, its emerging agentic AI control plane is Agent Fabric. AI governance is the future of API Management. Leading API management vendors recognize that the agentic AI control plane is the future of the market. I'm even inclined to rename the market "API and AI management" for my next Forrester Wave(TM) evaluation of API management. MuleSoft and competitors Kong and WSO2 have built strong AI gateways to govern LLM and MCP connections. But like APIs, governance is more than just a gateway. Gravitee, Kong, MuleSoft, and WSO2 deliver deep analytics for MCP and LLM token FinOps. MuleSoft has expanded its API portal to include LLMs, MCP servers, and agent cards. Gravitee's beta portal is slated to deliver similar capabilities soon. Both vendors are the first to deliver endpoint versioning for LLM, MCP, and A2A endpoints. Forrester clients can explore this more through Forrester's vendor comparison tool for API management vendors, based on my evaluative research, The Forrester Wave(TM): API Management Software, Q3 2026. Salesforce's advantage over API Management vendors: the full platform. But there are two things that MuleSoft, or rather Salesforce, has to augment its agentic AI governance that those other API management vendors lack: a broad agentic AI orchestration platform and context data to feed agents at runtime. To be clear, it is not assured that Salesforce will deliver a viable AI orchestration + context platform. Today, it is an amalgamation of Agentforce, Data 360, Headless Toolkit, AIforce, Informatica, MuleSoft's iPaaS for deterministic workflows, Slack, and more. Bolted-together Frankensteins create friction through unduly complex user experiences and complicated SKU purchases. But at least it's something. This could go in one of two paths. The ideal path is that Salesforce unifies its Frankenstein into a holistic AI platform with minimal buying and UX friction under one brand. One can imagine a future where Salesforce's agentic AI offering consolidates into three products - and I mean three real products engineered as such, not marketecture. The more likely path is that Salesforce stumbles to deliver. The obvious problem is that bringing together disparate M&A products into something that works is difficult. Notice in the above figure, though, that the control plane is the only layer that isn't currently a stitched-together Frankenstein. Unlike the rest of the platform, Salesforce's AI agent control plane is already one holistic product: Agent Fabric. Between its strategic positioning for buyers, its holistic product design, and its ability to extend Salesforce's reach to agents in every platform, MuleSoft's Agent Fabric, not Agentforce, is Salesforce's most strategic AI asset. AI agent control and governance is the most strategic element of the above for buyers. But AI orchestration is closest to where work gets done, so more economic activity flows through it, resulting in a larger total addressable market for tech vendors to chase after, especially in the near term. That may tempt Salesforce to chase after orchestration at the expense of Agent Fabric when it should be doubling down on Agent Fabric. This is especially likely so long as the Agentforce and MuleSoft business units remain siloed from each other. Agent Fabric has a strong lead compared to the competition. Will Salesforce expand that lead or blow it? MuleSoft's customers and competitors anxiously wait to find out. If you'd like to discuss Salesforce's strategy more deeply with me, schedule a guidance session or inquiry. See david mooter at: Technology & Innovation Forum East November 4-5, 2026, New York City Cut through CX tech noise and buy smarter. I walked into my first Dreamforce as a skeptic. Salesforce has made several attempts at IT service management, and none of them have provided the technical depth needed by IT teams. After a single briefing on the latest product and then months of silence, I had filed the effort under another short-lived experiment. The pre-announcements [...] As AI systems become more autonomous, security alone isn't enough to build trust. Learn how responsible AI helps organizations govern AI agents, manage emerging risks, and keep systems aligned with business goals and values.

Recently Posted Jobs

Sign up to get curated job recommendations

Mulesoft is Hiring for 14 Jobs on Simplify!

Find jobs on Simplify and start your career today

Don't see your dream role? Check out thousands of other roles on Simplify.Browse all jobs