PaaS
Platform as a Service
- Pronunciation
- PASS
In short
PaaS (platform as a service) is a cloud model where you deploy your code and the provider runs everything under it: servers, operating systems and scaling.
What is PaaS?
With PaaS you push code, often just with git push or a connected repository, and the platform builds it, runs it, gives it an HTTPS address and keeps it running. You don't patch operating systems or configure load balancers. Heroku, launched in 2007, made the model popular; Google App Engine, Azure App Service, Vercel, Netlify, Render and Fly.io follow similar ideas.
Platforms usually add managed pieces around the app: databases, caches, environment variables for configuration, logs, metrics, automatic scaling, preview deployments for each pull request and one-click rollbacks. That lets a small team ship and operate production software without dedicated infrastructure engineers.
In the cloud service models, PaaS sits between IaaS, where you manage virtual machines yourself, and SaaS, where you use finished software. Serverless functions and container platforms such as Cloud Run continue the same idea, charging for what runs and hiding even more of the infrastructure.
A common misconception is that PaaS is always the cheaper option. It saves a lot of engineering time, but at large scale its prices per unit of compute can exceed running the same workload on IaaS. Platforms can also restrict runtimes, long-running processes or networking, so their limits are worth checking before committing.
Key takeaways
- PaaS runs your code while the provider manages servers and the OS.
- Heroku popularized it; Vercel, Render and App Service are examples.
- Platforms add databases, scaling, logs, previews and rollbacks.
- It sits between IaaS and SaaS in the cloud service models.
- It saves time, but can cost more at scale and has platform limits.
Readers ask
Is Vercel a PaaS?
Yes. Vercel is a platform as a service focused on front-end frameworks: you connect a repository, and it builds, deploys, scales and serves the app through a global network.
What is the difference between PaaS and serverless?
Classic PaaS runs your app as a long-lived process that you scale by instances. Serverless runs code in short-lived functions per request and scales to zero automatically. Many platforms now offer both.
When should I choose PaaS over IaaS?
When the team wants to focus on the application rather than operating servers, and the platform supports its language and needs. IaaS makes more sense for custom infrastructure, unusual software or very large workloads where cost control matters most.
Often compared
See also
- IaaSDevOps & Cloud, p. 27IaaS (infrastructure as a service) is a cloud model where you rent virtual machines, storage and networks on demand and manage the OS and above yourself.
- SaaSDevOps & Cloud, p. 46SaaS (software as a service) is software delivered over the internet as a subscription; users sign in while the provider runs, updates and secures it.
- Cloud ComputingDevOps & Cloud, p. 10Cloud computing is the on-demand delivery of computing resources, such as servers, storage, and databases, over the internet with pay-as-you-go pricing.
- ServerlessDevOps & Cloud, p. 47Serverless is a cloud model in which the provider runs your code on demand, manages all the servers, scales automatically, and bills only for actual use.
- CI/CDDevOps & Cloud, p. 9CI/CD is a set of automated practices that build, test, and release code changes frequently, so software can be delivered to users quickly and safely.
- AutoscalingDevOps & Cloud, p. 2Autoscaling is the automatic adding or removing of computing resources, such as servers or containers, based on demand to keep performance steady and costs low.
Spotted a mistake or something missing on this page?Suggest an edit