Our startup was losing users silently for 6 hours - no alert fired. Here's what we built
Most monitoring tools tell you when your server goes down.
Nobody tells you when:
- Signups stopped at 2am - server was fine
- Payment initiated but never completed
- Cron job ran but processed zero records
- Stripe webhooks queued and silently stopped retrying
- AI agent looped for 3 hours burning API credits
- AI agent got stuck waiting on a tool call - never failed, never finished
- One of your 5 clients' data pipelines went quiet while the others ran fine
- Server 2 stopped processing while Server 1 looked healthy
We hit several of these on our own product. None triggered a single alert.
So we built NotiLens: it learns your normal baseline and alerts you when things go abnormally quiet. No manual thresholds. No dashboard to stare at.
Built for solo founders, small teams, and anyone running multiple AI agents or serving multiple clients across separate systems.
Offering 3 months free to the first 10 early users in exchange for honest feedback. 2 spots already taken.
Trending on Indie Hackers
This is the part of monitoring most people don’t realize until production:
The hardest outages are often the ones where nothing technically “breaks.”
200 OK responses.
Healthy CPU.
Healthy memory.
Healthy uptime.
Meanwhile:
From the outside, the system looks healthy.
But the business isn’t.
I ran into similar problems while building Sentinel. It completely changed how I think about “uptime monitoring.”
The real challenge isn’t detecting failure.
It’s detecting loss of function before users notice.
Exactly. "Loss of function" is the right framing and it's completely invisible to infrastructure monitoring. What's your approach to detecting it?
What stands out in this story is how often these “silent failures” happen without any signal until it’s already too late — users don’t complain, they just drift away, and dashboards only tell you after the damage is done. We’ve seen the same pattern in SaaS where everything looks fine on the surface but one weak point in onboarding or messaging quietly bleeds retention because users never fully lock in the value, they just lose confidence and stop showing up, and by the time you notice it, it feels sudden but it actually wasn’t.
Yes, by the time you notice, you've already lost 10 users who never said a word. Silent churn starts way before the dashboard shows anything.
Most monitoring tools catch failure.
The more expensive problem is quiet drift.
That’s the layer most teams miss:
nothing breaks
nothing crashes
revenue just quietly stops moving
That’s much closer to operational blindness than observability.
And that distinction matters, because “monitoring” sounds crowded fast.
The stronger positioning here is not uptime.
It is catching silent business failure before it compounds.
NotiLens is clear enough, but it still feels slightly feature-shaped for what this becomes.
If this leans harder into operational anomaly / silent failure infrastructure, something like Davoq.com would likely carry more weight as the product matures.
Really appreciate this. "Operational blindness vs observability" is a sharper distinction - going to think about how to surface that more clearly on the site. On the name, NotiLens is staying - but the framing you're describing is closer to where the product is heading than "alerting" is.
That makes sense.
If NotiLens is staying, then the main thing is making sure the site does not collapse back into “alerting.”
Because alerting sounds like:
something happened, notify me
But what you’re describing is bigger:
something is drifting before the business notices
That’s a stronger and more expensive problem.
I’d make “operational blindness” the enemy, not downtime.
That gives NotiLens a much sharper job to own.
Good framing. Already updated the headline today - "Catch Silent Business Failures Before Your Users Do." Still evolving.