Self hosted PaaS on your own servers, without hosting the platform
A PaaS platform gives you git push deploys, logs and rollback without thinking about servers. A self hosted PaaS gives you the same experience on machines you own, at your provider's price. Deployment combines the two: the platform layer is hosted and maintained by us, the apps and data run on your servers in your cloud account.
The two costs of a classic PaaS platform
The first cost is the bill. Managed platforms such as Heroku, Render and Railway charge per app, per instance size and often per gigabyte of bandwidth or memory, so a small team with an API, a frontend, two workers and a database can pay several times what the same resources cost as a plain server. The second cost is control. You cannot pick the exact runtime build, inspect the machine, colocate a worker with its database, or keep the data in a specific provider account.
Self-hosting the platform with an open-source tool removes the bill but adds a new job: you now run, update, secure and back up the platform itself.
A PaaS experience where the servers are yours
With Deployment, the workflow feels like a platform, while the runtime is a normal Linux server you can SSH into.
- Push to a branch and the app deploys, with build logs streamed in the panel
- Each deploy is an atomic release that switches only after a health check
- Rollback is one click to any kept release
- Workers, daemons and cron are declared per site and restart on deploy
- Environment variables are encrypted per environment with a diff before deploy
- Logs, metrics, uptime checks and alerts are built in
See the full workflow on web app hosting.
Managed PaaS, self-hosted panel and Deployment side by side
| Managed PaaS platform | Self-hosted open-source panel | Deployment | |
|---|---|---|---|
| Where apps run | Provider's infrastructure | Your servers | Your servers |
| Who runs the platform | Provider | You | Deployment |
| Compute pricing | Per app and usage, with markup | Provider price | Provider price |
| Platform price | Included in compute | Software is free, your time is not | Flat plan by server count |
| Root access | No | Yes | Yes |
| Lock-in | Buildpacks, add-ons, proprietary config | Panel config | Plain nginx, systemd and release folders |
| If the platform is down | Apps may be affected | Panel is your problem | Apps keep running on your servers |
For a deeper comparison read heroku alternative and coolify alternative.
Native runtimes or containers, your choice
Many self hosted PaaS tools require every app to be a container. Deployment runs apps natively when that is simpler: PHP-FPM behind nginx, Node.js under systemd, Gunicorn or Uvicorn for Python, Puma for Rails, a compiled Go binary, a Spring Boot jar or an ASP.NET Core service. If your repository has a Dockerfile or a compose file, Deployment builds and runs it instead. Both use the same releases, health checks and rollback.
Databases and backups next to your apps
Add MySQL, MariaDB, PostgreSQL or Redis on the app server or on a dedicated database server, with users and grants from the panel. Scheduled backups go to your own S3-compatible storage, so a platform change never puts your data at risk.
What a self hosted PaaS costs with Deployment
The arithmetic is simple. You pay your cloud provider for the servers at its list price, plus one flat plan. Take a team of five running four apps with two workers and PostgreSQL on two 8 GB servers. On a classic PaaS platform each app, worker and database is billed separately. On Deployment the same setup is two servers at your provider's price plus Team at 99 USD a month billed yearly. Check current prices of any PaaS on its own pricing page before comparing.
No lock-in by design
Everything Deployment configures is standard Linux: nginx or Caddy config files, systemd or supervisor units, cron entries and release folders with a current symlink. If you stop using Deployment, the servers keep running exactly as they are, and you can maintain them by hand or with another tool.
Stacks supported on the platform
PHP and Laravel, Node.js and Next.js, Django, FastAPI and Flask, Ruby on Rails, Go, Java with Spring Boot, .NET, static sites and Docker. Servers can live on any provider through cloud server management or be connected over SSH.
Which plan fits your platform
| Plan | Monthly | Yearly per month | Yearly billed | Servers |
|---|---|---|---|---|
| Starter | 49 USD | 24 USD | 288 USD | 3 |
| Team | 199 USD | 99 USD | 1 188 USD | 15 |
| Agency | 499 USD | 249 USD | 2 988 USD | 60 |
| Enterprise | 1 499 USD | 749 USD | 8 988 USD | 250 |
More on PaaS pricing.
Is Deployment open source?
No. Deployment is a hosted platform, so you do not install or maintain it. Everything it configures on your servers is standard open-source software such as nginx, Caddy, systemd and supervisor.
Do I need Kubernetes?
No. Deployment uses single servers or a handful of them with atomic releases, which covers most web apps without cluster complexity.
Can I scale an app across several servers?
Yes. A site can deploy to more than one server, each with its own release folders, behind a load balancer you choose in your cloud account.
Can I try Deployment before I pay?
Yes, with the free one-time demo on the home page. Plans start at 49 USD a month, or 24 USD a month billed yearly.
Get the PaaS workflow on your own servers
Connect a server and ship your next push with the comfort of a platform and the bill of a VPS.
Paste a repository and Try the demo to see the generated plan.
$ git push origin main
✓ build release 20261019-142210
✓ health check 200
✓ switch current 0.4 s
$