UpWatchr started as a personal itch: I wanted to know the moment one of my sites went down, without creating an account, picking a pricing tier, or handing a third party the URLs of things I hadn't launched yet. Every hosted monitor I tried solved the first problem and created three new ones. So I built the tool I actually wanted - a small native Windows app that checks from my own machine and tells me the moment something breaks.
This blog is where the notes that don't fit in a changelog will live. A few things to expect:
- Release notes with actual reasoning - not just a list of what changed, but why, and what it cost to get there.
- Local-first monitoring in practice - what a desktop probe can watch that a hosted one can't, and just as honestly, where a hosted monitor is still the right call.
- Small write-ups on the parts that are usually invisible - alert channels, the HTTP checker, the local status page, and now the MCP server that lets an AI assistant read your watchlist.
One thing this blog won't be: a funnel dressed up as content. UpWatchr is free, and it stays free. If a post here recommends a hosted monitor instead of UpWatchr for your situation, that's not an accident - it's the same honesty policy already running on the comparison pages.
If you're new here: UpWatchr is a free Windows app that watches the URLs you care about and alerts you - by popup, email, webhook, Telegram, or a local app of your own - the second something breaks. No account, no cloud, no subscription. Grab it and come back here for what's next.
