Definitions · Service models
What is PaaS?
What is PaaS? A cloud model where the provider runs the platform and you deliver code: what it covers, where the line sits, how it is listed.
Platform as a Service (PaaS) is a cloud model in which the provider runs the platform beneath an application - operating system, runtime, scaling machinery - while the tenant supplies code, configuration and data. The unit of work is a deployment, not a machine.
That shift is the whole point of the model. A team using PaaS stops provisioning servers and starts shipping builds: patching, failover and capacity sit with the provider, while the team owns what the application does and how it behaves. PaaS trades some freedom over the environment for a much shorter path from source repository to running service, which is a good trade whenever the environment itself was never the differentiator.
What a platform takes off your plate
A PaaS offering is best read as a list of things nobody has to build:
None of this makes the system underneath irrelevant. A tenant chasing a slow request still has to reason about the database it touches, the network path in between and the limits the platform enforces; the abstraction decides who repairs the machinery, not whether the machinery is involved. It also sets a ceiling on what may be changed: a platform that supports a fixed set of runtimes and add-ons will decline a requirement outside that set, and the refusal arrives as a product limitation rather than as a queue of work for your own team. Teams that read a platform as permission to stop thinking about infrastructure generally rediscover the boundary during their first serious incident, when the provider's support terms become the only question that matters.
- Runtime environment - language runtimes and frameworks available without provisioning machines for them.
- Deployment path - a build from source, a container image, or a command that turns either into a running service.
- Backing services - databases, caches, queues and object stores bound to the application as dependencies.
- Scaling and recovery - instances restarted, balanced and grown by rules the platform enforces.
- Operations above the runtime - patching, certificate renewal and failover handled by the provider.
The price of that list is legibility. A PaaS tenant generally cannot point at the machine running a process, choose its kernel, or install a system-level agent - the platform abstracts those details away. When a workload needs one of them back, it usually moves down a level rather than fighting the abstraction.
Where PaaS sits
PaaS occupies the middle of the service-model stack: below infrastructure you configure yourself, above software you simply use. The three are easy to confuse when they are described side by side, so the comparison itself is kept in one place - IaaS, PaaS and SaaS on VirtEngine - while this page defines only the middle term.
Two neighbours belong in the picture. Packaging the application as a container is how most modern platforms receive deployments, and code that needs only an event handler can go one step further into serverless execution. Both are adjacent to PaaS rather than replacements for it.
Teams that choose a platform, and teams that should not
PaaS fits product teams shipping frequently, organisations without the operations headcount to run infrastructure, and services whose value is the application logic rather than the machinery underneath. It is also a natural home for APIs, web front ends and back-end services that scale in the same shape as the traffic they serve.
It fits less well when the workload dictates the environment: software needing an unusual kernel or device driver, long-running batch or numerical jobs, systems requiring specific network topologies, or teams bound by strict rules about which systems may process their data. Those constraints are worth discovering before a migration, not after it.
Platforms published as offerings
On VirtEngine a PaaS is something a provider can put on sale. The listing states what the platform includes - runtime versions, backing services, quotas, the size of the machines behind it - so a buyer can compare offers on contents rather than on marketing language. Placing the order opens an escrow account, which the provider can inspect before provisioning anything.
Fulfilment routes the matched lease into the provider's control plane, where the project is created and its resource allocations are metered. Usage arrives as signed records, and once the dispute window closes the validated line items are taken from escrow, with unspent balance returning to the tenant. Neither party starts anonymously: identity verification precedes matching on both sides.
In practice
A managed platform appears as a catalogue entry whose runtime, quotas and price are stated up front; ordering funds escrow and the provider meters what the project draws from it.
Questions
Asked about what is paas
What does PaaS stand for?
Platform as a Service. The provider runs the operating system, runtime and scaling machinery, while you deliver your own application code and data into that platform.
What is the difference between PaaS and IaaS?
With IaaS you are given machines and manage everything on them; with PaaS you are given a deployment target and manage only the application. The boundary between the two is where the platform stops and your responsibility begins.
Is container hosting a form of PaaS?
Usually yes. Managed container platforms provide a runtime, deployment path, scaling and backing services, which is the PaaS shape even when the underlying unit is a container rather than a virtual machine.
How does a platform get sold on a marketplace?
As a listing that declares its contents and quotas. The tenant funds escrow when ordering, the provider provisions the project through its control plane, and metered usage settles against that escrow after a dispute window.
Related
Keep reading
- What is IaaS? What is IaaS? Rented compute, storage and networking you configure yourself: the service model, its boundary, and how instances are listed.
- What is SaaS? What is SaaS? Software run by a provider and used over a network instead of installed: what it replaces, what you keep control of, how plans are sold.
- What is containerization? What is containerization? Packaging an application with its dependencies into an image that runs the same everywhere: built once, run anywhere.
- What is serverless computing? What is serverless computing? Code run in short-lived executions by a cloud provider and billed while it runs: how it works, its limits, its listings.
- What is an Open Source Cloud Platform? The software you run to operate a cloud yourself: what an open source cloud platform includes, how it differs from managed cloud, and how providers connect it to a marketplace.
- All definitions Every cloud and marketplace term, defined in one place.
Longer explainers live in Learn; the full vocabulary is in the marketplace glossary.