
How we run Navy on Navy
We monitor our own checks, alerts and status pages with Navy. Here is what that setup looks like and what it has taught us.

Co-founder and CTO
Marco Bianchi co-founded Navy and leads its engineering team. He designed the check network that runs monitors every 30 seconds from 18 regions, and the confirmation model that waits for 3 regions to agree before anyone gets alerted.
About
He spends most of his time on the core scheduler, the alerting pipeline and the systems that keep Navy itself available. Marco cares about boring, predictable infrastructure: clear failure modes, good defaults and nothing that needs a human awake at 3 a.m. unless it really does.
Before Navy, he worked on distributed systems and observability tooling for over a decade, and he still reviews most changes to the check engine himself.
Writing

We monitor our own checks, alerts and status pages with Navy. Here is what that setup looks like and what it has taught us.

Cron jobs fail without making a sound. Heartbeat monitors tell you when a job did not run, ran late or never finished.