Loading content
Software-as-a-Service (SaaS) is a cloud delivery model where applications are hosted centrally and offered to customers as subscription services. Users access software over the internet while providers manage operations, scaling and updates. The model affects cost structures, integration patterns, security, and organizational responsibilities like tenancy an…
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.
Software as a service is a delivery model in which a provider operates and updates a usable application as an ongoing service.
SaaS developed as software moved from local installation to network-based services. The provider typically operates and maintains the application; customers access it over a network and often pay by subscription or usage.
Separate the service promise from its implementation: assess availability, data processing, tenant isolation, integrations, exit, and responsibilities. The provider controls core operations while customers control configuration, use, and their data; that boundary must be clear technically and contractually.
The application is offered as a continuously available service rather than an installation package.
The provider handles infrastructure, maintenance, updates, and typically scaling.
Provider and customer share duties for security, configuration, data, and use.
SaaS affects procurement, architecture, integration, and governance. Availability, data control, portability, and vendor dependency matter alongside features and price.
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.