About
I love building tools for developers — the kind you set up once and then mostly forget about, because they only speak up when there is something worth saying.
I built Owl Keeper because the failures that actually cost me weekends were never the ones an uptime checker caught. A certificate lapsing on a Sunday. A domain nobody renewed. A staging robots.txt that shipped to production and quietly drained a client’s search traffic over a fortnight. Every one of those answers a perfectly healthy 200, and every one of them is somebody’s Monday morning.
So this watches all of it on one page, per site rather than per check, and it tries very hard not to wake you for something that does not matter. An alert you can afford to believe is worth more than an alert that arrives first.
Write in and a person reads it. No ticket deflection, no bot asking you to rephrase the question first.
No analytics, no tracking pixels, no third-party scripts on the pages you sign in to. There is nothing here to put in a data processing agreement.
Checks run from several regions and a majority has to agree before anything is called down, so one bad route does not become an outage.
If you are weighing this up for a client estate and want to know whether it does something in particular, ask before you sign up rather than after.