Help center
How Heedery works, and how to use it.
Short guides to every part of the app: adding monitors, getting alerts to the right person, running status pages and reports. New here? Start with Getting started.
/
01Start here
02Monitoring
- Monitors and check typesWhat each check type is for, how often it runs and when a site counts as down.
- Changes, expiry and slowdownsWarnings that come before an outage: DNS and certificate changes, page content, PageSpeed, expiry dates and slowdowns.
- Site healthSilent breakages uptime cannot see: noindex, missing analytics, WordPress vulnerabilities, leaked API keys and source maps.
- Deploy markersReport each release from CI so charts and incidents show what shipped just before.
- Maintenance windowsPlan work ahead: checks keep running, alerts stay quiet and status pages say why.
03Alerts and incidents
- Alerts and channelsEmail, phone push, SMS and calls, Slack, Microsoft Teams, Discord, Telegram and webhooks, and which site alerts where.
- Escalation and on-callPage people step by step until someone acknowledges, and take turns being on call.
- IncidentsHow an incident opens and closes, what the evidence shows and how your team works on it.
04Status pages and clients
05Team, API and app
- Team, roles and securityInvite people, choose what each one can do, read the audit log and turn on two-factor sign-in.
- API and MCPManage monitors, incidents and maintenance from your own tools, or from Claude and Cursor over MCP.
- Mobile appPush alerts you can acknowledge from the lock screen, a home screen widget and Live Activities.
The numbers behind the checks (timeouts, thresholds, how uptime is worked out) are on How we check. Can’t find something? Ask us.