Auguro
That is not the same as working. Auguro loads your site in a real browser and tells you when it stops working for a human.
A real browser, right now, with no account. Takes about five seconds.
This is a real failure. A JavaScript error kills the render, the server still serves the page perfectly, and every uptime monitor stays green for as long as it lasts. Put your own address in above and see what we see.
Real Chromium, not a HEAD request. Auguro waits for the page to load, then asks whether anything rendered, whether your own scripts survived, and whether your own assets arrived. No uptime monitor asks any of that.
“Page rendered nothing.” “Asset failed to load: /assets/app.js.” “The HTTPS certificate was rejected.” Not a status code and a shrug.
A third-party ad script throwing does not fail your check. Nor does a lazy image, a missing favicon, or a telemetry beacon returning 400. Those are warnings. A monitor you stop trusting is a monitor you turn off.
Failures are confirmed before anyone is told, an outage becomes exactly one incident, and acknowledging it stops the reminders without pretending it is fixed. Webhook, Pushover, Telegram, email.
A maintenance window is an object you attach checks to. The checks keep running so the history stays honest; only the alerting stops.
Every organisation lives in storage pinned to the EU, screenshots included, decided at creation rather than promised in a policy.
You get both on every plan. One confirms the server answered. The other confirms your customers can actually use the site.
Status code, response time, and text that must or must not appear, as often as every minute on every plan including free. This is what conventional uptime monitoring gives you, and Auguro gives you it too.
Real Chromium opens your page. Did it render, did your scripts survive, did your assets load, is that button still there. It sees the outage a status code cannot: the blank page that still returns 200.
You pay for how many sites you watch and how closely. Nothing else — your whole team is included on every plan, free ones too.
HTTP checks run as often as every minute on every plan, including free.
Honestly, including where the other tool is the better answer.
React, Vue, Svelte, Astro, a headless shop front — anything that builds the page in the browser can fail after a perfectly healthy response. One bad deploy, one third-party script, one expired API key, and the server keeps answering 200 to an empty page. Uptime monitoring cannot see it. This is the case Auguro exists for.
Agencies and freelancers find out a client's site is broken when the client rings. Point a check at each one, put the whole team on the alerts at no extra cost, and hear about it first. Maintenance windows keep planned releases from waking anybody.
Yes. Paste any address into the box on the auguro.dev home page and it runs a real browser check there and then, showing you the verdict, what it found, and a screenshot of what our browser saw. No account and no card. Signing up is what turns that one-off look into something that keeps watching and tells you when it changes.
That the page rendered. Auguro loads your site in real Chromium and checks that there is content on the page, that your own scripts did not throw, that your own stylesheets and scripts loaded, and that whatever you told it to look for is still there. A server can answer 200 with a completely blank page, and that is invisible to a monitor that only reads the response code.
No. You paste a URL. If you want to be stricter you can add text that must appear, text that must not appear, a CSS selector that has to exist, and a response time ceiling, but none of it is required and none of it is code.
By only failing a check on things that are the site’s own fault. A third-party advertising script throwing an error does not fail the check. A lazy-loaded image below the fold is not a broken image. A missing favicon or a telemetry beacon returning 400 is a warning, not an outage. Anything ambiguous warns and never pages you.
Whatever you set. Every check has a threshold for how many consecutive failures count as an outage and how many consecutive successes count as recovered, so a single blip never wakes anyone.
In the EU. Every organisation’s data lives in a Durable Object pinned to the EU jurisdiction, and screenshots and saved page source go to an EU bucket in the same place. That is decided at creation and cannot be quietly changed later.
No, and we will not. Billing is the number of sites and how often we look at them, nothing else. Charging per teammate punishes you for adding the person who would actually answer the alert.
Webhooks, Pushover, Telegram and email. One incident groups every notification about one outage, so a flapping check cannot send you fifty messages, and acknowledging an incident stops the reminders without pretending it is fixed.
Yes. A maintenance window is an object with checks attached, so you put the whole release in one window. The checks keep running and the history stays honest; only the alerting stops.