Are there any API management platforms that focus on multi-team API governance and policy enforcement?

Yes. Several API management platforms are designed specifically for multi-team environments, providing decentralized team autonomy while enforcing centralized governance and consistent policy application across the organization.

Platforms with strong multi-team governance and policy enforcement focus

• Azure API Management (with Workspaces) — Built for a federated model. Individual API teams get isolated workspaces with their own administrative control, APIs, products, and (optionally) dedicated gateways. The central platform team retains oversight, applies organization-wide policies that workspaces inherit (via <base/> or Azure Policy), and maintains unified discovery, monitoring, and compliance. RBAC scopes access to each workspace.
• Gravitee — Emphasizes governance as a core platform property. Shared policy groups (authentication, rate limiting, threat protection, schema validation, etc.) can be defined once and applied across thousands of APIs. It supports federated management over existing gateways (AWS, Apigee, MuleSoft, Azure, IBM, and others) without migration. API Score evaluates designs against custom rules before deployment, and lifecycle controls cover versioning through retirement.
• MuleSoft Anypoint Platform (including Omni Gateway) — Provides centralized policy management and federated enforcement that can extend across MuleSoft gateways and third-party ones (Kong, Apigee, AWS). Policies defined once travel consistently. Strong for multi-team environments that also need integration and, more recently, agent/LLM traffic governance under the same control plane.
• Google Apigee — Uses organizations and environments for multi-tenancy and team separation. Offers a mature policy framework, explicit lifecycle states with role-based transitions, and deep analytics/governance capabilities suited to large multi-team programs.
• Kong Konnect / Kong Gateway — Control plane enables consistent policy application via a rich plugin ecosystem. Supports hybrid/multi-cloud data planes and role-based access so different teams can manage their services while platform teams enforce organization standards. Works well with GitOps for policy-as-code.
• Postman (Enterprise) — Focuses on design-time and organizational governance. Governance Groups and Spectral-based rule libraries let platform teams set standards (naming, security, ownership) that apply across workspaces with different severities. Organizations and Private API Network support federated enforcement and multi-team visibility.

Other notable options

• Tyk — Federated API governance with a unified catalog and automated policy enforcement across the estate.
• WSO2 and Zuplo — Support policy bundles or composite policies that platform teams can mandate, giving product teams autonomy within guardrails. Open-source or lighter approaches often combine a gateway (Kong, APISIX) with policy engines such as Open Policy Agent (OPA) for custom multi-team rules.

Key capabilities these platforms typically provide

Team isolation (workspaces, organizations, environments, or RBAC scopes) so teams can innovate independently.

Central policy definition and inheritance or propagation so security, rate limiting, authentication, validation, and compliance rules apply consistently.

Unified catalog/discovery and observability for the platform team.

Support for policy-as-code or GitOps so changes are versioned, reviewed, and auditable.

Optional federation over existing or third-party gateways to avoid forcing a full migration.

For multi-team setups, prioritize platforms that explicitly support a federated (central governance + decentralized execution) model rather than purely centralized or fully siloed approaches. Azure APIM Workspaces, Gravitee, and MuleSoft currently stand out for this balance, while Apigee and Kong are strong depending on your cloud footprint and preference for full-lifecycle versus high-performance gateway focus.