Rather than treating platform engineering as a isolated tooling initiative, the research models it as a socio-technical capability that reshapes how software organizations coordinate, govern, and execute operational responsibilities as they scale.
According to the framework, the organizational outcomes of developer platforms emerge from dynamic interactions among three primary forces: adoption, friction, and the standardization value generated by organizational complexity.
The research situates internal developer platforms across established software engineering domains, connecting platform outcomes to literature on software delivery performance, socio-technical congruence, Conway’s Law, modularity, software ecosystems, platform governance, and developer experience. Within this context, the paper defines platform friction as a latent construct that reflects the cumulative resistance teams encounter when evaluating, adopting, utilizing, and extending a platform. The author explicitly distinguishes friction from adjacent concepts including switching costs, coordination burdens, trust deficits, and developer experience.
To support analysis and evaluation, the framework introduces stylized models addressing complexity, adoption, friction, and return on investment. The paper explicitly qualifies these formulations as heuristic devices intended for conceptual exploration rather than empirically calibrated empirical laws. Accompanying these models are diagnostic tables, proxy metrics, and an operationalization methodology for friction designed to facilitate structured organizational learning and provide foundations for subsequent empirical investigations.
The study incorporates two anonymized organizational vignettes to illustrate the theoretical mechanisms in real-world environments. The author notes explicit boundaries regarding these examples, clarifying their qualitative provenance, operational limitations, and non-generalizable status rather than presenting them as universally applicable case studies.
Finally, the paper examines platform engineering in relation to AI-assisted software engineering. The analysis proposes that as generative artificial intelligence decreases the marginal cost of producing code-like artifacts, the organizational necessity for governed defaults, unambiguous ownership, verification pathways, and operational legibility increases. The author presents this perspective as a bounded inference and emerging research agenda rather than an established empirical certainty, concluding that platform investments must be appraised comprehensively across operational cost, engineering flow, and risk reduction rather than reduced to any single metric.
Authored by Phani Vasishta Kuruganti, the paper presents five distinct contributions designed to establish a specialized, platform-specific vocabulary for software engineering research and practice. Kuruganti provides this conceptual terminology to explain why certain developer platforms evolve into organizational paths of least resistance rather than remaining technically sound but organizationally marginal initiatives. Under this vocabulary, the framework models platform friction as the cumulative resistance technical teams experience across four specific activities: evaluating, adopting, using, and extending internal platforms.
Published on 15 September 2026, the open access research paper was released early in the Journal of Cloud Computing to provide faster access to peer-reviewed, accepted scholarship. This citable version carries a permanent digital object identifier and remains subject to further editorial modifications before being automatically replaced by the final Version of Record, with all legal disclaimers applying.
Subject of Research: Socio-technical dynamics and organizational economics of internal developer platforms
Article Title: Platform engineering as organizational strategy: platform gravity, friction, and the economics of scaling internal developer platforms
Article References: Kuruganti, P. V. (2026). Platform engineering as organizational strategy: platform gravity, friction, and the economics of scaling internal developer platforms. Journal of Cloud Computing. https://doi.org/10.1186/s13677-026-00972-9
Image Credits: AI Generated
DOI: 10.1186/s13677-026-00972-9
Keywords: Platform engineering, Internal developer platforms, Platform gravity, Platform friction, Socio-technical systems, Conway's Law, Software delivery performance, Modularity, Software ecosystems, Platform governance, Developer experience, AI-assisted software engineering, Generative AI, Operational legibility, Return on investment, Engineering flow
News Source: Denise Maddox. (November 19, 2026). Platform Gravity Framework Explains Why Internal Developer Platforms Succeed or Stall. Scienmag.



