An open-source, self-hostable PaaS alternative to Vercel, Heroku & Netlify that lets you easily deploy static sites, databases, full-stack applications and 280+ one-click services on your own servers.
58.2k
Stars
5k
Forks
808
Open issues
30
Contributors
AI Analysis
Coolify is an open-source, self-hostable Platform-as-a-Service that lets developers and teams deploy applications, static sites, databases, and 280+ one-click services on their own servers via Docker and SSH, acting as a self-managed alternative to Vercel, Heroku, and Netlify. It is best suited for technically capable individuals, small teams, and businesses who want cloud-like deployment automation without vendor lock-in or recurring cloud infrastructure bills. It is not intended for non-tec...
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Coolify brings PaaS-style deployment UX to self-hosted infrastructure with 57K+ stars and active daily development
Coolify is a self-hostable platform that lets developers and small teams deploy web apps, databases, and 280+ services on their own servers via a web UI, SSH connection, and one-click workflows. It targets developers and small businesses who want the convenience of managed PaaS platforms (Vercel, Heroku, Netlify) but reject vendor lock-in, per-seat pricing, or data sovereignty concerns. With 57K+ GitHub stars, a funded cloud offering, active sponsorships, and daily commits, it has crossed into genuine mainstream adoption within the self-hosting community.
Started in January 2021 by Andras Bacsai as a side project, Coolify gained significant momentum after Heroku eliminated its free tier in 2022, attracting developers looking for self-hosted alternatives. Version 4 represented a significant rewrite and stabilization effort.
Heroku's free tier removal in late 2022 was a major catalyst. Coolify rode the broader 'self-hosting' wave driven by developer distrust of vendor lock-in and rising SaaS costs. The project earned steady organic growth through developer community content, Reddit/Hacker News discussions, and a strong open-source-first ethos. 301 stars in 7 days as of June 2026 indicates sustained, non-fading momentum three years after the initial surge.
Multiple named commercial sponsors (Hetzner, Hostinger, LiquidWeb, Blacksmith, etc.) suggest real business usage. A paid cloud offering at app.coolify.io implies revenue-generating customer base. Community references and self-hosting forum discussions are widely documented externally. The scale of sponsorship diversity (VPS providers, SaaS businesses, hosting companies) implies real production deployments at meaningful scale. Adoption is verified but exact user count is not publicly disclosed.
Likely a Laravel/PHP monolith backend based on the primary language being PHP, with a web UI likely built on Livewire or similar PHP-driven frontend stack. Likely uses Docker under the hood to orchestrate deployments, and communicates with remote servers via SSH. The 280+ one-click services suggest a template/manifest-driven service catalog. The cloud version appears to share the same codebase. Architecture appears designed for single-operator or small-team deployment.
not documented in README
Last push was on the same day as analysis (2026-06-20), indicating active daily development. The project has been consistently maintained for over 5 years. A funded cloud tier and documented sponsor ecosystem suggest ongoing financial sustainability. README is comprehensive and well-maintained. All signals point to actively maintained and growing, not stagnant.
ADOPT IF: you want to self-host your deployment infrastructure with a Heroku/Vercel-like experience, value no vendor lock-in, and are comfortable managing a Linux server with SSH access. Particularly strong for indie developers, small teams, and agencies deploying multiple projects across owned or rented VPS. AVOID IF: you need enterprise-grade SLAs, complex multi-region Kubernetes orchestration, or if your team lacks Linux/server administration skills — Coolify reduces but does not eliminate infrastructure responsibility. MONITOR IF: you're evaluating it for a growing team with complex deployment needs; watch how the managed cloud offering matures and whether multi-server and team collaboration features reach parity with commercial platforms.
Independent dimensions
Mainstream potential
7/10
Technical importance
7/10
Adoption evidence
8/10
- Single primary maintainer dependency: the project appears heavily driven by one individual (Andras Bacsai), creating bus-factor risk despite growing sponsorship.
- PHP stack may limit contributor pool relative to TypeScript/Go competitors like Dokploy, potentially slowing feature velocity as the project scales.
- Self-hosting complexity is reduced but not eliminated — users are still responsible for server security, backups, and uptime, which may cause frustration for less experienced operators.
- Competitive pressure is intensifying: Dokploy is growing rapidly with 35K stars, and more entrants are likely given the market demand, which could fragment the community.
- Cloud offering sustainability: the open-core business model requires the cloud tier to generate sufficient revenue to fund full-time development; if cloud adoption lags, maintenance pace may slow.
Coolify is likely to remain the reference implementation for self-hosted PaaS through 2027, with gradual expansion of its cloud offering and team-collaboration features. May face meaningful competition from Dokploy but the market appears large enough for coexistence.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://coolify.io
- Language
- PHP
- License
- Apache-2.0
- Last updated
- 4h ago
- Created
- 66mo ago
- Analyzed with
- anthropic/claude-sonnet-4-6
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
[Bug]: Can not select the Server to create a new App on
[Enhancement]: Improve dashboard with operational KPIs and healthcheck visibility
[Bug]: PR preview deploys ignore [skip ci]/[skip cd] in the head commit — only the PR title is checked
Top contributors
Recent releases
Similar repos
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
coollabsio/coolify
this
|
58.2k | +411 | PHP | 8/10 | 4h ago |
 Dokploy/dokploy
|
35.5k | — | TypeScript | 8/10 | 1d ago |
 kubero-dev/kubero
|
4.3k | — | TypeScript | 7/10 | 2w ago |
 zane-ops/zane-ops
|
1.4k | — | Python | 7/10 | 3d ago |
 vitodeploy/vito
|
3.2k | — | PHP | 7/10 | 7d ago |
 MightyMoud/sidekick
|
7.5k | — | Go | 7/10 | 5mo ago |
Dokploy (35K stars, TypeScript) is Coolify's closest direct competitor with a similar self-hosted PaaS premise. Dokploy is newer and growing rapidly, suggesting the market is large enough for multiple entrants. Coolify has a longer track record, a broader service catalog, and a cloud offering. Dokploy may appeal to developers who prefer TypeScript-based tooling.
CapRover is a mature, Docker-based self-hosted PaaS that predates Coolify. Coolify generally has a more polished UI and broader service support. CapRover appears to have stagnated relative to Coolify's active development pace.
These are managed cloud PaaS platforms rather than self-hostable tools. They offer less operational burden but impose vendor lock-in and ongoing per-usage costs. Coolify is the explicit alternative for teams wanting to own their infrastructure. Not direct substitutes but the conceptual category these users left.
Sidekick (7.4K stars, Go) targets a simpler single-server deployment use case. Less full-featured than Coolify but may appeal to users wanting a minimal, CLI-first tool without a web UI or full service catalog.
Portainer is a Docker/Kubernetes management UI, not a PaaS deployment tool. It requires more manual container configuration. Coolify abstracts more of the deployment workflow, making it more accessible to developers who don't want to manage Docker compose files directly.
