Cachet

A SaaS company operating public APIs faces steep subscription bills once commercial status page tiers scale with subscriber counts and team seats. Cachet eliminates that recurring overhead as an open-source status page platform deployed on standard Linux servers or containers. By giving teams complete control over outage reporting without metered subscriber pricing, it keeps incident communication predictable and budget-neutral.

Why Cachet instead of Statuspage

Atlassian Statuspage bills teams based on subscriber tiers, member seats, and notification channels. For growing teams, expanding email subscriber lists pushes pricing into tiers costing hundreds of dollars monthly, with SMS add-ons compounding the bill. Cachet eliminates that pricing curve. Running on self-managed infrastructure, it carries no licensing fees whether ten or ten thousand stakeholders follow an incident, requiring only a modest server paired with a transactional email relay.

The operational trade-off is infrastructure ownership. Atlassian Statuspage runs off-network, ensuring status updates remain reachable during total data center failures. Deploying Cachet requires DevOps engineers to isolate the instance on a separate cloud provider or independent region so production outages do not take down the status portal. Teams also trade turnkey third-party monitoring plugins for Cachet JSON REST API, scripting their own triggers to update component health.

What it does well

• Component hierarchy: Operators can group services into logical tiers with clear health states, including operational, degraded performance, partial outage, and major outage.
• Incident lifecycle tracking: Engineers can publish incident announcements across four explicit stages—investigating, identified, watching, and fixed—formatted with Markdown.
• JSON REST API: DevOps teams can script status updates and metric submissions directly from CI/CD runners, synthetic probes, or monitoring daemons.
• Integrated metric charts: Status pages can plot real-time latency, error counts, or query response times on public or private graphs without a separate visualization stack.
• Unmetered subscriber alerts: Visitors can subscribe to incidents via email, keeping stakeholders informed without triggering per-recipient SaaS fees.
• Two-factor authentication: Administrative dashboard access supports time-based one-time passwords, preventing credential hijacking during active incident response.