---
title: "PaaS"
description: "PaaS is a cloud model where the provider delivers a ready application runtime. Learn how PaaS differs from IaaS and SaaS and where it fits best."
url: "https://nodea.io/en/glossary/paas"
lang: "en"
updated: "2026-07-13"
---

# PaaS

> PaaS (Platform as a Service) is a cloud model in which the provider supplies a complete environment for building and running applications, removing the need to manage servers and operating systems.

**PaaS** (Platform as a Service) is a cloud service model in which the provider delivers a ready-made environment for building, deploying and running applications. The development team focuses on code and data, while the underlying layers — hardware, operating system, runtime and scaling mechanisms — remain the platform operator's responsibility.

## How the PaaS model works

Cloud computing is usually described in three core layers: [IaaS](https://nodea.io/en/glossary/iaas) (raw infrastructure), PaaS (the platform) and [SaaS](https://nodea.io/en/glossary/saas) (finished software). PaaS sits in the middle: the provider handles servers, networking, OS patching and runtime configuration, while the customer pushes an application through a dashboard or a CI/CD pipeline and controls its settings.

A typical PaaS offering bundles runtimes for popular languages (PHP, Python, Node.js, Java), managed databases, message queues, caching layers, plus automatic scaling and load balancing. Billing is usually based on resource consumption, and shipping a new version comes down to pushing code to a repository.

## Practical application

PaaS shines wherever delivery speed and reduced operational overhead matter. A startup can launch a web application in minutes without hiring a team to maintain servers, and the platform absorbs traffic spikes by adding instances automatically. The model pairs naturally with a [DevOps](https://nodea.io/en/glossary/devops) culture and [CI/CD](https://nodea.io/en/glossary/ci-cd) pipelines, because every deployment is repeatable and automated.

The trade-off is reduced control over the lower layers — tuning the operating system or an unusual configuration is harder. Teams that need full freedom more often reach for IaaS or their own [VPS servers](https://nodea.io/en/glossary/vps), where they build the environment themselves and pay for that flexibility with more administrative effort.

### How does PaaS differ from IaaS?

With IaaS you get raw infrastructure — virtual machines, storage and networking — and install the operating system and software yourself. With PaaS the provider also manages the OS, runtime and scaling, and you simply deploy your application code. PaaS is more convenient but offers less control over the lower layers than IaaS.

## Related

- [IaaS (Infrastructure as a Service)](https://nodea.io/en/glossary/iaas)
- [SaaS](https://nodea.io/en/glossary/saas)
- [Cloud](https://nodea.io/en/glossary/cloud)
- [Serverless computing](https://nodea.io/en/glossary/serverless-computing)
- [DevOps](https://nodea.io/en/glossary/devops)

---

Languages: [pl](https://nodea.pl/pl/slownik-pojec/paas.md)  
Site index: [llms.txt](https://nodea.io/en/llms.txt)