Anypoint Platform setup is a multi-week project. Coordinate with the Salesforce account team for licensing; coordinate with internal IT for runtime selection.
- Confirm MuleSoft licensing
Coordinate with the Salesforce account team. Pricing scales with API volume, vCore consumption, and environment count.
- Pick the runtime
CloudHub for SaaS, Anypoint Runtime Fabric for on-premises, hybrid for both. Decision based on data-residency and operational preferences.
- Install Anypoint Studio
Developers install the IDE locally. The studio is free; the platform license is the paid component.
- Plan API-Led Connectivity
Layer applications into System, Process, and Experience APIs. The pattern shapes how integrations get built across the enterprise.
- Configure CI/CD
Anypoint integrates with GitHub Actions, Jenkins, and other CI/CD systems. Set up automated deployment pipelines from day one.
- Roll out monitoring and alerting
Anypoint Monitoring is the daily operational view. Configure dashboards and alerts for production applications.
- MuleSoft licensing is enterprise-grade. Budget carefully; pricing scales with usage.
- CloudHub vs. Runtime Fabric is a strategic decision. Switching after deployment is non-trivial.
- API-Led Connectivity is a strong architectural pattern but adds complexity. Small integrations may not need three layers.
- Salesforce-MuleSoft is the strategic direction. Customers running both products benefit from the integrated offerings.