PaaS & App Deployment
Platforms that deploy and run applications from Git or containers, managed or self-hosted, without managing servers.
25 results in PaaS & App Deployment
Active Pro listings from this category appear first. Your sort applies within Pro and Free results.
Shortlists for PaaS & App Deployment
Explore collections with tools relevant to this category, grouped by deployment, source model or workload.
Self-hosted PaaS platforms for application deployment →
3 matching tools from this category
Cloud providers and deployment platforms for developers →
7 matching tools from this category
European cloud providers for technical teams →
2 matching tools from this category
How to choose paas & app deployment tools
PaaS and app deployment platforms take source code from Git or a container image and turn it into a running service, handling builds, routing, TLS, environment variables, logs and rollbacks for you. Some are managed clouds with usage billing, others are open source control planes you install on your own servers. They sit above raw cloud hosting and container orchestration, trading low-level control for faster, repeatable deployments.
Who uses these tools
- Small teams shipping web apps without dedicated ops
- Developers deploying preview environments per pull request
- Agencies hosting many client projects on own servers
Capabilities to compare
- Git push and container image deployment
- Preview environments and instant rollbacks
- Managed databases and one-click services
- Custom domains, TLS and edge routing
- Scaling, regions and persistent volumes
Operating considerations
- Usage billing spikes from traffic or bandwidth
- Platform shutdowns and migration exits
- Patching and backups for self-hosted control planes
- Build minutes and cold start limits
- Proprietary config files that tie apps down
Selection checklist
- Deploy a representative app with its database and background worker during the trial, not just a static page.
- Model monthly cost at expected traffic, including bandwidth, build minutes and idle instances.
- Check that builds rely on standard Dockerfiles or buildpacks so you can move to another platform.
- For self-hosted options, plan who patches the host, backs up data and monitors the control plane.
What belongs in this category: A product belongs here when it deploys and runs applications from code or images with managed builds and routing, rather than renting bare virtual machines or requiring you to operate an orchestrator directly.
PaaS & App Deployment on iThub in figures
iThub lists 25 tools in PaaS & App Deployment. 10 of 25 are open source, 13 of 25 can be self-hosted, 19 of 25 have a free, freemium or open-source pricing model and 19 of 25 offer an API.
- Tools listed
- 25
- Open source
- 10
- Self-hostable
- 13
- Free to start
- 19
- With an API
- 19
- Web app
- 14
- Desktop app
- 3
Recently added: OpenComputer, Railway, Render, Cyclic
Typical use cases
- Deploying a web app and its database from a Git repository
- Spinning up a preview environment for every pull request
- Hosting side projects on one rented virtual server
- Running containerized APIs across several regions
Trade-offs to model
- Managed platforms remove server upkeep but bill by usage, while self-hosted PaaS runs on a cheap server you must maintain.
- Opinionated platforms make the first deploy fast, but unusual workloads like long jobs or custom networking may not fit.
Common mistakes
- Building on a small hosting platform without an exit plan and scrambling when it shuts down.
- Leaving autoscaling without spending limits and receiving a large bill after a traffic spike or bot crawl.
Compare Coolify and Dokploy →Compare Railway and Render →See self-hosted PaaS platforms →
Continue the technical evaluation
Use the resources that match your decision stage. Profile data and linked sources were refreshed through November 11, 2026.
