Diagram
Three layered stacks compare infrastructure as a service, platform as a service, and software as a service. In each stack the provider manages the lower hardware, virtualization, and platform layers, while the customer manages the upper application, data, and settings layers — with responsibility shifting to the provider as you move from IaaS to PaaS to SaaS.
Comparing IaaS, PaaS, and SaaS Responsibilities
The three service models differ by who manages what and how much control the customer keeps. The tradeoff is consistent: more customer control requires more customer management, while more provider management means faster use with less flexibility.
| Model | Provider manages | Customer manages | Choose when |
|---|---|---|---|
| Infrastructure as a Service (IaaS) | Physical hardware, virtualization, networking | Operating system, runtimes, data, applications | Maximum control or custom infrastructure is needed |
| Platform as a Service (PaaS) | Hardware plus operating system, runtime, and scaling | Application code and data | Developers need to build apps without managing servers |
| Software as a Service (SaaS) | Almost everything, including the finished application | User settings and data inside the app | A ready-to-use application is needed with minimal work |
Domain 1 of 6
27 practice questions
Practice this DomainLast updated