This guide is for teams running or considering Cachet who want to trade self-hosting control for a managed status page connected to real monitors. It is not a claim that Cachet is broadly inferior. The useful question is whether its strongest capabilities match the work your team actually needs.
As of August 10, 2026, Cachet is a free, open-source, self-hosted status-page application. The official documentation says the 3.x line is under active development and not all features are complete; the repository’s published release history should be checked before production rollout. Prices and packaging can change, so use the linked official sources for a final quote.
Short answer
Keep Cachet when source control and self-hosting are requirements. Choose a managed alternative when the status page must stay available independently and the team does not want to operate another production application.
Where Cachet is still the better fit
- Full control of hosting, database, appearance, and application changes
- No vendor subscription fee for the software
- API-driven status communication and an open project with an active 3.x branch
Why teams consider an alternative
- Cachet is a status page, not an independent monitoring network; another system must detect failures and update it
- Your team owns hosting, backups, upgrades, security, email delivery, and availability of the page itself
- Moving to hosted software can reduce control and may not support custom changes made to a Cachet installation
Comparison criteria that matter for Cachet users
- Self-hosting and data-control requirements.
- Monitor-to-component automation.
- Subscriber delivery and compliance.
- Upgrade, backup, and disaster-recovery ownership.
Where Webalert fits—and where it does not
Against Cachet, Webalert’s relevant scope is managed HTTP/HTTPS, TCP, DNS, ping, and heartbeat monitoring with multi-region confirmation, SSL alerts, status pages, and incident alerting. Check current pricing and features for plan boundaries.
Webalert is a possible fit when the migration scope is straightforward public availability and customer communication. It is not a promise of parity with every Cachet capability. In particular, respect the limitations above and keep specialist tooling where it remains useful.
Migration advice
Inventory components, groups, incidents, metrics, subscribers, API integrations, branding, and custom code. Build the hosted page on a temporary domain, connect components to live monitors, import only data the destination supports, then lower DNS TTL and switch the custom domain after testing subscriptions.
Decision
Keep Cachet when source control and self-hosting are requirements. Choose a managed alternative when the status page must stay available independently and the team does not want to operate another production application. Avoid an all-at-once cutover: move the checks that clearly fit, preserve specialist coverage, and let parallel evidence decide the rest.
Status-page software vs a monitored page
Cachet is a status application you operate. It does not, by itself, detect that checkout is down.
| Responsibility | Cachet | Hosted status + monitors |
|---|---|---|
| Render incidents / components | Yes | Yes |
| You patch PHP / composer / DB | Yes | No |
| Probe the production URL | Separate (or a plugin) | The same product |
| Subscriber mail deliverability | Your SMTP | Vendor |
| Custom domain | Your nginx | Supported |
| License cost | Free software | SaaS plan |
If Cachet is down, customers see nothing — the worst failure mode for a status page.
Frequently asked questions
Is Cachet abandoned?
Treat it as a self-hosted codebase with community forks and maintenance cost. The alternative decision is operational, not “Cachet vs Webalert features on a spreadsheet.”
Can I keep Cachet and add monitors?
Yes. Point Cachet at metrics you already trust, or replace the public URL with a hosted page and keep Cachet internally.