Through architecture optimisation and by using a phased approach, we helped one of our customers to save over £52K ($73K) licensing cost in their first year.
A starting package for anyone embarking on an integration journey or planning to scale API adoption.
Everything is required to start, deliver and expand MuleSoft programmes.
You'll receive comprehensive support to successfully initiate or scale your MuleSoft programme.
Set up of thresholds and alerts within Anypoint Platform
Engaging us is easy and straightforward.
You know exactly what you get when you get it and how much it costs. There are no hidden expenses!
Step 1. Fill in our Licensing Assessment Template to describe your requirements and IT landscape, select a package and choose add-on options.
Step 2. Send the Licensing Assessment Template to email@example.com to initiate a discovery call with our experts.
Step 3. Receive your high-level API-led design and our recommendations.
Unlike many other vendors, MuleSoft thrives off the success of each customer and every project. It's vital that the platform is adopted and utilised according to the MuleSoft methodologies and best practices.
To ensure that all clients receive maximum value from their investments, MuleSoft introduced several pre-conditions that you should be aware of:
All potential MuleSoft customers must be prepared to engage with MuleSoft.
There should be an agreed plan for your programme delivery supported by either certified resources or a MuleSoft certified partner.
CloudHub (iPaas) provides the fastest way of getting started and the easiest way to manage the Anypoint Platform. It also means that the run costs of your infrastructure are included, unlike for the On-Premise or Hybrid options.
With CloudHub, you have to assign a minimum of 0.1 vCore to an API regardless of whether it consumes that capacity or not. So, you get a maximum of 10 APIs for 1 core. If your APIs are not maximising this minimum count, consider bundling some APIs into Sub-System APIs. However, this should be done only in case APIs are logically similar, and their features can be easily decoupled in the future.
Plan how and when you will be building your APIs. Careful planning will significantly affect the utilisation of your cores. Very likely the core count will steadily ramp up over time. You won't need the full projection on day 1!
Manage your non-production core count effectively. Consider how many those environments you really need. You may not want all non-prod APIs to stay active across all environments. Look at potentially switching APIs off across some environments to free up the core count.
Discover our Integration Framework - a tailored roadmap to build a solid foundation for your integration journey.
Our Managed service model provides routine maintenance and troubleshooting and fills your IT team's knowledge ...
Give your IT teams the knowledge and skills to confidently use the MuleSoft Anypoint Platform to its full potential.
Our MuleSoft experts help you manage costs from the start. As a part of the service, you receive recommendations on API optimisation and a sizing plan to start with a minimum number of cores and gradually add more as required.
You will be delighted with the results - fewer APIs, greater reuse and optimisation of licences at the same time!