How Anypoint API Experience Hub (AEH) is comparable to Anypoint Community Manager (ACM)

In the previous blog, we understood the need for AEH, the challenges faced by developers in creating API Portal, and the solutions offered by AEH to resolve them. In this blog, let’s better understand AEH by comparing it with ACM.

Before we dive into the major difference between brand new AEH and the existing powerful ACM, let’s first understand the similarity between both products.

Similarities between AEH and ACM

1. Both AEH and ACM are products based on the Salesforce experience cloud platform.
2. The core components to build API Portal are similar between the two products.
3. Both products support the full range of use cases from internal private portals to full-blown external portals.
4. Underlying components of the product are built as a managed package by MuleSoft and installed into Salesforce Org.
5. Licenses are procured and provisioned by MuleSoft.

Differences between AEH and ACM

1. Single Platform vs Multi-Platform

Fig. 1 — A sample ACM portal in the Salesforce platform

Those who worked with ACM know that developing an API Portal using ACM requires juggling between two platforms; Anypoint Platform and Salesforce Experience Cloud based on which feature you’re going to use. Moving back and forth between these two platforms is a cumbersome process and creates frustration and confusion among the developers.

Fig. 2— A sample AEH portal in the Anypoint platform

MuleSoft has made developer’s life easier with AEH by providing all the features of creation and management of API Portal from the single Anypoint platform.

2. Easier and faster with AEH compare to ACM

Fig. 3–4 steps to launch API Portal with AEH

Launching API Portal with small to medium complexity with ACM requires a couple of days but with AEH it’s reduced considerably, thanks to a single platform with easier management in AEH. Whether you're a Portal Admin who is responsible to create, configure or manage the portal or a Developer who browses or learns APIs to use them in the applications it’s a breeze with AEH. Launching an API Portal with AEH is simply a 4 steps process.

3. Salesforce platform is transparent with AEH

Creation of Portal with AEH, you don’t need to learn the nitty-gritty of the salesforce platform. AEH reduces the burden of salesforce knowledge to get started and see value immediately by providing a simple portal creation experience. In addition, one can manage portal users and API Products through an Anypoint account directly.

4. New Templates, Components with AEH for improved Marketplace experience

With the AEH Portal administrators can use a newer set of out-of-the-box templates to build a best-in-class API marketplace experience. The new template provides an updated design and layout to make a modern API consumption experience for the users. AEH provides lightning web components using SF LWC framework.

5. Licensing

A standard ACM license consists of a Salesforce Customer Community Plus Login License Unlimited Edition. Community login-based license is calculated by the number of daily unique logins.

AEH requires two types of licenses:
Salesforce — This license is required to use the Salesforce Experience Builder.
External Identity — This license is based on the number of member requests to access the portal. The current package has a minimum of 100 API access requests which require a minimum of 2000 External Identity licenses. This is required for the portal consumers to access the API portal.

For more details about the license of ACM refer here and for AEH refer here.

With the motto of starting fast with simplicity in portal development, AEH has enabled a community of business users to launch the marketplace. Both the products, ACM and AEH are powerful and complement each other in the journey of launching API Marketplace.