Software as a Service (SaaS)
Slide deck explaining Software as a Service (SaaS), provider and customer responsibilities, how SaaS differs from PaaS and IaaS, typical scenarios, and common pitfalls.
Software as a Service (SaaS)
Introduction to Software as a Service (SaaS), covering what SaaS is and how it differs from other cloud service models.
Software as a Service (SaaS)
Introduction to Software as a Service (SaaS), covering what SaaS is and how it differs from other cloud service models.
SaaS = use a finished app
SaaS is a provider-run application you access and use. Software as a Service (SaaS) equals finished application. Provider runs and updates the service. You focus on users, devices, and data. Goal: recognize SaaS vs PaaS/IaaS.
Access SaaS, don't host it
You consume the app; you don't manage servers or the OS. Access via browser or client application. No customer-managed servers. No customer-managed Operating System (OS). Responsibilities shift, not disappear.
Shared responsibility (SaaS)
Provider runs the service; you manage access and data usage. Provider: runs and patches the application. Provider: datacenters, power, networking. You: identities and access decisions. You: data organization and sharing.
Your responsibilities in SaaS
You still control access, data sharing, and endpoints. Data: organize, protect, share appropriately. Users: identities, roles, permissions. Devices: endpoints, browsers, client apps. 'Provider-run' does not equal 'risk-free'.
Control clue: SaaS vs PaaS vs IaaS
Classify the model by what you control. Use the app equals Software as a Service (SaaS). Deploy your code equals Platform as a Service (PaaS). Manage the OS equals Infrastructure as a Service (IaaS). Ask: 'What do I control?'
SaaS trade-off
Less control, less operational work. Less control over underlying stack. Provider handles updates and patching. Faster start and reduced maintenance. Best when a standard app fits.
Scenario: sign in and use it
'Finished app plus provider-operated' is a SaaS signal. Need: email, collaboration, customer system. Users sign in and use the application. Provider operates and updates the service. You still manage access and permissions.
Deploying code ≠ SaaS
If you push your own app code, you're in PaaS territory. Team builds an API (Application Programming Interface) or web app. They deploy their own code to a managed platform. That's Platform as a Service (PaaS), not SaaS. 'Managed' doesn't automatically mean SaaS.
Who patches what in SaaS?
Provider patches the service; you manage safe usage and access. Provider: patches servers and Operating System (OS). Provider: maintains the application service. You: permissions, sharing, and governance. You: identity and access controls.
Subscription ≠ SaaS
SaaS depends on who operates and updates the application. Subscription price is not the deciding factor. Local install plus manual updates equals not SaaS. Cloud sync alone doesn't make it SaaS. Ask: 'Who patches and operates the app?'
Pitfalls to avoid
Most SaaS mistakes come from confusing 'who runs what'. SaaS vs PaaS: use app vs deploy code. You don't manage OS/runtime in SaaS. You still own access control. SaaS includes CRM (Customer Relationship Management) and ERP (Enterprise Resource Planning).
Recap: spot SaaS quickly
Use 'what do I control?' to identify SaaS. SaaS: finished app, provider-operated. You manage users, devices, and data usage. Use, Deploy, Manage equals SaaS, PaaS, IaaS.