PingPilot started in 2022, in a tiny apartment in Lisbon, after our founder shipped a side project that quietly went down for nine hours on a Saturday. The existing monitoring tools either cost more than the side project earned, or alerted on every transient hiccup until the alerts became noise.
So we built the one we wanted: cheap enough to wire into a hobby project, smart enough to trust at 3 a.m., and simple enough to set up in under five minutes.
Today we're a fully remote team of seven across four time zones. We're profitable, bootstrapped, and have zero plans to take VC money or "pivot to AI." We just want to keep building the best uptime monitor in the world for people who write code for a living.
If that sounds boring — good. Boring is exactly what you want from infrastructure.
These aren't on the wall. They're in every decision we make — from pricing to product roadmap to the on-call rota for our own infrastructure.
An alert that fires when nothing's wrong is worse than no alert at all. We verify from multiple regions before bothering you.
No "contact sales." No bait-and-switch when you hit a check limit. The price you see is what you'll pay, forever, on that plan.
We don't add features for the sake of a launch. We add them when enough customers actually need them and they fit our soul.
Our own dashboard is monitored by PingPilot. If we go down, we get paged the same way you do. Same dog food, same bowl.
Spread across Lisbon, Berlin, Bangalore, and Mexico City. We hire engineers who've shipped real things and writers who've actually used an oncall pager.
Wrote the first version of PingPilot in a single weekend. Previously SRE at a payments company you've used. Lisbon.
Builds our check infrastructure. Believes the only real test is the production one. Berlin.
Owns the dashboard and the public API. Will out-debate you about REST vs RPC. Bangalore.