Hey PH, Honest origin story: GeoPulse API started as an experiment — I wanted to see what it took to actually build and launch a product, not solve a personal pain point. But partway through, I got genuinely invested in it and decided to see it through properly rather than let it stay a side experiment. That shaped how I approached it: instead of a quick MVP, I focused on doing the fundamentals right — multi-region checks from the free tier (not gated behind a paid plan), a webhook system that's actually reliable (HMAC-signed payloads, automatic retries with backoff, not just a fire-and-forget request), and a full REST API with real docs. I also spent time writing honest comparisons against UptimeRobot, Nodown, and Better Stack — including where they're genuinely better than GeoPulse (SMS/voice alerts, full observability, built-in on-call scheduling). Didn't want to pretend those gaps don't exist just because I built the thing. Would love feedback, especially from anyone running infra across multiple regions — what's missing for your use case?

GeoPulse API

Multi-region API monitoring with a real webhook system

Multi-region API monitoring with a real webhook system