We got tired of the blame game.
Netovair exists for one reason: to end the "is it the database or the network?" argument that eats the first hour of every serious outage.
Our founders spent years on opposite sides of that argument — one running database platforms, the other running networks — at companies where a slow checkout meant two teams staring at two dashboards, each one green, each one certain the problem lived somewhere else.
The tools were never the problem. The seam between them was. Database monitoring and network monitoring grew up as separate disciplines, with separate vendors, separate dashboards, and separate on-call rotations. The one view nobody had was the one that mattered: both layers, on the same timeline, correlated.
So we built it. Netovair collects from the query and the wire with a single agent, lines the two up against a shared clock, and tells you which layer moved first. The result isn't another dashboard to check — it's the end of the debate.
How we build.
Answers over dashboards
A dashboard makes you look. An answer tells you what to do. We ship the second kind — the correlation, the cause, the owner — not just another chart to interpret at 2 a.m.
Your data stays yours
Run Netovair in our cloud or entirely inside your own network. We never make you choose between good monitoring and keeping telemetry where it belongs.
Respect the on-call
Every alert we send has to earn its page. Grouped incidents, learned baselines, and real root cause mean fewer wakeups and more trust in the ones that come through.
From a shared frustration to a shipping product.
The idea
Two on-call veterans compare war stories and realize they've been debugging the same incident from opposite ends for a decade.
First correlation
The prototype links a replication-lag spike to a saturated uplink in under a second. The blame game loses its first round.
Design partners
A handful of teams put Netovair in front of production incidents and stop opening two dashboards to answer one question.
Open to everyone
Netovair launches with a free tier so any team can put both layers on one timeline before their next outage.
Built by the people who used to get paged.
Ada Roy
Spent a decade keeping replicas honest at scale. Now makes sure the query side of Netovair never lies.
Marco Keane
Former backbone engineer who has traced one too many "it's not the network" incidents that were, in fact, the network.
Sana Tellis
Turns messy incident timelines into a console the on-call can actually read at 2 a.m. Obsessed with the first thirty seconds of an alert.
Come end the blame game with us.
We're a small, remote-friendly team of people who've carried the pager and want to build the tool we always wished we had.