Announcing Standalone Mule support for MuleSoft Government Cloud

Responding to COVID-19 challenges has led to an explosion of digital innovation in a place often overlooked — our own governments. 

Through the power of APIs, innovative agencies have enabled contact tracing solutions across major U.S. cities, automated eligibility programs for real-time citizen financial assistance, and other mission-critical projects in a matter of weeks. And with nearly 200 FedRAMP-authorized cloud technologies now available, U.S. government agencies can leverage similar digital solutions that have driven innovation throughout the private sector. 

Flexibility is the key to success in government IT modernization

Yet, when you look behind the curtain on these success stories, many of these digital solutions rely on data and processes locked away in legacy IT infrastructure decades in the making. And as the GAO reports, the U.S still has a long way to go before it can fully embrace government digital transformation.

This is where integration platform-as-a-service, or iPaaS, comes into play. The ability to manage APIs and integrations in the cloud is still a fairly new concept in the public sector, but it is already helping agencies securely accelerate their IT modernization journeys. Last year, we announced our FedRAMP-compliant MuleSoft Government Cloud and have already supported a number of federal, state, and local agencies for their cloud-based integration needs.   

But we know that decades-old, massive on-premise IT infrastructure stacks are not going to be moved to the cloud overnight. Successful IT modernization initiatives take considerable time and planning, and some agencies may have select, sensitive data, and integration needs that are just better left on-premise. Citizen and employee demands will continue to evolve rapidly, and many agencies are already reporting challenges securely managing their data needs consistently across cloud and on-premise applications. 

So how can public sector IT teams add and monitor these new digital solutions to meet citizen demands, without disrupting critical on-premise integrations and infrastructure? 

Standalone Mule support provides flexibility to meet both short and long-term needs  

We recognize this unique challenge, which is why we’re so excited to announce the availability of Standalone Mule support in MuleSoft Government Cloud. MuleSoft Government Cloud now permits the deployment of Mule runtime engine instances into an on-premises environment (Standalone Mule instances). 

Standalone Mule support enables our federal, state, and local government customers and government contractors to deploy runtimes inside their private cloud or on-prem environment, while having the ability to manage them all from their Government Cloud control plane. 

Standalone Mule support underwent a rigorous internal security and compliance review, and the Significant Change Request Form and updated System Security Plan were approved by our FedRAMP sponsoring agency. With this new capability, we are continuing to enhance our FedRAMP-compliant environment for Anypoint Platform, the only solution in the Gartner Magic Quadrant as a leader for both Enterprise Integration Platform as a Service (iPaaS) and Full API Lifecycle Management.  

*Standalone Mule instances, and MuleSoft support for standalone Mules, are outside the scope of FedRAMP. The customer is responsible for ensuring that all data shared with Salesforce complies with any and all data and information protection policies, requirements, and standards. Review the MuleSoft System Security Plan for FedRAMP scope. 

Interested in learning more?  

Check out our upcoming webinar on September 10th to see how government agencies have taken an API-led approach to unlock legacy systems and quickly bring new critical citizen services online. You can also learn more about standalone Mule support on the official Government Cloud documentation page. To learn more about MuleSoft Government Cloud, check out our whitepaper or view a demo.



We'd love to hear your opinion on this post