coollabsio/coolify

An open-source, self-hostable PaaS alternative to Vercel, Heroku & Netlify that lets you easily deploy static sites, databases, full-stack applications and...

View on GitHub ↗Jump to charts ↓Open shareable report →

coollabsio/coolify has 63k+ stars and 5.5k+ forks on GitHub, is written in PHP, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on August 30th, 2026
Created on January 25th, 2021
Open Issues & Pull Requests: 588 (+0)
GitHub issues: Enabled
Number of forks: 5,686
Total Stargazers: 63,153 (+2)
Total Subscribers: 197 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.6 hours
Mean response time: 22.5 days
90th percentile: 44.6 days
Tracked items: 4,009

Maintainer activity

6 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 10% of issues opened in the past year have never received a reply. 98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "💤 Waiting for feedback" is answered fastest, typically in about 3 hours, while "🖌️ UI/UX" waits about 3 days. 62% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. 80% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 448
New in 7 days: 15
Closed in 7 days: 106
Avg open age: 320 days
Stale 30+ days: 413
Stale 90+ days: 323

Recent activity

Opened in 7 days: 14
Closed in 7 days: 104
Comments in 7 days: 15
Events in 7 days: 127

Top labels

  • 🔍 Triage (689)
  • 🐛 Possible Bug (623)
  • 💤 Waiting for feedback (107)
  • 🐞 Confirmed Bug (96)
  • ✅ Done (69)
  • 🚧 Next (52)
  • 🔧 Improvement (50)
  • 🖌️ UI/UX (49)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Coolify is an open-source, self-hostable platform-as-a-service that lets you deploy applications, databases, and services on your own servers as an alternative to managed platforms like Heroku, Netlify, and Vercel.

The tool solves the problem of vendor lock-in and high hosting costs by providing a self-hosted deployment system that works with any server you control via SSH. It manages VPS, bare metal, and single-board computers, automating application and database deployment while keeping all configuration on your own infrastructure. If you stop using Coolify, your running resources remain functional and manageable without the platform's automation layer.

Coolify suits teams and individuals who want control over their infrastructure, prefer to avoid recurring cloud platform fees, or need to deploy across heterogeneous hardware. The self-hosted model requires you to provision and maintain at least one server for Coolify itself and separate servers for your applications and databases. The project also offers a paid cloud-hosted version for those who prefer not to self-host, which includes high availability and managed infrastructure at comparable cost to self-hosting.

The project maintains a substantial user base, with almost all open issues coming from outside adopters reporting real-world problems rather than from the core team. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on bug triage and feedback collection, indicating active engagement with reported problems and user needs.