Skip to content
BlipLite

Product

From a wall of alerts to a short list of decisions.

BlipLite turns raw alerts into grouped, explained, policy-checked decisions, then hands the pages to the platform your team already uses. Here's each stage, and what's in the beta today.

Request beta accessGet an Alert Noise Report

A short animation in five chapters: alerts arrive from every source, duplicates are grouped, AI explains and raises the one that matters, your paging policy decides what reaches a person, and the page is handed to PagerDuty.

Sample data from a fictional workspace

01 · Ingest

In the beta

One receiver, next to your existing routes.

Add BlipLite as a webhook receiver with continue: true, so it gets a copy and your current routing keeps paging. It reads Alertmanager and Grafana payloads and tracks each alert from firing to resolved.

A secret URL per source, shown once and stored as a hash. A generic JSON webhook for everything else.

receivers:
  - name: bliplite
    webhook_configs:
      - url: https://<your-bliplite-app>/api/ingest/<source-secret>
        send_resolved: true

route:
  routes:
    # First in the list: BlipLite gets a copy, then your existing routes carry on.
    - receiver: bliplite
      continue: true

02 · Group and triage

In the beta

Group first. Then explain.

Alerts with the same rule, service and environment become one group, with flapping and self-resolving alerts tracked. Triage then summarises the group, suggests where to look, and may suggest a higher severity.

Secrets are redacted first. Triage has 8 seconds; on any failure the alert keeps its own severity.

Illustrative example

group: HighErrorRate · checkout · production

seen: repeatedly in the current window

severity: high

Checkout errors keep climbing across checks. Likely to get worse.

next: check recent deploys and checkout dependencies

03 · Decide

In the beta

Your paging policy, applied the same way every time.

Choose 24/7, business hours, no paging or digest only. The policy turns each group into page, notify or digest, and records the reason in a sentence.

Only rules you set can hold back a page. AI can escalate, never suppress. Custom rules are next.

The business hours preset
in hours · critical, high
page now
in hours · medium
notify channel
out of hours · critical
page now
out of hours · high
notify, page at 09:00
anything else
morning digest

04 · Hand off

Being built

Keep your incident platform. Send it less.

Pages will go to PagerDuty or incident.io with a stable key per group, so a resolve in BlipLite resolves downstream too. Today, shadow mode records what it would send instead.

Your schedules, escalations and incident process stay exactly where they are.

Illustrative handoff

→ PagerDuty · trigger · key=[alert fingerprint]

→ PagerDuty · resolve · key=[alert fingerprint]

→ incident.io · firing · key=[alert fingerprint]

The control centre

One place to see, silence and understand.

  • Live feed

    Every group, its decision and the reason, with "was this the right call?" feedback. In the beta.

  • Sources

    What's connected, when it last spoke and how much of its output needed a human. In the beta.

  • Silences

    Mute by source, pattern or time window, always visible. Next.

  • Monthly summary

    What was paged, held and resolved on its own, and which rules to fix. Later.

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