Your site returns 200. Your client says it is broken.
UptimeEZ watches the sites you look after and tells you what to fix, not just that something broke. It reads what a status code cannot describe: a stylesheet that failed, a database error printed inside a valid page, a certificate about to lapse.
Same engine either way. The hosted plan saves you the server, not features.
Open the live demo (resets every hour, sends nothing, saves nothing)
Each label above links to the file where its number is counted. The engine is public and MIT: if a figure here and the code ever disagree, the code is right and this page is wrong.
UptimeEZ watches the client sites of Coeur du Web, the agency that wrote it. Every check on this page exists because we got caught out once: the stylesheet that vanished after a cache purge, the database error a client found before we did, the noindex that shipped on a Friday. Who we are, and what we refuse to claim.
The same outage, twice
Only one of these two alerts lets you fix it
What an uptime checker sends
HTTP 200 · 412 ms · UP
Nothing is sent, because nothing looks wrong. The site has been unreadable for nineteen minutes.
What UptimeEZ sends
The page layout is broken
The page answers, but the resources that style it cannot be used: visitors see a bare, empty or broken page.
TO DO One stylesheet returns 404: /wp-content/cache/min/1/absent.css. Your minify cache is serving a file that no longer exists.
Same interval, same server, same 200 OK. The difference is what gets read in the answer.
Against the category
Where every monitor stops, and where this one keeps going
Where the others are better: longer track records, more notification channels, and points of presence on several continents. If you need to know that your site is unreachable from Sydney specifically, they do that and we do not.
The seven best known tools, named, and where each one beats us
The longer version: what separates website monitoring tools, and how to test one
Which one
Same engine. The difference is who runs it
| Criterion | Self-hosted, free | Hosted by us |
|---|---|---|
| Detection features | All of them | All of them, identical |
| Where the data lives | Your server, your database | France, one database per customer |
| You take care of | Install, the scheduled task, PHP upgrades, backups, and mail delivery so alerts actually arrive | Nothing |
| Blind spot to know about | A monitor on the same server as the sites it watches goes down with them | Runs outside your hosting |
| Price | Free, MIT, forever | 9.90 EUR a month |
If you have a server and half an hour, self-host it: that path is not a trial and nothing is held back. The hosted plan exists because a monitor running on the machine it monitors has a hole in it, and because the scheduled task, the mail delivery and the upgrades are work you would rather bill elsewhere.
Pricing
One plan, plus a free one you install yourself
No per-monitor pricing, and no tier that unlocks the checks that actually matter. Cancel from your account in one click, and your history stays exportable.
The launch price below is locked for as long as you keep the plan. It will not go up on you later, whatever it becomes for new sign-ups.
The hosted plan is for businesses only: agencies, freelances and companies acting for their own activity. If you are an individual, install the engine on your own server instead. It is free, it is the same code, and nothing is held back.
UptimeEZ
- Unlimited monitors, on unlimited sites
- Catches what a 200 OK hides: broken layout, dead database, forgotten noindex
- Tells you what to fix, with the evidence and a one-click repair
- Certificate, domain and published-vulnerability deadlines
- Dead-man heartbeats for your cron jobs and backups
- One read-only link per client, no account needed
- Your own instance, your own database, deleted on request
Or run it yourself, free forever
The same engine, MIT licensed, with every check on this page. PHP 8.2 and a database, no Composer and no Docker. You handle the install, the scheduled task and the mail delivery.
Get it on GitHubTax, billing, cancelling and what you take with you, on the pricing page.
Questions worth asking
Is the free version limited?
No. The self-hosted engine is the same code, under the MIT licence, with every check the hosted plan runs. There is no paid tier of the engine, no feature flag and no telemetry. What the hosted plan buys is a server that is not yours to maintain.
How is this different from an uptime checker?
An uptime checker tells you the server answered. UptimeEZ reads the answer: nine layout signals, forty-one database and application error signatures, a proof string you choose, and a silhouette of the page. When something is wrong it names one of twenty-five causes and tells you what to check first.
Will it slow down the sites it watches?
The availability check costs one page request per pass. The heavier layers are deliberately rationed: resources at most every 15 minutes, one HEAD request for the top-of-page image, certificates and domain expiry once a day and cached. The dead-man heartbeat costs nothing, because your script does the calling.
Can I move my monitors from another tool?
Yes. Drop in the export from UptimeRobot, Uptime Kuma, Better Stack, Pingdom or Site24x7, or any CSV with a column of addresses: UptimeEZ recognises the format by its content rather than the file name, shows what it will create, and tells you what it cannot take over. Past uptime percentages are not imported, because displaying another tool measurement as ours would be a lie.
What happens to my data if I stop paying?
Checks and alerts stop, your history is kept, and it resumes where it left off if you come back. Nothing is deleted on a failed payment: a billing problem should not cost you the one thing that cannot be rebuilt afterwards.
Who is behind it?
Coeur du Web, a French web agency. We built UptimeEZ for the client sites we look after, and released the engine because a monitoring tool whose source you cannot read is asking for a lot of trust.
Find out before your client does
Install it on your own server this afternoon, or let us run it and start watching your first site in a couple of minutes.