7 posts tagged with "stentorosaur"

Our 90-day status heatmap looked great in mockups. In production, it was 84% empty. Here's how we fixed it with daily summary aggregation.

Traditional status pages show infrastructure health: API up, Database up, Cache up. But users don't care about infrastructure—they care about whether they can complete their tasks.

This post explains how to model business processes in Stentorosaur so your status page reflects user-facing capabilities.

This post outlines planned automation features for Stentorosaur—specifically, using LLMs to draft incident summaries and statistical methods to detect degradation. These are design proposals, not shipped features.

This guide covers setting up a local development environment for Stentorosaur and the contribution workflow.

This guide walks through adding status monitoring to an existing Docusaurus site. By the end, you'll have a /status page showing system health, powered by GitHub Issues and Actions.

This post covers the technical decisions behind Stentorosaur—why we chose certain approaches, what we rejected, and the trade-offs you should understand before adopting it.

The Problem: Status Page Infrastructure Sprawl​

If you run a SaaS product or developer platform, you need a status page. The standard approach? Subscribe to Statuspage.io ($29-$99/month), spin up a separate domain, configure separate auth, and maintain another deployment pipeline—all to tell users when your actual service is down.