Deployment/PaaS

Coolify60.4k★

Coolify is a self-hosted PaaS that handles deployment, SSL, database provisioning, and reverse proxying for your applications. Point it at a server, connect your Git repos, and it handles builds, deployments, SSL certificates, and reverse proxying. It's your own private Heroku running on a $5/mo server. Self-hosting is free under Apache 2.0. You get automatic deployments from Git, built-in database provisioning (Postgres, MySQL, Redis, MongoDB), wildcard SSL via Let's Encrypt, and a clean dashboard. It's impressive how much it covers. The catch: you're trading money for ops time. When a deployment fails at 2 AM, there's no support team. It's you and the Docker logs. The managed cloud option starts at $5/mo per server but you're still managing the underlying infrastructure decisions. And Coolify itself needs updates, which occasionally break things if you're not careful with the upgrade path.

1Panel36.5k★

1Panel is a control panel for your server: a web dashboard that lets you install apps, host websites, manage Docker containers, set up SSL, and schedule backups without living in the command line. It's the open source answer to cPanel, with a 165-app marketplace and native AI agent support so you can spin up local LLMs through Ollama right from the UI. GPLv3 and free for the community edition. The ops reality is the host itself. 1Panel runs on a Linux VPS with as little as 1GB of RAM, and once it's installed it takes most of the busywork off your plate. You still own patching the OS and securing SSH, but deploying and updating apps gets a lot friendlier. Solo and small: the free edition is plenty for a single box, and the price is zero. Teams running more than one server hit the wall fast, since multi-node management and the advanced WAF live in Pro at $80/year. That is fair pricing for what you get. The catch: a control panel is a big attack surface sitting in front of everything on your server. Lock down the login, keep it patched, and don't expose the admin port to the open internet, because one compromised panel hands over the whole machine.

Dokku32.1k★

It's a single-server PaaS (platform-as-a-service) that turns any Linux box into a deployment platform. Git push, automatic Docker build, zero-downtime deploys, SSL via Let's Encrypt, and plugin support for databases. This is the tool for developers who want the simplicity of Heroku without the cost, and who have one server (not a Kubernetes cluster). Perfect for side projects, MVPs, internal tools, and small production apps. MIT, battle-tested for years. The most popular self-hosted PaaS. The catch: single server only. When you outgrow one box, Dokku doesn't scale horizontally. You graduate to Kubernetes, Coolify, or a managed platform. Also, you're the ops team. SSL renewals, server security patches, database backups, monitoring, all on you. Dokku makes deployment easy but doesn't make operations disappear.

vercel16.1k★

This repo is the Vercel CLI and the build adapters behind it, all Apache-licensed and free. `vercel dev` runs your app locally, `vercel deploy` ships it, and the framework adapters turn a Next.js or Node project into deployable output. The tooling is open. What it deploys to is not. You can run the CLI for nothing and even `vercel build` to produce the output and host it wherever you want. Most people don't. The point of the CLI is the Vercel platform on the other end, and that's where the meter starts. Vercel's Hobby tier is free and fine for side projects: a few hours of active CPU a month, a million function calls, 100GB of transfer. Pro is $20 per user a month plus usage, and the enterprise add-ons climb fast, with SAML SSO alone running $300/mo. Solo devs and small teams live on Hobby or low Pro. Larger teams should price the usage and the add-ons before committing, because the platform bill, not the CLI, is the real cost. The catch is that this is open-source tooling for a closed platform. The CLI is a pleasure to use, but the value you pay for, the edge network, the builds, the analytics, lives behind Vercel's infrastructure, not in this repo. Treat it as a client, not a product you own.

CapRover15.1k★

CapRover is a platform-as-a-service (PaaS) you install on your own server. One-click apps, automatic SSL via Let's Encrypt, Docker under the hood. Setup takes about 20 minutes on a fresh Ubuntu server. After that, you get a web dashboard where you can deploy apps from Git, Docker images, or one-click templates (WordPress, Postgres, Redis, Ghost, etc.). It handles nginx reverse proxying, SSL certificates, and Docker orchestration automatically. Mature and stable. The community is active and the one-click app library is extensive. Completely free. No paid tier. No cloud offering. You bring the server, CapRover runs on it. The catch: single-server by default. You can add worker nodes for horizontal scaling, but it's Docker Swarm underneath, not Kubernetes. For most small-to-medium workloads, that's fine. But if you're scaling to dozens of services, Coolify (which also does this) has more active development, or Dokku if you want something even simpler. CapRover's web UI is functional but dated. And if something breaks at the Docker/nginx layer, you're debugging it yourself.

zane-ops1.4k★

ZaneOps is a self-hosted PaaS (platform-as-a-service) that aims to be the open source Heroku/Railway. Push your code or Docker image, ZaneOps handles deployment, HTTPS, environment variables, and scaling on your own server. Built in Python with a modern UI, it targets developers who want the convenience of Heroku but on their own $5-20/mo VPS. Zero-downtime deployments, automatic SSL via Let's Encrypt, and a clean dashboard. MIT, fully free. No paid tier. The catch: this is very early. Small team, and competing against Coolify which does the same thing with a much larger community. The feature set is thinner: no built-in database management, fewer one-click app templates, less documentation. If you want a self-hosted PaaS today, Coolify is the safer bet. ZaneOps is interesting to watch if you prefer its Python stack or UI approach, but it's not production-ready for anything critical.

openchoreo1.4k★

OpenChoreo is an internal developer platform you run on your own Kubernetes cluster. The idea is to give your developers a Heroku-style experience, push code and get a running app with CI/CD and observability, without making them learn Kubernetes, while your platform team keeps full control underneath. It's the open source foundation of WSO2's commercial Choreo product, Apache 2.0 licensed. This is platform infrastructure, so the ops burden is heavy and unavoidable. There's no standalone mode. You need a Kubernetes cluster, and OpenChoreo installs as a multi-plane system: control, data, observability, and a Backstage-powered developer portal on top. You can kick the tires locally with K3d or a dev container, but a real deployment is a serious platform-engineering project, not an afternoon. This is for platform teams building an internal PaaS, not for individual developers. If you're a group of platform engineers tired of gluing together Backstage, Argo CD, and a pile of controllers, OpenChoreo bundles that into one opinionated system. Small teams and solo devs should look at Heroku, Render, or Vercel instead. The whole point of OpenChoreo is to serve many developers behind a platform team. The catch is maturity and gravity. It's a CNCF Sandbox project, which is the earliest tier, so it's promising but young. And an internal developer platform is one of the heaviest things a team can adopt. Once your org runs on it, moving off is expensive. Great fit if you're already committed to running your own platform on Kubernetes. Overkill for anyone who isn't.

swiftwave890★

Swiftwave handles it. Point it at a VPS, push your code, and it builds, deploys, and manages SSL certificates automatically. Think Coolify or Dokku but written in Go with a focus on simplicity over features. Everything is free under Apache 2.0. No paid tier, no hosted cloud version. You get Git-based deployments, automatic SSL via Let's Encrypt, a web dashboard, and built-in support for Postgres, MySQL, Redis, and MongoDB. The setup is straightforward: single binary, minimal dependencies. The catch: this is early-stage. The community is small, documentation has gaps, and you're betting on a project that hasn't proven long-term sustainability. Coolify has 10x the community and more features. Swiftwave's advantage is simplicity (fewer moving parts, less config), but that also means fewer escape hatches when you need something custom.