Platform as a Service (PaaS) is a cloud service that gives development teams a ready-made environment for building, deploying and running their own applications. The provider manages the servers, operating systems, language runtimes and much of the supporting software; your team supplies the application code and data and configures how it runs. It sits between Infrastructure as a Service (IaaS), where you manage the operating system yourself, and Software as a Service (SaaS), where you use a finished application.
At a glance
- The provider runs the infrastructure, operating system and runtime; you deploy code and manage your data and settings.
- Many platforms add managed databases, caching, queues, logging and automatic scaling as services you switch on.
- Pricing is usually usage-based: compute capacity plus each managed service you use.
- It speeds up delivery for many web, API and internal applications, but may not fit software that needs low-level control of the operating system or hardware.
- The trade-off for less operations work is closer dependence on the provider’s platform.
What problem it solves
Running applications on your own servers, or on rented virtual machines, means someone has to choose operating systems, patch them, install language runtimes, plan capacity, set up load balancing and monitor it all. For many teams that work adds little to the product but takes a large share of their time.
PaaS takes most of it off the team. Developers push code, and the platform builds it, runs it, restarts it if it fails and adds capacity when traffic grows. New environments for testing can be created in minutes. This tends to help most where teams are small, release often, or are building new web applications and APIs.
How it works
Build and deploy. Developers push code or a container image to the platform. The platform builds it into a runnable release, applies configuration and secrets, and deploys it, often with options for gradual rollout and rolling back to an earlier release.
Runtime and scaling. The platform runs the application on supported language runtimes or as containers. You set how many instances to run or rules for scaling, and the platform places them, checks their health and replaces failed ones.
Managed services. Databases, caches, message queues, search and storage can usually be added as services, with connection details passed to the application automatically. This is where much of the convenience, and much of the lock-in, comes from.
Operations. Many platforms collect logs and metrics, provide dashboards and alerts, and handle encryption in transit for public endpoints.
Shared responsibility. Under the shared responsibility model, the provider is typically responsible for the infrastructure, operating system patching and runtime updates it manages. You are responsible for your code and its dependencies, your data, who can access the platform, and how you configure network access and services.
Designing for the platform. Applications run best on PaaS when they don’t store data on the server itself, because instances can be replaced at any time. Files go to object storage and sessions to a shared cache or database. Moving a large existing application onto PaaS without these changes often causes problems.
When it matters for buyers
- When building new applications or APIs. PaaS can shorten the time from idea to running service and reduce the operations staff needed.
- When deciding between PaaS, IaaS and SaaS. If a finished SaaS product meets the need, building on PaaS may not be worth it; if the software needs full control of the operating system, IaaS may fit better.
- When cloud costs need control. Autoscaling and always-on test environments can drive spend up; budgets, tagging and FinOps practices help.
- When connectivity and security matter. Private connections to the platform and protection for public endpoints are often needed for business applications.
Our Public Cloud guide covers how PaaS fits within the wider set of cloud services.
Questions to ask vendors
- Which languages, runtimes and versions are supported, and how much notice do you give before retiring one?
- How does scaling work, and are there limits on instances, connections, memory or request duration?
- Which managed services are included, and how are they priced as usage grows?
- What are you responsible for in security and patching, and what remains ours?
- What uptime commitment applies, and does it cover the managed services as well as the runtime?
- Can we connect privately from our network, and can we restrict public access to our applications?
- How would we move our applications and data off the platform if we needed to?
How it differs from IaaS
With IaaS you rent virtual servers, storage and networks and manage everything from the operating system up. PaaS adds a managed layer on top: the provider also handles the operating system, runtime, scaling and often the database, and you deploy only your code and data. IaaS gives more control and runs most existing software unchanged; PaaS removes more operations work but ties your application more closely to the provider’s platform. Many organizations use both, along with SaaS.
Problems this helps with
- Developers waiting on servers and patching before they can ship
- Small teams spending more time on infrastructure than on the product
- Apps that can't scale up for busy periods without manual work
- Worry about getting locked into one cloud provider's platform

