We build the monitoring we wanted when we were on call
Navy is a small, remote team of engineers and designers who have all held the pager. We make uptime monitoring, on-call and status pages for teams who want fewer, better alerts.
- Founded
- 2021
- People on the team
- 38
- Countries we work from
- 11
- Teams on Navy
- 4,000
Story
Why Navy exists
Navy started in 2021, after one of our founders spent a weekend answering pages for an outage that turned out to be a single flaky network route. Every tool we tried either missed real outages or cried wolf, and on-call engineers had learned to ignore both.
So we built the monitor we wanted: checks from many regions, an outage only when three of them agree, and alerts that go to one person instead of a whole channel. The status page came next, because customers deserve to hear about problems from you first.
Today Navy runs more than two billion checks a month for 4,000 teams, from two-person startups to companies with rotations in every time zone. The goal hasn't changed: when your phone buzzes at 3 a.m., it should be worth waking up for.
Milestones
Five years of fewer pages
2021
Navy launches with HTTP checks from six regions.
2022
Status pages arrive, with email subscribers.
2023
On-call schedules and escalation policies.
2024
The Terraform provider and the Navy CLI.
2026
18 regions and 4,000 teams on Navy.
Principles
How we work
01
Every alert is real
We would rather confirm an outage for ten more seconds than wake someone up for nothing.
02
Quiet by default
No dashboards to babysit. Navy stays out of the way until something actually breaks.
03
Honest status
Our own status page is public, including the incidents we would rather forget.
Team
The people on call for you
Meet the whole team
Co-founder and CEO
Maya Lombardi
She started the company with one goal: alerts that engineers can trust, and status pages that tell customers the truth.
Co-founder and CTO
Marco Bianchi
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.
Product Engineer
Carmen Vidal
She built the Terraform provider, the Navy CLI and the validation that catches config mistakes before they reach production.
Head of Design
Ingrid Solberg
She shaped the dashboard, the status page themes and the alert messages that land on phones at 3 a.m., where every word has to be clear on the first read.
Backend Engineer
Paula Herrera
She owns the confirmation rounds that re-run a failed check from other regions, and the logic that decides when a failure becomes an outage.
Site Reliability Engineer
Samuel Ortiz
He keeps the check network running across all 18 regions and makes sure Navy stays up when the services it monitors do not.
We are hiring
Remote roles in engineering, design and support. Everyone joins the on-call rotation, and everyone gets paid for it.