🚦 Cachet, the open-source, self-hosted status page system.
15.1k
Stars
1.6k
Forks
45
Open issues
30
Contributors
AI Analysis
Cachet is an open-source, self-hosted status page system built on Laravel and PHP, designed for organizations to communicate infrastructure and service status to users in real-time. It serves teams and enterprises that need to maintain transparent communication about system availability without relying on third-party SaaS providers. This tool is best suited for DevOps teams, system administrators, and organizations with strict data sovereignty or cost control requirements, not for users seeki...
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.
Cachet 3.x rebuild brings self-hosted status pages back to active development after years of stagnation
Cachet is a self-hosted, open-source status page system that lets teams publicly communicate service health, incidents, and scheduled maintenance without depending on paid SaaS providers. It targets DevOps teams, startups, and organizations with data-sovereignty requirements who want full control over their status page infrastructure. With 15,000+ stars and an active 3.x rebuild underway, it occupies a well-defined niche. The project nearly went dormant between 2020 and 2023 but has since resumed meaningful development under new sponsorship.
Founded in 2014, Cachet was one of the first prominent open-source status page tools and gained rapid adoption during 2015–2018. Development stalled significantly around 2020–2022, prompting community concern. A formal 3.x rebuild announcement restarted active development.
Initial growth was driven by the absence of affordable self-hosted alternatives to StatusPage.io. Stars accumulated heavily between 2015–2019. Growth has since plateaued at roughly single-digit stars per week, consistent with a mature project in a stable niche rather than an expanding one. The 3.x announcement likely provided a modest revival bump.
Cachet has been widely referenced in self-hosting and DevOps communities since 2015, and numerous blog posts and Docker Hub pulls from earlier versions confirm real-world deployment. However, specific production usage metrics for v3.x are not documented in the README or available metadata. Historical adoption for v2.x was well-documented; v3.x adoption is still accumulating.
Likely a Laravel-based PHP application given the PHP requirement, Composer dependency, and multi-database support (MySQL, MariaDB, PostgreSQL, SQLite). Appears to follow a standard MVC web application pattern with a separate dashboard and public-facing status page. The 3.x rebuild suggests significant architectural changes from the 2.x codebase.
Not documented in README
Last push was 2026-06-01, approximately 25 days before the evaluation date, indicating active maintenance. The 3.x rebuild discussion and live demo environment suggest sustained engineering effort. Sponsorship from identifiable companies (Jump24, CodeRabbit, de:doc) provides some resource signal. This is an actively maintained project, not stagnant, though contribution velocity is modest.
ADOPT IF: you need a self-hosted, full-featured status page with incident management, subscriber notifications, and PHP/Laravel infrastructure already in place, and are willing to run on the actively-developed v3.x branch. AVOID IF: you require a production-hardened, battle-tested deployment today — v3.x is still maturing and may introduce breaking changes; consider waiting for a stable release or using v2.x with caution. MONITOR IF: you are evaluating self-hosted status page options but want to see v3.x reach a stable tagged release before committing to it.
Independent dimensions
Mainstream potential
3/10
Technical importance
6/10
Adoption evidence
5/10
- The 3.x rebuild is still in progress; migration paths from 2.x may be incomplete or undocumented, creating upgrade friction for existing deployments.
- Project has a history of multi-year maintenance gaps; dependency on a small number of sponsors and maintainers creates single-point-of-failure risk for long-term sustainability.
- Star growth has plateaued at very low weekly rates (~9/week), suggesting limited organic discovery momentum in the current ecosystem.
- PHP as the implementation language may deter adoption among teams with Node.js, Go, or Python-centric infrastructure stacks.
- Competing tools with built-in uptime monitoring (Gatus, OpenStatus) may offer more value with less operational overhead for teams that need both monitoring and status communication.
Cachet v3.x will likely stabilize into a reliable, niche-but-respected self-hosted option for PHP-friendly teams. It is unlikely to reclaim category leadership but may sustain a loyal user base of several thousand active deployments.
Explore similar
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://cachethq.io
- Language
- PHP
- License
- NOASSERTION
- Last updated
- 2d ago
- Created
- 142mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Authenticated SSTI/RCE via Unsandboxed Template Rendering in Incident Templates
SQLite connection causes "database is locked" errors when hit with concurrent requests
Fix API documentation example for `create schedule`
Cachet v3.x Official Release Date
Cachet 3.x Fails to install on Ubuntu 24.04 as PHP 8.4 is not available
Top contributors
Similar repos
gordalina/cachetool
CacheTool is a CLI utility and PHP library for managing APCu, OPcache, and file...
JosephSilber/page-cache
Laravel Page Cache caches HTTP responses as static files on disk to serve pages...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
cachethq/cachet
this
|
15.1k | +13 | PHP | 7/10 | 2d ago |
|
gordalina/cachetool
|
1.8k | — | PHP | 7/10 | 5mo ago |
 caido/caido
|
2.5k | — | Shell | 7/10 | 1mo ago |
 cipi-sh/cipi
|
1.1k | — | Shell | 8/10 | 2d ago |
|
JosephSilber/page-cache
|
1.3k | — | PHP | 7/10 | 4mo ago |
 Cacti/cacti
|
1.8k | — | PHP | 7/10 | 2d ago |
OpenStatus is TypeScript-based and targets a more modern stack with built-in monitoring features. It offers a hosted SaaS option alongside self-hosting, and is growing faster in GitHub stars (8,783). Cachet is more mature and has a larger existing user base but a narrower PHP ecosystem fit.
The dominant commercial option. Statuspage requires no infrastructure management and has enterprise support, but costs scale significantly. Cachet's primary value proposition is avoiding this cost and retaining data control. For teams already managing PHP infrastructure, Cachet is a credible alternative.
Coolify is a broader self-hosting platform that includes status page functionality as a feature, not a dedicated product. Teams wanting a specialized, purpose-built status page tool would likely prefer Cachet's focused feature set.
Gatus is a Go-based monitoring and status page tool emphasizing uptime checking as the primary function. It appeals to infrastructure-first teams. Cachet focuses more on incident communication and manual or API-driven updates, serving a complementary but distinct use case.
Upptime uses GitHub Actions and GitHub Pages for zero-infrastructure status pages. It is simpler and free to operate but far less flexible for incident management. Cachet is better suited to teams needing rich incident workflows and subscriber notifications.
