Cachet is the original open-source status page. It is a clean, PHP-based, self-hosted tool you run on your own server, and for a long time it was the default answer when a team wanted a status page without paying Statuspage.io. Component management, incident timelines, scheduled maintenance, email subscribers, and a REST API — Cachet has the shape of a proper status page, and it is free under a BSD licence.
What pushes teams to search for a Cachet alternative in 2026 is the gap between "free and self-hosted" and "actually reliable." Cachet does not monitor anything — it is purely the public-facing page, so you wire it to a separate uptime tool and hope the connection holds. Development has slowed significantly; the current stable release is dated, and the v3.0 rewrite is still in progress. And the deepest problem is the monitoring paradox: a self-hosted status page runs on infrastructure that can fail alongside the very outage it is supposed to report. When your server goes down, your status page goes down with it, and your customers see a blank page instead of an incident update.
That is the core argument for moving to a hosted status page: the page has to stay up when your product does not. This guide covers what to look for, how Cachet compares to hosted alternatives, and how to switch.
This is not a hit piece on Cachet. It is a fine tool for a team with ops capability that wants full control at zero licence cost. The question is when self-hosting the status page itself stops being worth the operational risk.
Why Teams Look for a Cachet Alternative
No built-in monitoring
Cachet displays incidents; it does not detect them. You need a separate uptime monitor to generate the incident, then push it to Cachet via the API. That is two products, two bills (or one bill and one self-hosted tool), and a wire between them that can itself fail. Hosted alternatives bundle monitoring and the status page in one tool — one incident lifecycle, from detection to customer notice.
The monitoring paradox
This is the structural problem with self-hosting a status page. Cachet runs on your server. When your server or hosting provider has an incident, Cachet goes down with it, and your customers cannot reach the page that is supposed to tell them about the outage. A hosted status page runs on independent infrastructure, so it stays up when your product does not — which is the entire point of a status page.
Development has slowed
Cachet's current stable release is dated, and the v3.0 rewrite is in active development but not yet feature-complete compared with the predecessor. A status page is a long-lived piece of infrastructure; a team adopting one wants to know the project is maintained. Hosted alternatives have a vendor responsible for uptime and updates.
PHP and the hosting burden
Cachet is PHP-based (Laravel), which some teams want to avoid, and it requires a database, web server, and TLS setup you operate yourself. Patching the underlying PHP and its dependencies is on you. A hosted status page removes that surface area entirely.
Subscriber management is basic
Cachet supports email subscriber notifications via SMTP, but end-user subscription management is basic compared with dedicated tools. Hosted alternatives offer email, SMS, Slack, and webhook subscriptions, often with unlimited subscribers and no per-subscriber fee.
You are responsible for the page's uptime
Hosting your own status page means you need it to survive the same outages it reports on. That is a contradiction. A hosted page on independent infrastructure removes the contradiction by design.
None of this makes Cachet a bad tool. It is still the right pick for a team with ops capability that wants full control, custom code, and zero licence cost. A Cachet alternative is for teams that want the page to stay up when their product does not, without operating a PHP application.
What to Look For in a Cachet Alternative
1. Hosted on independent infrastructure
The whole point of switching is to escape the monitoring paradox. Verify the alternative runs on infrastructure separate from yours, so the page stays up when your product does not.
2. Monitoring included
- Does the tool check your uptime itself, or only display incidents?
- Can it auto-create and auto-resolve incidents from real checks?
- How many regions does it check from?
Collapsing "monitor + status page" into one product is the biggest reason to switch. If the alternative still needs a separate monitor, you have not saved much.
3. Subscriber experience
- Can customers subscribe by email, SMS, Slack, webhooks?
- Are subscribers capped, or unlimited?
- Is the page brandable with a custom domain?
4. Incident management
- Is on-call scheduling and escalation included?
- Can you write and schedule incident updates?
- Is there a post-incident review surface?
5. API and automation
- Can you push incidents via API or webhooks (the way you do with Cachet)?
- Can you manage components programmatically?
- Does it integrate with your existing alerting (Slack, Teams, PagerDuty)?
6. Total cost
- Flat rate, per-subscriber, or per-responder?
- Are subscribers capped, or unlimited?
- Cachet is free to licence but costs ops time and hosting — compare the real total cost, not the sticker.
Cachet vs Hosted Status Page Alternatives
| Dimension | Cachet | Hosted status page |
|---|---|---|
| Built-in monitoring | No (separate tool needed) | Yes, included |
| Hosting | Self-hosted (your server) | Hosted on independent infrastructure |
| Survives your outages | No (monitoring paradox) | Yes |
| Development | Slowed; v3.0 in progress | Vendor-maintained |
| Stack | PHP + database + web server | Managed by vendor |
| Subscriber channels | Email (SMTP) | Email, SMS, Slack, webhooks |
| Subscriber caps | Self-managed | Often unlimited |
| On-call / escalation | None (separate pager) | Often included |
| Incident automation | Manual or via API | Auto from real checks |
| Cost | Free licence + ops + hosting | Flat or per-monitor, often with free tier |
| Best for | Teams with ops capability wanting full control | Teams wanting the page up when their product is not |
The trade-off is clear: Cachet gives you full control and zero licence cost, at the price of operating a PHP app and the monitoring paradox. A hosted alternative gives you a page that stays up during your outages, monitoring included, and no ops surface, at the price of a recurring fee.
How Webalert Compares as a Cachet Alternative
Webalert bundles uptime monitoring and status pages in one hosted product, which is the core gap Cachet leaves.
- Hosted on independent infrastructure — the status page runs on Webalert's infrastructure, not yours, so it stays up when your product does not. The monitoring paradox is removed by design.
- Monitoring included — Webalert checks your endpoints from multiple regions; the status page reflects real checks, not manual updates. No separate monitor to buy and wire.
- Auto incident workflow — incidents can be created and resolved from real downtime, so the page updates itself and your customers find out fast — the thing Cachet needs a separate tool and an API integration to do.
- Status pages with subscribers — a public, brandable status page with custom domain and subscriber notifications (email, Slack, webhooks). Customers subscribe and get notified without you typing updates by hand.
- Incident management — on-call, escalation, and post-incident review in the same product, instead of a separate paging tool.
- Smart alerting — downtime confirmed from multiple regions before an incident opens, keeping false alarms off your status page and out of your customers' inboxes.
- SSL, DNS, and domain monitoring — the upstream causes of outages monitored alongside uptime, so you can prevent incidents before they reach the page.
- Free tier — start with a hosted status page without a PHP server, a database, or a TLS setup.
The honest framing: if you want full source-level control and have the ops capability to run a PHP application and keep it patched, Cachet is a legitimate choice. For teams that want the status page to stay up when their product does not, with monitoring included and no ops surface, the hosted model wins.
How to Migrate From Cachet
1. Export your components and subscribers
Cachet stores components, incidents, and subscribers in its database. Export the component list and subscriber list — these become the seed for your new page. Note which components map to which monitors, since a hosted tool ties components to real checks.
2. Recreate the page and components
Create the new status page, add your components, set up the custom domain, and apply your branding. Most of the layout work is one-time and quick.
3. Attach real monitors
This is the step that does not exist on Cachet: connect each component to an uptime monitor. Now the page reflects reality instead of waiting for a human or an API push to update it.
4. Import subscribers
Import your subscriber list so customers keep getting notifications without re-subscribing. Set up notification channels (email, Slack, webhooks) to match what you offered before — and add SMS if you want to upgrade from Cachet's email-only subscriptions.
5. Run in parallel, then redirect
Run both pages in parallel for a short window. Once you are confident the new page updates correctly from real checks, point your status subdomain at the new page and decommission Cachet. Communicate the change to subscribers so they know where to look.
6. Decommission the Cachet server
Once the cutover is complete, shut down the Cachet instance and its database. You no longer patch PHP, renew the server, or worry about the page going down with your product.
Frequently Asked Questions
Is Cachet still worth using in 2026?
Yes, if you have ops capability, want full source-level control, and accept the monitoring paradox — your self-hosted status page can go down with the very outage it reports on. For teams that want the page to stay up when their product does not, a hosted alternative is usually a better fit.
What is the best Cachet alternative?
It depends on your priorities. If you want monitoring included with the status page, on independent infrastructure, look for a tool that bundles both natively. Webalert is one option; the comparison table above covers what to evaluate.
What is the monitoring paradox?
A self-hosted status page runs on your infrastructure. When your server or hosting provider has an incident, the status page goes down with it, so customers cannot reach the page that is supposed to tell them about the outage. A hosted status page on independent infrastructure removes the contradiction.
Does a Cachet alternative include monitoring?
A good one does. The whole point of switching is to collapse "monitor + status page" into one product and to escape the monitoring paradox. Verify the alternative checks your uptime itself and can auto-create incidents from real downtime.
Can I keep my subscribers when I switch from Cachet?
Yes. Export your subscriber list from Cachet's database and import it into the new tool. Customers keep receiving notifications without re-subscribing, and you redirect your status subdomain so the URL does not change.
Stop Self-Hosting the Page That Reports Your Outages
If your status page runs on the same infrastructure as your product, the simplest reliability improvement available is to host the page somewhere else — a tool that checks your endpoints and updates your customers from independent infrastructure.
Start monitoring with a hosted status page — free. No PHP server, no database to operate, no monitoring paradox. Webalert checks your site from multiple regions and updates your status page from real downtime, so the page stays up when your product does not — and your customers hear about incidents from you, not from a blank screen.