Skip to content

Start here

Bobbin is a read-only incident investigator for teams on Google Cloud. When a Cloud Monitoring alert fires, Bobbin reads your logs, metrics, deploys and commits — inside your own project, using an identity you grant — and posts a likely cause to Slack with the evidence behind it.

An alert fires. Somebody would otherwise open six console tabs and start correlating logs, metrics and the last deploy by hand — usually at the worst possible time. Bobbin does that correlation instead, and posts one answer to the thread: the culprit, the evidence, a suggested fix, and how confident it is.

Bobbin cuts investigation time. It does not solve incidents. That is a deliberate line, not modesty. Every investigation ends with a card, whether Bobby found the culprit or ran out of road — an honest “I don’t know, here is what I checked” is a good outcome, not a failure. See Reading the card for what that looks like.

Bobbin reads your telemetry transiently, at the moment an alert fires, through your own Google Cloud APIs:

  • Log entries (Cloud Logging)
  • Metrics and alert policies (Cloud Monitoring)
  • Error groups (Error Reporting)
  • Cloud Run revisions and their configuration
  • Commit and diff metadata, if you connect GitHub

That is the complete list. Every one of those reads happens under a service account you create and grant — see Connect a Google Cloud project for the exact roles.

This is the honest privacy claim, stated precisely because the people reading it are technical:

We never store your telemetry or code. Nothing persists outside your Google Cloud project except the investigation report.

Not “we can’t read it” — we transiently can, while serving an investigation. What Bobbin keeps, in europe-west1, is the report Bobby posted and the transcript that produced it, both redacted before they are written. Your logs, metrics and code are never copied out, never indexed, and never stored. Full detail: Security and trust.