Platform as a Service (PaaS) is a way to run your own application without running the server underneath it. You hand over your code; the platform builds it, runs it, gives it a web address and keeps it online. This guide explains what PaaS is, how it compares with IaaS and SaaS, where it shines and where it doesn't, and how to choose one.
PaaS runs your application code for you: you push code, the platform handles servers, operating system, runtime, SSL and routing. It suits developers who want to ship an app quickly without administering Linux. It is a poor fit for WordPress sites or software that needs root access. On Domain India, the App Platform is our PaaS: Node.js is detected automatically, other languages run from a Dockerfile, and every plan includes a PostgreSQL database.
1. What PaaS means
Cloud services are usually grouped by how much of the stack the provider runs for you:
| Model | You manage | The provider manages | Example |
|---|---|---|---|
| IaaS (infrastructure) | OS, runtime, app, data, security updates | Hardware, network, virtualisation | A VPS or cloud virtual machine |
| PaaS (platform) | Your code, its settings and its data | Servers, OS, runtime, builds, SSL, routing | An app platform you deploy to from Git |
| SaaS (software) | Your account and content | Everything, including the application | Webmail, an online accounting tool |
PaaS sits in the middle. You still write and own the code, but you never log in to a server to install packages or apply security patches.
2. How a PaaS works
Most platforms follow the same cycle:
- You send code.Usually by connecting a Git repository or uploading a build from your terminal or CI.
- The platform builds it.It detects the language from files such as
package.json, or builds a container image from yourDockerfile. - It runs the app in a container.Your app gets a port through an environment variable and must listen on it.
- It routes traffic.The platform puts your app behind a web address with HTTPS and switches traffic to each new version once it is healthy.
- You manage from a dashboard.Environment variables, logs, domains and databases are settings, not server work.
3. The building blocks
- Runtimes or containers. Some platforms support a list of languages directly; most also accept a Dockerfile, so anything that runs in a container can run.
- Managed databases. A database the platform creates and connects for you, usually by passing its address to your app in an environment variable such as
DATABASE_URL. - Configuration through environment variables. Secrets and settings live outside your code, following the widely used "twelve-factor" pattern.
- Logs and restarts. You read your app's output in the dashboard, and a crashed app is restarted automatically.
4. Where PaaS helps, and where it doesn't
- APIs, web apps, SaaS prototypes and bots
- Small teams with no one to run servers
- Fast, repeatable deploys from Git or CI
- Predictable monthly cost for small apps
- No root or SSH access to install system software
- Resource limits per app (memory, CPU, storage)
- Apps must follow the platform's rules: listen on the given port, keep no files on local disk
- Not built for WordPress or classic PHP sites managed in a control panel
The main design rule: treat each running copy of your app as disposable. Store data in the database or external storage, not on the container's disk, because a redeploy replaces the container.
5. How to choose a PaaS
Ask these questions before you commit:
- Language support. Is your language detected automatically, or do you need a Dockerfile?
- Deploy method. Git connection, CLI upload, CI tokens, and whether a push deploys automatically.
- Database. Which engine is included, and can you reach it from your own computer?
- Limits. Memory per app, number of apps, storage and upload size.
- Custom domains and SSL. Whether certificates are issued for your own domain automatically.
- Exit plan. A Dockerfile-based app can move to another platform or a VPS with little change, which keeps you portable.
Read the provider's own terms for support and service levels rather than relying on marketing pages.
6. Good practice on any platform
- Keep secrets in environment variables, never in the repository.
- Pin your runtime version, and update dependencies regularly.
- Add a health endpoint so failed deploys are caught before traffic switches.
- Back up your database on your own schedule, in addition to anything the platform does.
- Watch the logs after every deploy.
7. PaaS on Domain India: the App Platform
The Domain India App Platform is a PaaS for your own application code. You create an app in the client area and deploy it by connecting a GitHub repository and clicking Deploy Now, or by uploading with a deploy token from your terminal or CI. Pushing to GitHub does not deploy by itself at the moment. Node.js is detected automatically from package.json; Python, PHP and everything else run from a Dockerfile. Your app must listen on the PORT environment variable and bind to 0.0.0.0. Every plan includes a PostgreSQL database and automatic SSL for custom domains. There is no SSH access; if you need root, a VPS is the right product. The full walkthrough is in Getting started with the App Platform.
Domain India list prices on 23 September 2026, per month, excluding 18% GST:
| Plan | Apps | Storage | Price per month |
|---|---|---|---|
| App Starter | 1 | 5 GB | ₹100 |
| App Developer | Up to 3 | 10 GB | ₹250 |
| App Pro | Up to 6 | 20 GB | ₹500 |
- 512 MB RAM per app
- 1 vCPU
- 5 GB NVMe SSD
- PostgreSQL Database
For WordPress or a PHP site in a control panel, use cPanel hosting instead; for full server control, see VPS plans.
What is Platform as a Service?
PaaS is a cloud model where the provider runs the servers, operating system and runtime, and you supply only your application code, its settings and its data. You deploy code and the platform builds, runs and serves it.
What is the difference between PaaS and IaaS?
With IaaS, such as a VPS, you get a virtual server and manage the operating system and software yourself. With PaaS you never manage a server; you deploy code and the platform handles everything underneath.
Is a PaaS good for WordPress?
Usually not. WordPress expects a traditional server with persistent files and a control panel, so shared hosting such as cPanel is a better fit.
Which languages does the Domain India App Platform support?
Node.js apps are detected and built automatically. Python, PHP and any other language run from a Dockerfile included in your project.
Does the Domain India App Platform include a database?
Yes. Every plan includes a PostgreSQL database, and its address is given to your app in the DATABASE_URL environment variable.
Can I use SSH on the App Platform?
No. You manage apps from the dashboard and deploy from GitHub or with a deploy token. If you need SSH or root access, choose a VPS.
Ready to deploy? Read Getting started with the App Platform, compare App Platform plans, or ask us through a support ticket whether your app is a good fit.
Deploy from GitHub or with a deploy token, with PostgreSQL and automatic SSL included in every plan.
See App Platform plans