Platform engineering and internal developer portals: a multivocal literature review

Platform engineering has become the dominant approach to managing developer infrastructure at scale, with industry surveys indicating that 94% of organizations have adopted or plan to adopt dedicated platform teams. Despite this rapid practitioner uptake, academic research remains scarce: a systematic search across five major databases identified fewer than a dozen peer-reviewed papers from reputable venues that address platform engineering directly, while gray literature from foundations, vendors, and industry surveys is abundant. This study presents the first multivocal literature review (MLR) of platform engineering and internal developer portals, following published guidelines for including gray literature in software engineering reviews. The review synthesizes 88 sources across both peer-reviewed and gray literature, with sources explicitly tiered by provenance and gray literature assessed using the AACODS framework. Five research questions address the state of the literature, architectural components and patterns, success metrics and KPIs, adoption barriers, and the relationship between platform maturity and developer productivity. The synthesis yields a taxonomy of internal developer portal components grounded in 36 architecture-focused sources, an integrated metrics framework spanning DORA, SPACE, and developer experience dimensions, a comparative analysis of four platform engineering maturity models, and a quantification of the academic–practitioner divide: only 2 of 88 included sources (2.3%) originate from tier-1 venues with platform engineering as their primary topic, while practitioner communities have generated the authoritative definitions, frameworks, and measurement instruments as academic engagement lags by two to three years. A particularly striking gap concerns scorecards, the primary governance mechanism within IDPs, for which no peer-reviewed empirical evidence of effectiveness exists despite widespread commercial adoption. These findings carry implications for both researchers and practitioners. For the research community, the study identifies nine specific opportunities where empirical work is most needed, with a validated PE maturity model and a PE-specific measurement instrument representing the highest-impact contributions. For practitioners, the evidence supports treating platforms as products, combining delivery metrics with developer experience surveys, and designing golden paths as enablers instead of mandates.