On-call should be designed before it becomes urgent.
oncall.fyi is a practical field guide and free toolkit for the people who design, manage, and carry on-call responsibility. We publish guides, calculators, templates, and migration resources for schedules, escalation, alert quality, compensation, handoffs, and incident response.
The project is created by the team behind MonoDuty. That relationship gives us direct experience with webhook alerting, uptime, heartbeat monitoring, and notification workflows, but it also creates a responsibility to be transparent. We identify MonoDuty references clearly, date vendor comparisons, and separate educational recommendations from product promotion.
Our goal is not to make on-call look heroic. It is to make ownership clearer, alerts more actionable, escalation safer, and the responder experience more sustainable.
What we publish
- Guides for the decisions behind schedules, escalation, alerting, handoffs and incident response.
- Free tools that run entirely in your browser and need no account.
- Templates you can copy, adapt and put in front of your team today.
- Migration resources with dated, sourced vendor facts.
Who it is for
Solo developers running a small production system; platform and SRE leads responsible for coverage across several teams; engineering managers accountable for fairness and sustainability; engineers about to take their first shift; and teams that have to move providers on somebody else’s deadline.
How we review content
We distinguish publication approval, technical verification and source freshness. Owner approval authorizes a page to be published; it does not certify that every procedure has been independently tested. Articles show their available review evidence and dated sources. The full policy is in our editorial policy.
Burak Y approves publication, with the MonoDuty Support Team handling corrections and reader reports. Assisted drafting and checks are identified without inventing a separate human reviewer.
Our relationship with MonoDuty
MonoDuty is built by the same team. We disclose that wherever product context matters. MonoDuty appears on this site only where its documented product scope fits the reader’s problem. Our comparisons cover schedules, incident ownership, notifications and plan limitations using current public sources. Fit judgments are separate from vendor facts. Educational outputs never require a MonoDuty purchase.
Corrections and contact
If something here is wrong, we want to fix it and say that we did. Material corrections are published with a date and a short change note. Write to [email protected].