PaaSDirectory

The complete guide to Platform-as-a-Service in 2026

Platform-as-a-Service, or PaaS, sits in the middle of the cloud computing spectrum. Below it, Infrastructure-as-a-Service hands you raw virtual machines, networks, and disks that you must configure and maintain yourself. Above it, Software-as-a-Service gives you a finished application you simply log into. PaaS occupies the productive ground between the two: it abstracts away servers, operating systems, patching, load balancers, and scaling, while still letting you deploy your own code and own your application logic. The promise is simple but powerful — you push your code, and the platform handles the undifferentiated heavy lifting of running it reliably at scale.

PaaSDirectory is a curated, vendor-neutral catalog of the platforms that make this possible. Every listing on this page links to a real, verifiable provider and carries an editorial summary written to explain what the platform actually does, who it is built for, and where it fits among the alternatives. We track the full landscape, from the veterans that defined the category to the fast-moving startups reshaping it today, so that engineers, founders, and platform teams can shortlist the right tool without wading through marketing pages.

How the directory is organized

We group platforms into five practical categories. App Hosting covers general-purpose platforms such as Heroku, Render, Railway, DigitalOcean App Platform, and the managed offerings from the big clouds like AWS Elastic Beanstalk, Azure App Service, and Google App Engine — services where you bring application code and the platform runs it. Edge PaaS gathers frontend and edge-first clouds such as Vercel, Netlify, Cloudflare Pages, Cloudflare Workers, and Deno Deploy, which push static assets and lightweight functions to data centers close to your users. Serverless includes event-driven and function platforms like AWS Lambda, Firebase, and IBM Code Engine that scale to zero and bill by execution. Container PaaS covers services that run your container images globally — Fly.io, Google Cloud Run, Koyeb, Porter, and Northflank among them. Finally, Database PaaS collects managed data layers such as Supabase, Neon, PlanetScale, CockroachDB, MongoDB Atlas, Convex, and Aiven, where the database itself is the product.

How to choose a PaaS

The right platform depends on a handful of questions. What languages and frameworks does your stack use, and does the platform support them natively or only through containers? How does pricing scale — is it predictable flat tiers, or pure usage-based billing that can spike under load? Do you need global, low-latency delivery at the edge, or is a single region enough? How important is the ability to scale to zero between bursts of traffic, and how fast does the platform cold-start when traffic returns? Are there data-residency or compliance requirements, such as GDPR or SecNumCloud, that push you toward European providers like Scalingo or Clever Cloud? And critically, how much lock-in are you willing to accept versus running an open-source stack you could self-host or move to your own cloud account?

There is rarely a single best answer. A solo developer shipping a side project values zero-config simplicity and a free tier; a Series-B startup cares about predictable cost and preview environments for every pull request; an enterprise weighs compliance, support SLAs, and the ability to keep workloads inside its own cloud account using a platform like Porter. The platforms below span all of those needs. Use the category filters and search bar to narrow the list, read the editorial summaries to understand the trade-offs, and follow the links to each provider to evaluate current pricing and features for yourself.