Skip to main content

Open source · MIT licence · Self-hosted

From application noise to trusted security signal.

Bower collects the security events that matter, removes sensitive details before they are stored, and proves their arrival in Microsoft Sentinel.

tar -xzf bower-collector-offline-0.1.0-linux-amd64.tar.gz
cd bower-collector-offline-0.1.0-linux-amd64
(umask 077; cat >seed/enrolment-token) # paste the one-time token, then Ctrl-D
sudo ./install.sh --endpoint https://bower-management.example.com/ --environment production
Full linux guide →

Collectors run on Linux, Windows and containers. The console runs in your tenant.

5stages, Collect to Prove
6outputs, from Logs Ingestion to S3
7signed packs
0events kept that policy does not name

01 How it works

A deliberate path, at every step.

Inspired by the bowerbird, which selects and arranges what is valuable. Bower is a security telemetry bridge, not a general log shipper, a SIEM or a replacement for Azure Monitor Agent.

  1. 01

    Collect

    Applications, machines and cloud sources send security events to a collector you run.

  2. 02

    Select

    An approved, versioned policy keeps only the event types it names. Everything else is denied and explained.

  3. 03

    Arrange

    Events are structured and sensitive details are redacted before anything is stored.

  4. 04

    Deliver

    A durable, hash-chained queue delivers with retries, dead letters and audited replay.

  5. 05

    Prove

    A canary is queried in Sentinel. An evidence bundle records what was found.

Bower: scattered application events pass through a bowerbird-shaped network into selected blue security signals. Collect, Select, Arrange, Deliver, Prove.

02 What you get

Security events you can trust, and show you can.

03 Deploy

Run it where your events already are.

Start with the guide for your environment, then send your first verified event.

04 Connect

Sources and frameworks.

SDK guides for common web frameworks, plus host sources selected by signed pack parsers.

  • ASP.NET Core
  • Next.js
  • Express · Fastify · NestJS
  • Django · Flask · FastAPI
  • Rails
  • Laravel
  • Spring Boot
  • Go log/slog
  • Syslog
  • Windows Event Log
  • Local files
  • Docker containers

All guides →

05 Compare

Bower and a typical log shipper.

From vendor documentation reviewed in October 2026. Local tests do not prove tenant delivery.

TopicBowerTypical alternative
Proof of arrivalA canary is queried in Sentinel and the result is recordedStops at "the API accepted it"; checking Sentinel is manual
RedactionOn the host, deterministic, before anything is storedIn Azure after transfer, or a paid redaction processor
What is keptOnly event types an approved policy namesEverything configured, filtered later
Delivery accountingDurable queue, dead letters, audited replay, drift checksRows can be dropped without a per-record error
Tamper evidenceHash-chained queue ledger, witnessed headNot offered at the collector
ContentSigned, hash-pinned, tested packsUnsigned community content
Where it runsYour infrastructure; the console belongs to your tenantOften a hosted control plane

Send your first verified event.

A harmless test event, through policy, privacy, the queue and delivery, found by a query in Sentinel.