Broadcom Layer7 API Developer Portal

Name: Broadcom Layer7 API Developer Portal
Brand: Broadcom
Rating: 4.1 (11 reviews)

Leader

Broadcom provides semiconductors and infrastructure software for global organizations’ complex, mission-critical needs

Est 1961|Valuation $1764B

LinkedIn 446K|Website|Web traffic 4.0M|FTEs 33,000|HQ Palo Alto, California, US

MarketsAPI Management

Broadcom Layer7 API Developer Portal screenshot

01Competitive Landscape

Narrative analysis

Where the Layer7 Portal tends to be selected: - When an organization already runs Layer7 API Gateway and requires an integrated portal with enterprise authentication and governance. - When enterprise authentication controls are a priority: release notes highlight SAML SSO enhancements, multi-org/multi-role mapping, the option to disable local logins, and JWT support for Portal APIs. Where competitors often have advantages: - Developer experience and portal polish: competitors such as Kong, Apigee, and Azure APIM are commonly perceived as more modern and faster to configure for common portal experiences (branding, documentation, interactive consoles), though capabilities vary. - Pricing transparency and trialability: some competitors publish clearer packaging or offer trials, while Layer7 Portal pricing and trial options are less visible publicly. Competitive selection reality: - Review content suggests some buyers select the Layer7 Portal primarily for gateway integration rather than for portal UX.

	Broadcom Layer7 API Developer Portal	Kong Konnect Developer Portal	MuleSoft API Community Manager
Starting Price	Pricing not publicly listed; vendor provides quotes	Vendor publishes packaging that includes add-on costs for developer portals; enterprise tier pricing is quote-based	Licensing is tied to Salesforce community licensing; pricing typically provided by quote
Typical use case	Enterprises standardized on Layer7 API Gateway needing integrated portal and enterprise auth controls	Teams seeking a modern SaaS control plane and faster time-to-value for developer portals	Enterprises using MuleSoft and Salesforce that want an integrated developer community experience
Key Strength	Integration with Layer7 Gateway; enterprise auth controls (SAML, disable local logins); Portal API updates	Clear SaaS packaging, modern developer portal experience and cloud-native ecosystem	Ecosystem alignment with MuleSoft and Salesforce and enterprise platform integration
Key Weakness	Reviews frequently cite portal maturity and UX gaps; pricing opacity; operations-heavy upgrades for on-prem	Enterprise tier pricing is quote-based; costs can scale with usage and services	Perceptions of high cost and complex licensing; platform complexity

01Competitive Landscape

Narrative analysis

Where the Layer7 Portal tends to be selected:

When an organization already runs Layer7 API Gateway and requires an integrated portal with enterprise authentication and governance.
When enterprise authentication controls are a priority: release notes highlight SAML SSO enhancements, multi-org/multi-role mapping, the option to disable local logins, and JWT support for Portal APIs.

Where competitors often have advantages:

Developer experience and portal polish: competitors such as Kong, Apigee, and Azure APIM are commonly perceived as more modern and faster to configure for common portal experiences (branding, documentation, interactive consoles), though capabilities vary.
Pricing transparency and trialability: some competitors publish clearer packaging or offer trials, while Layer7 Portal pricing and trial options are less visible publicly.

Competitive selection reality:

Review content suggests some buyers select the Layer7 Portal primarily for gateway integration rather than for portal UX.

	Broadcom Layer7 API Developer Portal	Kong Konnect Developer Portal	MuleSoft API Community Manager
Starting Price	Pricing not publicly listed; vendor provides quotes	Vendor publishes packaging that includes add-on costs for developer portals; enterprise tier pricing is quote-based	Licensing is tied to Salesforce community licensing; pricing typically provided by quote
Typical use case	Enterprises standardized on Layer7 API Gateway needing integrated portal and enterprise auth controls	Teams seeking a modern SaaS control plane and faster time-to-value for developer portals	Enterprises using MuleSoft and Salesforce that want an integrated developer community experience
Key Strength	Integration with Layer7 Gateway; enterprise auth controls (SAML, disable local logins); Portal API updates	Clear SaaS packaging, modern developer portal experience and cloud-native ecosystem	Ecosystem alignment with MuleSoft and Salesforce and enterprise platform integration
Key Weakness	Reviews frequently cite portal maturity and UX gaps; pricing opacity; operations-heavy upgrades for on-prem	Enterprise tier pricing is quote-based; costs can scale with usage and services	Perceptions of high cost and complex licensing; platform complexity