Jayasuriya, RPiyarisi, TAwandya, SWickramasooriya, SThelijjagoda, SKasthurirathna, D2026-09-162026-07-07R. Jayasuriya, T. Piyarisi, S. Awandya, S. Wickramasooriya, S. Thelijjagoda and D. Kasthurirathna, "The Multi-Tenant Customization Paradox: Formalising the Intrinsic Conflict Between Scalable Shared Codebases and Tenant-Specific Operational Customization in SaaS Architecture," 2026 IEEE 50th Annual Computers, Software, and Applications Conference (COMPSAC), Madrid, Spain, 2026, pp. 3052-3057, doi: 10.1109/COMPSAC69091.2026.00456.979-833154497-3https://rda.sliit.lk/handle/123456789/5270Multi-tenant Software-as-a-Service (SaaS) architectures promise economies of scale through a single shared codebase serving multiple tenants. However, enterprise tenants increasingly demand deep operational customization (bespoke workflows, domain-specific business rules, and industry-specific computational logic) that fundamentally conflicts with the sharedcodebase constraint. Despite the centrality of this tension to SaaS architecture, no formal definition exists in the literature. This paper formally defines the Multi-Tenant Customization Paradox (MTCP): the structural impossibility of simultaneously maximizing codebase unity and tenant customization depth without incurring costs that grow super-linearly with the number of tenants. We introduce a formal model quantifying this tension through the Paradox Coefficient $P(S)$, establish a five-dimensional customization taxonomy with per-dimension formal measures, derive the Feasibility Region governed by an architectural sophistication parameter $α(B)$, propose an operational rubric for estimating $α(B)$ in practice, and derive an upper bound on the achievable unity-depth trade-off for four canonical resolution strategies. Our formalization demonstrates that the paradox is inherent to the mathematical structure of multi-tenancy rather than incidental to implementation choices, providing architects and researchers with a theoretical foundation for reasoning about customization trade-offs.enarchitectural trade-offscustomization paradoxMulti-tenancyformal methodsSaaS architecturesoftware product linesConference PaperDOI 10.1109/COMPSAC69091.2026.00456