Business and Tech

Mulesoft: Anypoint Platform Business Group Limit

Written by:
Published on March 31, 2021

Mulesoft: Anypoint Platform Business Group Limit


Anypoint Platform configuration is a key challenge for any MuleSoft Solution Architect.

Any client, small or large, would have multiple lines of Business or Business Units. They might be grouped within centralized or decentralized teams or even run single or multiple projects at any given time.

MuleSoft has the concept of Business Groups. These align with lines of business for segregation in the Control Plane.

It also has the concept of environments to segregate in the Control Plane to align with different environments.

This ring-fencing in terms of either business group or environment provides certain controls for segregation requirements.

The agenda behind this article is trying to identify the boundary conditions platform architects and decision-makers need to be aware of to make a more informed choice while planning to use business groups or environment combinations.

Limits on Number of Business Groups

As of March 2021, AnyPoint Platform has a hard limit on the number of business groups a registered account can create.

This hard limit is on the total number of business groups created with the AnyPoint platform account.

These business groups can be hierarchically structured or flat. Every business group counts in the total number.

This limit is 100 and excludes the top-level business groups that gets created by default while onboarding on AnyPoint platform.

Example diagram

A(1) -> B(2),C(3),D(4) = total 4

A(1)-> B(2),C(3),D(4)   B(2)->E(5),F(6),G(7)  D(4)->H(8) = total 8

Limits on Number of Environments per Business Group

As of March 2021, Anypoint Platform has a hard limit on the number of environments that are allowed to be created per business group.

This hard limit is on the total number of environments. Also this is per business group.

There is no concept of hierarchy in environments in a business group.

Example diagram 

A(150) -> B(150),C(150),D(150) = 150 environments in each business group

What is the Overall limit?

The overall number of Business groups allowed for a single registration with Mulesoft is 100, including the parent level Organization.

Overall, the number of environments that can be created to hit the boundary conditions are 101 X 150 = 1650 environments

Will, you hit this Limit?

It is highly unlikely one might hit this limit during implementation.

Who can hit this limit?

Large organizations that have global footprints and many independent teams, with large numbers of parallel projects in progress, might hit these limits.

How to Plan?

If you are a large organization that may encounter such limits, the following scenarios may present themselves

  1. Using environments to only segregate projects in large organizations
  2. Using Business groups to only segregate projects

It may help to rework your approach in terms of segregation. This way you will evaluate the possibility of hitting these business groups or environmental limits.


You may have a scenario where you might hit these boundary conditions of a business group and environment.

It is highly recommended to use the combination strategy to blend business groups and environment in such cases.

End Note

Hope you found this article interesting, do drop us a comment below with your inputs, views, and opinions regarding Mulesoft: Anypoint Platform Business Group Limit

Also, if you are interested in trying out an exciting new MuleSoft code quality product that reduces your Mule project costs by 79%, follow the below link :


Leave a Reply

Your email address will not be published. Required fields are marked *

Other Blog Posts

Other Blog Posts

Mulesoft Development Fundamentals: Dataweave Best Practices

‘MuleSoft development fundamentals’ is a blog series that takes you through various aspects of MuleSoft development from “How to structure your Mule code” to “Things to cater to when you deploy to production”. We would love to share our expertise with the Community, having worked with several MuleSoft Enterprise clients. Please find all the blogs …

Read more

IZ Analyzer – Scanning API Projects

In an API and microservices world, the quality of the deliverable becomes paramount – since a weak link can break the whole chain. In the previous blog posts, we had seen how Mulesoft code implementations could be quality tested in an automated manner with IZ Analyzer. Now with API Analyzer plugin, APIs can be quality …

Read more

Mind Your Code Quality; It’s an Asset

When comes to code quality, I have seen discussion rather than an argument that the main task of a developer is to deliver working code to the customer. Is it true? I don’t think so. It must be fully covered code; that means not only functionality-focused code, but the quality of code also matters. A …

Read more