WHAT IS IT?
Cachet is a self-hosted status page: the public page telling your customers the service is degraded, what broke and when it will be fixed. It monitors nothing itself - it communicates. You declare your components, open an incident, post updates, and subscribers get notified.
WHY IS IT INTERESTING?
- It does one thing: unlike monitoring suites that bolt a status page onto the end of the pipeline, Cachet only does this. It deploys outside your infrastructure, on a different host and database, so it stays up when everything else is down.
- Structured incident model: grouped components, per-component statuses, incidents linked to the components they affect, and a timeline of updates. Incident templates spare you rewriting the same message every outage.
- Scheduled maintenance: maintenance windows are announced ahead of time and attached to the relevant components, without polluting the history of real outages.
- Subscribers and webhooks: per-component subscriber notifications, plus outbound webhooks with delivery attempt tracking to wire up Slack, a queue or your internal tooling.
- API-first: Sanctum tokens, Laravel-style filtering and sorting. Your alerting system opens and closes incidents on its own, with no human clicking.
- Displayable metrics: push your own metric points and Cachet renders them as charts on the public page - latency, throughput, whatever you want to expose.
USE CASES
- Public status page for a SaaS, fed automatically from Prometheus or a homegrown probe.
- Internal incident communication for an IT department, with subscriptions per business service.
- Announcing maintenance windows to customers under SLA, with a timestamped written trail.
- Hosting provider exposing per-region status and letting customers subscribe to what concerns them.
GOOD TO KNOW
Two things to weigh before adopting. First the license: the project presents itself as open source, but LICENSE.md is a custom Alt Three Services license, and the composer.json of both cachet and cachet/core declare proprietary. Commercial use, modification and self-hosting are allowed; redistributing it as a standalone product is not. Second, maturity: the 3.x branch is a full rewrite on Laravel 13 and Filament 5, still under active development with incomplete features. The repo moves, but don't expect v2-level stability.