About
A page should be rare, clear and worth waking for.
BlipLite exists so the right person hears about the right problem once, with the reason attached, and everyone else on the rotation gets to sleep.
Why a gateway?
APIs got gateways because traffic needed one place to be seen, secured and controlled. Alerts are traffic too, and they reach the people who are least able to absorb noise.
So BlipLite sits in front of your incident tools: one place to ingest, understand and decide, so the pager only rings when it should.
It doesn't replace PagerDuty or incident.io. They're good at schedules, escalation and running an incident. BlipLite decides what reaches them, by rules you can read.
Who's building it
I'm Zee, an engineer in the UK. I've been paged at 3am for a disk at 81%, for the same alert five times, and for alerts that resolved before I found my laptop. BlipLite is what I wanted on the other side of those pages.
It's built in public, by one person, with a small group of design partner teams. If you join, you talk to me, not a sales team, and what your alerts need decides what I build next.
What we believe
Calm by default
The quiet state is the goal. A page should be rare, clear and worth waking for.
AI explains, policy decides
AI should explain alerts and escalate when unsure. It should never quietly drop what you needed to see.
Small teams first
Good alert hygiene shouldn't need a platform team or an enterprise budget.
Private beta
Run it in shadow mode on your own alerts.
We're onboarding 10 teams. Your paging stays exactly as it is while you see what BlipLite would have done.
Try the demo first