Loading page
Loading page

Developer tools
Run the Mule runtime Community Edition to connect apps, data and APIs with message flows instead of point-to-point code.
Mule is a lightweight integration platform. Instead of writing a direct link between every pair of systems, you build flows in Mule. A flow receives a message, transforms it, runs business logic on it and routes it on. MuleSoft calls this an end to point-to-point madness.
Mule is event-driven. A flow starts when something happens, such as a request from a mobile app, a change in a database, or a new file. Transformers convert the data so the next system can read it. The MuleSoft README notes that the name comes from Mule carrying the heavy development load.
This template suits Java developers and integration engineers who already build Mule applications. It also suits teams that want to learn Mule or test Community Edition flows on their own server.
Running the Community Edition runtime lets you deploy and test Mule applications without a managed platform. Your flows and the data they move stay in your own service.
Be clear about what you get. This is the open-source runtime only, packaged by a community member. The enterprise features, cloud hosting and API management of the Anypoint Platform are not part of it. You build applications in a separate tool, and you look after updates and backups yourself.
Containers: yogeshmulecraft/mulece-esb:latest
Step 1
Choose the Starter plan. It costs $20 a month and runs up to 3 apps.
Step 2
Open App templates in the dashboard, choose MuleSoft ESB Runtime Community Edition, and click Deploy. We set up the containers, secrets and domain.
Step 3
Wait a few minutes for the first deploy, then open your new URL and finish the MuleSoft ESB Runtime Community Edition setup screen.