Platform-as-a-Service (PaaS) is a cloud service model that provides developers with managed runtimes, middleware, and platform tools to build and operate applications without managing underlying infrastructure. It streamlines deployment, scaling and continuous delivery, while introducing abstraction, provider lock-in and additional operational responsibiliti…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Platform as a service (PaaS) is a cloud model in which a provider supplies a managed runtime and development platform while customers remain responsible for their applications and data.
PaaS emerged as a cloud abstraction between infrastructure and software as a service: providers take on more runtime and platform operations so teams can deploy applications without managing servers. NIST classifies PaaS as a cloud service model in SP 800-145.
You deliver application code and configuration to a prepared stage. The provider runs much behind the curtain—operating system, runtime, or scaling—while your application, data, and use remain your responsibility.
The provider operates platform components; the customer manages the application and data within the agreement.
Code runs in a provider-maintained environment with standardized services.
Dependencies on APIs, runtime, and operating model affect the ability to move platforms.
PaaS speeds delivery and reduces infrastructure work. Teams must assess provider boundaries, cost, data access, compliance, and lock-in.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.