// guides
Short, specific, and honest about what each one will not catch. Written for someone running production without a monitoring team.
5 min · no prior setup
Signup to a verified alert on your own phone, using one URL and the free plan. The point is to prove the delivery path before you depend on it.
10 min · you have a Stripe account
Payment failures are the most expensive silent outage a small product can have. What to watch, what Stripe already tells you, and where the gap is.
8 min · you have a Supabase project
Supabase is several services behind one URL. Which parts fail independently, what its own dashboard tells you, and what to do about the rest.
10 min · you run Lambdas
What is worth alerting on for a Lambda, what is only worth collecting, and how to avoid maintaining alarms per function per metric.
7 min · conceptual
Most damaging outages never touch your status code. A field guide to the failure modes uptime monitoring structurally cannot see, and what does catch them.
9 min · you have an Atlas cluster
Atlas rarely goes down. It degrades — slowly, on one node, in ways your application reports as its own fault. What to watch, and what Atlas already tells you.
These are written from the questions people actually ask. If yours is not here, say so — it is a short list and it moves.