Why we built it
Every SaaS product these days is a stack of other people's SaaS products. When Stripe goes down, your checkout goes down. When OpenAI has a capacity issue, your chatbot stops. When your CDN has a regional hiccup, half of Asia can't reach you.
Most teams find out the same way — a customer emails to say something's broken, you scramble to figure out whether it's you or one of the services you rely on, and by the time you've confirmed it's the vendor the incident has been running 20 minutes.
The existing tools in this space do the job but are priced for enterprise procurement. A two-person indie team building a side project shouldn't be paying $300/month to find out GitHub is degraded.
Pingoru is the same idea — check every vendor's public status page every 5 minutes, translate their wildly different formats into one common shape, alert you when something breaks — at a price that makes sense for indies and small teams.
How it works
We check each vendor's public status page every 5 minutes and translate what we find into one consistent shape — so a "partial outage" on AWS looks the same as a "partial outage" on Stripe, even though the two vendors describe them in completely different ways.
When something changes — a service flipping from working to degraded, a new incident posted, an incident resolved — we send the alert to wherever you've asked us to: email, webhook (Discord, Slack, PagerDuty), or both.
You pick which providers to watch, which specific services (AWS EC2 us-east-1 only, say), and which event types fire alerts. We respect your filters — no blanket spam.
Who runs this
Pingoru is built and operated by a small indie team in Canada 🇨🇦. No venture funding, no growth targets, no exit plans — just a tool we use ourselves and wanted to exist. We build it with love (and way too much coffee) because we were tired of finding out one of our vendors was down from a customer support ticket.
Every feature on the roadmap is prioritized because it'd make the thing more useful, not because it'd juice a metric for the next board meeting.
If any of this resonates — or if there's something missing — we'd genuinely like to hear from you. Drop us a line.