> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/p/paas-platform-as-a-service.md). # PaaS (Platform as a Service) A cloud computing model that provides a complete platform for developing, running, and managing applications without infrastructure complexity. A cloud computing model that provides customers a complete platform -- hardware, software, and infrastructure -- for developing, running, and managing applications without the complexity of building and maintaining the infrastructure typically associated with developing and launching an app. PaaS sits between Infrastructure as a Service (IaaS) and Software as a Service (SaaS) in the cloud computing stack. While IaaS provides raw compute, storage, and networking, PaaS adds managed runtimes, databases, development tools, and deployment automation. Examples include Heroku, Google App Engine, and Azure App Service. PaaS reduces the operational burden on development teams by handling operating system updates, patching, scaling, and load balancing. Developers deploy application code, and the platform manages everything below the application layer. Serverless platforms can be considered an evolution of PaaS, further abstracting away resource allocation and billing at the function or request level rather than the application level. API gateways on PaaS and serverless platforms provide managed routing and security without infrastructure management. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/p/paas-platform-as-a-service.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.