Start here
Nodrik is a read-only incident investigator for teams on Google Cloud. When a Cloud Monitoring alert fires, Nodrik 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.
What it does
Section titled “What it does”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. Nodrik does that correlation instead, and posts one answer to the thread: the culprit, the evidence, a suggested fix, and how confident it is.
Nodrik cuts investigation time. It does not solve incidents. That is a deliberate line, not modesty. Every investigation ends with a card, whether Nodrik 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.
What it reads
Section titled “What it reads”Nodrik reads your telemetry transiently, at the moment an alert fires, through your own Google Cloud APIs:
- Log entries (Cloud Logging), including the Admin Activity audit log — the IAM change or config update behind an incident nobody committed
- Metric time series (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 of what Nodrik reaches for by itself, and it does not grow. The one way to widen it is yours to open: read-only tools you host and declare, which Nodrik calls at your invitation and under your own credentials — see Connect your own tools.
Every one of the reads above happens under a service account you create and grant — see Connect a Google Cloud project for the exact roles.
What it never stores
Section titled “What it never stores”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 Nodrik keeps, in europe-west1, is the report Nodrik
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.
Where to go next
Section titled “Where to go next”- New to Nodrik and evaluating it: Sign up, then Connect a Google Cloud project.
- Already signed up, setting up: Connect Slack and Connect GitHub.
- Want Nodrik to check something only your own systems know: Connect your own tools.
- Wondering what a report actually contains: Reading the card.
- Adding a colleague, or wondering what they will be able to change: Your team.
- Checking pricing or a billing question: Plans and billing.
- Reviewing this for a security sign-off: Security and trust.
- Something went wrong: Support.