Full-Time
Updated on 9/12/2026
Enterprise API management and integration platform
$141.6k - $235.8k/yr
No H1B Sponsorship
Washington Metropolitan Area, USA + 1 more
More locations: Herndon, VA, USA
Hybrid
The Herndon role is office-flexible; the Washington, D.C. metropolitan area roles are remote with office flexibility.
US Top Secret Clearance Required
See people who can refer or advise you
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.
Company Size
1,001-5,000
Company Stage
Acquired
Total Funding
$480M
Headquarters
San Francisco, California
Founded
2006
See people who can refer or advise you
Help us improve and share your feedback! Did you find this helpful?
Health Insurance
Professional Development Budget
F5 and MuleSoft, a Salesforce company, collaborate to deliver inline security and governance for Agent Fabric and agentic AI applications. F5 announced a technology integration with MuleSoft, bringing F5 AI Guardrails - part of the F5 AI Security Platform - directly into Agent Fabric. As enterprises rapidly scale AI agents and large language model (LLM) applications, this native integration provides security and platform engineering teams with centralized policy enforcement, real-time protection against malicious prompts, and enhanced auditability without re-architecting or replacing the systems already in use. As organizations scale agentic AI capabilities, security teams face a growing governance gap and frequently lack visibility into agentic traffic. They risk exposure from prompt injection, harmful outputs, and sensitive data leakage. The joint integration federates F5's runtime AI security into Agent Fabric's Omni Gateway, enabling enterprises to enforce unified guardrail policies across all prompts and outputs moving through their agentic workflows. Eliminating the governance gap for agentic AI. Until now, organizations deploying Agent Fabric and seeking to leverage F5 AI Guardrails have faced a trade-off: either route LLM traffic through a separate F5 inspection layer, creating additional operational complexity and fragmented telemetry, or rely solely on native gateway controls without extending F5 AI Guardrails policies directly into their MuleSoft-managed workflows. By federating F5 AI Guardrails into Agent Fabric, enterprises gain: * Unified governance and zero double-proxy overhead: Policy management for AI traffic lives in a single control plane. Agent Fabric's Omni Gateway routes LLM calls directly to the F5 AI Guardrails Scan API, inspecting inbound prompts and outbound completions inline before models are invoked or responses returned. * Support for Agentforce ecosystems: Organizations can apply consistent runtime security controls across Agentforce-powered agents, Agent Fabric workflows, and custom AI applications. * Proactive threat mitigation: The solution is designed to block prompt injection, jailbreaks, toxicity, and unauthorized topics while reducing personally identifiable information (PII) and protected data exposure at runtime. * Data residency and sovereign control: Flexible dual-deployment topology allows self-hosted Kubernetes deployments including private VPCs, allowing sensitive prompt and completion data to remain within customer boundaries. * Low-touch policy tuning: Security teams author and version scanners, blocklists, and sensitivity thresholds within the F5 console, which Omni Gateway picks up dynamically without requiring policy or code changes. * SOC back-correlation and compliance auditability: Decisions carry detailed telemetry and shared scan IDs for seamless correlation in the F5 console, simplifying compliance with regulations such as the EU AI Act, GDPR, and HIPAA. "AI agents are moving from experiments into the critical path of the enterprise," said Kunal Anand, Chief Product Officer at F5. "The biggest risk in agentic AI is that agents will move faster than enterprise security and governance models can keep up. By integrating the F5 AI Security Platform directly into Agent Fabric, we are putting protection in the path of every prompt and response, where it can operate in real time. That lets organizations move faster with AI while preserving the control, visibility, and accountability their most important business processes demand." "We built Agent Fabric as the neutral solution to support enterprises running agents across a mix of models and platforms," said Andrew Comstock, SVP & GM at MuleSoft. "By extending Agent Fabric's existing LLM API and AI services to support F5 AI Guardrails as a first-class provider, we're making it even easier for customers to scale their agentic enterprise on the security tooling they know and trust." David Marshall is the founder of VMblog.com, one of the industry's longest-running independent publications covering modern data center technologies. What began as a focus on virtualization and cloud computing has expanded to cover the full spectrum of enterprise IT, including AI, security, and DevOps, making VMblog a trusted destination for vendor news, technology analysis, and industry commentary.Beyond publishing, David has spent his career at the intersection of technology and business, inventing, marketing, and launching a number of successful software companies and products, and building a reputation as a skilled marketing executive in the enterprise IT space.David is also a published author, having written two well-regarded books on virtualization and served as technical editor for two "For Dummies" titles covering virtualization and cloud computing. He co-founded CloudCow.com, a publication focused on cloud computing, and has been named a VMware vExpert every year since 2009, one of the longest continuous honoree streaks in the program's history.Connect with David on LinkedIn: https://www.linkedin.com/in/davidmarshall/
F5 and MuleSoft have integrated F5 AI Guardrails into Agent Fabric to provide inline security for AI agent applications. The integration addresses growing security challenges as enterprises scale AI deployments, including risks from prompt injection, harmful outputs, and data leakage. The solution enables unified governance without requiring additional infrastructure. Agent Fabric's Omni Gateway routes calls directly to F5's Scan API, inspecting prompts and responses before model invocation. Security teams can manage policies centrally whilst maintaining data residency control through flexible deployment options. The integration supports Agentforce ecosystems and provides threat mitigation against jailbreaks and unauthorized data exposure. It includes compliance features for regulations including the EU AI Act, GDPR, and HIPAA. F5 AI Guardrails for Agent Fabric is now generally available. The companies will demonstrate the integration at Dreamforce in San Francisco from 15-17 September 2026.
APIKit now Resolves OAS fragments: scaffold modular apis natively. July 22, 2026 | 4 mins read Modular design is a necessity for enterprise API teams. By leveraging reusable components like schemas, parameters, and security definitions as external fragments, developers can ensure consistency and efficiency across their API ecosystems. However, one common friction point has been the scaffolding process: developers often had to manually bundle OpenAPI specifications before generating their Mule applications. MuleSoft, INC. is excited to announce native support for OpenAPI Specification (OAS) fragments within APIKit, streamlining the "design-to-implementation" workflow. The Problem: Scaffolding required a fully resolved spec. In the past, APIKit required a fully resolved OpenAPI specification to scaffold a project. If your API relied on external fragments - referenced via $ref to local files or Exchange assets - the scaffolding engine would fail, forcing developers to manually bundle their specifications using external tools. This added unnecessary complexity to the API-first workflow and discouraged the use of modern, modular design patterns. The Solution: Native fragment resolution using APIKit. Now, MuleSoft, INC. has updated APIKit to natively recognize and resolve external OAS fragments. When you initiate a scaffold from an OpenAPI specification, APIKit now automatically: * Resolves dependencies: It handles $ref references pointing to local files, relative paths, and Exchange assets * Maintains modularity: It supports fragments for schemas, parameters, responses, request bodies, headers, and security schemes, ensuring that your modular API design is respected throughout the implementation phase * Automates bundling: It bundles the resolved specification seamlessly before scaffolding, removing the need for manual pre-processing 3 reasons this matters for your workflow. This update is an investment in developer productivity and API governance. You can expect the following: * Faster development cycles: By eliminating manual bundling, you can jump straight from a modular API design to a scaffolded project in seconds * Improved governance: Because APIKit now supports fragment resolution, it encourages the use of reusable enterprise API components, leading to cleaner, more maintainable codebases * Consistent experience: Your implementation will now match your design, with payload shapes, headers, and error definitions correctly propagated from your fragments into your Mule flows Get started. This capability is included as part of the core APIKit experience within Anypoint Code Builder developer experience, with no additional licensing required. Download the latest Anypoint Extension Pack via Visual Studio Marketplace and scaffold directly from your modular OpenAPI specifications.
Mule Diagnostic Agent now available for Runtime Fabric customers. July 21, 2026 | 2 mins read MuleSoft, INC. is thrilled to launch the AI-powered MuleSoft Diagnostics Agent for Anypoint Runtime Fabric, enabling hybrid deployment customers to drastically reduce mean time to resolution (MTTR), minimize application downtime, and focus on core innovation. By bringing this advanced cloud functionality to your self-managed Kubernetes clusters, Runtime Fabric delivers the best of both worlds: the velocity of intelligent insights through Anypoint Monitoring and the new Diagnostics Agent and the absolute control required to meet your strictest data sovereignty and compliance mandates. Get started with the Mule Diagnostic Agent. To get started, you will need to have your MuleSoft organization linked to an Einstein-enabled Salesforce organization. Mule diagnostics are available from the latest patch versions of Mule 4.6 LTS, Mule 4.9 LTS, Mule 4.10 Edge, Mule 4.11 Edge, and Mule 4.12 Edge. You need to be on RTF agent versions 2.11.50 or later. Learn more about Mule Diagnostic Agent and its features in the official announcement.
MuleSoft Government Cloud now supports FIPS 140-3 compliant runtime. June 26, 2026 | 6 mins read MuleSoft is excited to announce that FIPS 140-3 compliant Mule Runtime is now generally available (GA) for MuleSoft Government Cloud, a significant milestone in its commitment to meeting the highest federal security standards for its public sector customers, ensuring your integration workloads satisfy FedRAMP mandates without additional tooling. Upgrade your Government Cloud environment to the current federal cryptographic standard. This release ensures that every cryptographic process within the Mule Runtime meets the rigorous requirements set forth by the U.S. federal government to protect sensitive, unclassified data. What is FIPS 140-3? FIPS 140-3 (Federal Information Processing Standard Publication 140-3) is the latest U.S. federal government standard that defines strict security requirements for cryptographic modules used in IT systems. It is the successor to FIPS 140-2 and is required for any system that processes, stores, or transmits sensitive government information. For government agencies and organizations handling federal data, using FIPS-validated cryptography is a regulatory mandate, not optional. What this means for customers: Benefits and availability. You can now run your MuleSoft Government Cloud workloads on Hybrid Standalone (HSA) and CloudHub 1.0 (CH1) deployment models with full FIPS 140-3 compliance built directly into the runtime, with no third-party cryptographic solutions required. * Meet FedRAMP compliance requirements Ensure your MuleSoft Government Cloud integration workloads satisfy federal cryptographic security mandates without additional tooling or workarounds * Align with federal security frameworks: Whether you're operating under FedRAMP, FISMA, or other compliance frameworks, this release ensures your cryptographic processes meet the required standards * Operate with confidence in regulated environments: Remove compliance uncertainty and run your integration workloads knowing that cryptographic operations are fully validated against federal standards * No alternative solutions needed: FIPS 140-3 compliance is built into the runtime, eliminating the need to seek third-party cryptographic solutions This release is available to all MuleSoft Government Cloud customers using: * Hybrid Standalone (HSA) deployments: Mule applications hosted and managed in customer's own Data Centers or Private/Public Clouds * CloudHub (CH1) deployments: Mule applications hosted on MuleSoft Government Cloud Getting started. Ready to take advantage of FIPS 140-3 compliant runtime in your MuleSoft Government Cloud environment? Upgrade to Mule Runtime 4.9 LTS patch version 4.9.18 or later that supports FIPS 140-3 compliance and get started with its FIPS 140-3 support documentation. Its commitment to security-first integration. This release reflects MuleSoft's deep commitment to serving government agencies and security-conscious organizations. As federal security standards continue to evolve, MuleSoft remain dedicated to ensuring that MuleSoft Government Cloud provides a trusted, compliant platform for the most sensitive integration workloads. MuleSoft Government Cloud meets the highest federal cryptographic security standards, enabling agencies and regulated organizations to integrate with confidence. Effective September 21, 2026, the National Institute of Standards and Technology (NIST) will officially transfer every FIPS 140-2 validation into 'Historical' standing. To prevent FedRAMP compliance findings, MuleSoft strongly encourage upgrading your integration applications and underlying Mule runtimes to FIPS 140-3 validated versions before any upcoming security assessment scheduled past this deadline.