In plain English

A tireless junior analyst that shows its work.

For leaders and non-technical readers. No jargon.

The problem

A security team (a "SOC" — Security Operations Center) gets a flood of computer alarms every day — often thousands. Most are false alarms, but a few are real attacks. There are never enough trained people to check them all, so many alarms go unread — and the real threat can hide in the pile. Checking them is slow, repetitive, and exhausting, and good analysts burn out and leave.

What blue-kakapo is

Think of it as a careful junior analyst that never sleeps. For each alarm it gathers the facts, explains what it found in writing with its sources, and gives a clear verdict: "this is harmless, I closed it," or "this looks dangerous — a human should look." It does the boring first pass so your experts spend their time on what actually matters.

It's named after the kākāpō — a rare, nocturnal, remarkably clever New Zealand parrot. Watchful at night, resilient, and one of a kind. That's the idea: a vigilant night-shift guardian for your "blue team" (the defenders).

Why it's different (and safer)

How you'd get it

It's free and open-source. A security engineer can start it on a laptop in about a minute, connect it to your existing tools, or run it across the company on your own servers. There's nothing to buy and no per-use meter.

For leaders — talking points

What it does not do

It isn't magic and it can still be wrong — which is exactly why a person stays in the loop on anything serious. It doesn't replace your detection tools; it helps make sense of what they report. See the honest, detailed "what it can & cannot do".

See the overview → Technical docs