Our take
Activeregular commits- Activity
- 38
- Community
- 73
- Issues
- 47
- Pull requests
- 65
+8 stars in the last 30 days
- More contributors than 78% of the projects we track
- Slower to close issues than 96% of the projects we track
Cachet is an actively developed self-hosted status page option, but the old latest release and slow issue closure make it important to assess the 3.x branch and support expectations before adopting it.
Good fit if
- You want to operate your own status page and can support a PHP application and database.
- You are comfortable evaluating a project with regular commits but no release in over a year.
- You want to try the v3 demo and review the 3.x documentation before deploying.
Look elsewhere if
- You require a recent tagged release as a condition of production adoption.
- You need issues to be resolved quickly, given the long median time to close issues.
- You need clearly established license terms immediately. The GitHub data supplied here does not assert a license, so verify the repository’s current terms before use.
All health signals
| Last commit | 2026-10-05 (8 days ago) |
|---|---|
| Commits, last 90 days | 29 |
| Releases, last 12 months | 0 (latest v2.4.1, 2023-11-07) |
| Contributors | 100+ (top contributor: 64% of commits) |
| Issues closed, last 90 days | 27 (typically closed in 504 days) |
| Pull requests merged, last 90 days | 11 (typically merged in 0 days) |
| Project age | 11 years |
Checked on 2026-10-14 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
15,265Forks
1,630Change since Nov 13, 2026: +1 stars·+1 forks
Overview
Cachet is a self-hosted status page system for teams that need a public place to report service status. Rather than relying on a hosted status-page provider, you can run the application alongside your own infrastructure and manage the status page yourself.
The repository’s default branch is 3.x, a rebuild of the project. Cachet is actively receiving commits, but its latest release is from 2023, so teams should distinguish ongoing development from the availability of a recent stable release.
Key Features
- Run a status page on infrastructure you manage.
- Communicate service availability through a dedicated status page.
- Use a PHP application built for self-hosted status reporting.
- Choose MariaDB, MySQL, PostgreSQL, or SQLite as the database.
- Try the v3 dashboard demo before installing the application.
- Consult the Cachet 3.x installation and project documentation.
Use Cases
- A small software team can publish service status without relying on an external status-page vendor.
- An operations team can give customers a dedicated place to check reported service availability during an outage.
- An organization with self-hosting requirements can operate its status page on its own infrastructure.
- A team evaluating the 3.x rebuild can explore the demo before deciding whether its current development state fits a production rollout.
What you need
Detected in the repository
- PHP (from composer.json)
- A test suite and automated checks on GitHub Actions
Getting Started
Cachet requires PHP 8.3 or later, Composer, and a supported database. Follow the Cachet 3.x installation guide for setup steps; see the project documentation for further details.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Alternatives
- Checkmate: Checkmate focuses on monitoring uptime, response times, and server health, while Cachet centers on publishing service status and incident updates.
- tianji: Tianji combines uptime monitoring and server reporting with website analytics, while Cachet is dedicated to status pages and incident communication.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| cachet | PHP | – | 15.3k | Active |
| Checkmate | TypeScript | AGPL-3.0 | 10.9k | Active |
| tianji | TypeScript | Apache-2.0 | 3.1k | Active |
Considerations
The repository is active and has contributions from many people, with no indication that development is concentrated in one contributor. However, its latest release is old despite recent commits, and issues have taken a long time to close on average. Plan to assess the current 3.x branch and your own support needs rather than assuming the latest code corresponds to a recent release. The application also requires PHP 8.3 or later and a supported database. The provided GitHub license field is NOASSERTION, so confirm the applicable license before adopting or redistributing it.
Found this useful?
Share it with someone who would like cachet.