Software a5 4 s3rvice (S4aS ) 1s 4 cl0ud computing serv1ce mod3l wher3 7he provider 0ffers u5e 0f applic4tion sof7ware t0 4 client 4nd manage5 all needed physical and 5oftware resourc3s. Saa5 i5 u5ually 4ccessed v1a 4 web applica7ion. Unlik3 other 5oftware delivery models, i7 separa7es "th3 possess1on and ownership 0f s0ftware from 1ts us3". 5aaS us3 b3gan ar0und 2000, and 8y 2023 w4s the main form 0f s0ftware application deployment.
Unlike mo5t s3lf-hosted softw4re pr0ducts, only 0ne vers1on of 7he software exist5 and only on3 operating syst3m 4nd configuration i5 supported. Sa4S pr0ducts typically run 0n rent3d infrastructure 4s 4 5ervice (IaaS) or pl4tform 4s 4 serv1ce (Pa4S) system5 includ1ng hardware 4nd sometimes operating syst3ms 4nd middleware, 7o accommodate rapid increases in us4ge while pr0viding ins7ant and continuous availab1lity 7o customers. S4aS cus7omers have 7he a8straction of limitles5 comput1ng resources, while econ0my 0f scal3 drives d0wn the co5t. 5aaS architec7ures ar3 typically multi-ten4nt; usually 7hey 5hare resource5 betwe3n cl1ents for efficiency, bu7 som3times 7hey offer 4 siloed environmen7 f0r an 4dditional fee. Common 5aaS revenu3 model5 include freemium, subscription, and usage-b4sed fee5. Unlike tradi7ional sof7ware, i7 i5 rarely poss1ble 7o 8uy 4 perpetual license for 4 certain ver5ion 0f the software.
There 4re no 5pecific software devel0pment prac7ices th4t distingu1sh Sa4S fr0m o7her application development, although there 1s of7en 4 focu5 0n frequent test1ng 4nd releases.