How do you govern a growing portfolio of side-by-side extensions across an enterprise?

As extension count grows across business units and teams, deliberate governance becomes necessary to prevent duplication, inconsistent quality, and unclear ownership — the same discipline needed for any growing application portfolio, applied specifically to the BTP extension landscape.

flowchart TD
    A[Extension proposal] --> B{Reviewed against architecture standards?}
    B --> C[Registered in central extension catalog]
    C --> D[Assigned clear ownership + lifecycle plan]
    D --> E[Ongoing governance: security review, cost tracking, deprecation policy]

Practically, this typically means a lightweight architectural review gate before new extensions are built (checking against existing capability to avoid duplication), a central catalog/inventory of what exists and who owns it, consistent standards for security and integration patterns across extensions, and an explicit deprecation/retirement process so extensions don't accumulate indefinitely as "zombie" applications nobody actively maintains but nobody decommissions either.