Changelog

0.2.2

27 September 2026

• Each plan now lists the support it actually includes. Team is priority email; Scale is priority email plus an onboarding call. The plan cards used to offer Slack Connect and a named contact, which Nodrik does not provide.

0.2.1

24 September 2026

• “What’s new” in the notification bell now links to the changelog, and stays read once you have read it. Each release is one short notice that opens its entry here, rather than the whole entry squeezed into the bell. Opening the bell used to leave the newest notices marked unread again a moment later, and a dismissed notice — or everything under Clear read — came back on the next refresh. Both now stick.
• Your project rows in Settings keep their shape. A project that is not monitored yet used to push its explanation into the row, which shifted the columns and stacked Grant access, Check again and Remove on top of each other. The explanation now sits on its own line under the row, and the buttons stay put in every state.
• Coming back from checkout now tells you it worked. After subscribing you land on Settings with a confirmation; your plan shows there as soon as Stripe confirms it, usually within seconds.
• Old console.getbobbin.dev links land on the console again, instead of failing to connect.

0.2.0

23 September 2026

• Action needed if you granted access before 22 September 2026. The grant script is now grant-nodrik-access.sh, and the Terraform module has been renamed to match — re-run whichever you used. The custom roles and the notification channel it creates are named after the product, and the old names are not the ones Nodrik looks for. The console wizard was already correct and needs nothing.
• Alerts from a newly connected project now actually arrive. Creating a notification channel was never enough on its own: Google’s Cloud Monitoring publishes through a service agent in your project, and that agent needed permission on the topic at our end — a grant only we can make, and one nothing was making. A project could show every role bound, the channel present and a green monitored pill while no alert it ever sent could be delivered. Nodrik now makes that grant as part of the same check, and says Confirming alerts until it has landed rather than claiming to be ready.
• The console has a left rail, and the top bar names your workspace. The navigation moved off the top of the page and down the side, where a tool’s navigation belongs, and the workspace you are looking at is now on screen rather than inside the account menu — which matters if you belong to more than one.
• Settings is three tabs instead of nine cards on one screen. Connections is your projects, Slack, GitHub and your own tools; Investigating is how Nodrik works and what it has seen; Workspace is leaving. The tab is in the address bar, so a link to one goes where you point it.
• Nodrik names the Slack channel it reports to, on the Slack card, instead of telling you it is the one you chose.
• How Nodrik writes a fix — gcloud or Terraform — is a labelled choice, not two buttons that looked like two actions.
• A suggested command now says whether it was checked against Google’s current documentation, in the console as well as in Slack. A command that had never been checked used to read exactly like one that had.
• Notifications can be cleared, and the ones you cannot clear are the ones that matter. The dismiss control was there and invisible unless you happened to hover the right row. Anything still needing you has no dismiss at all and goes away when the thing it is about is resolved — and “Nodrik has nowhere to send the answer” now clears when you connect Slack, which it never did. There is a Clear read for the rest.
• The privacy policy now says exactly which one thing is stored as you sent it. Everything Nodrik fetches is redacted before the model sees it and before anything is stored; your original alert is kept alongside, because it is what the card shows you and what a repeat alert is matched against.

0.1.0

20 September 2026

• Nodrik joins the Slack channel you point it at. Slack only delivers a mention from a channel the app is a member of, so a follow-up question asked in a channel nobody had invited Nodrik to went unanswered, with the report still arriving and nothing saying why.
• Ask Nodrik a question in a thread and it reacts immediately, so you can see the question landed while the answer is being written.
• A project’s Slack channel is a dropdown in Settings, showing the channel’s name rather than its id, and naming which one is your workspace default.
• If Slack is not connected, Nodrik turns an alert away instead of investigating it and posting nowhere. Nothing is charged for an alert it declines, and the console says why.
• Nodrik reads the stack you actually run, not just Cloud Run. When an alert is about a database, a queue, a load balancer or a cluster, it asks what that kind of thing fails on — Cloud SQL connections, replication lag, disk and transaction age together, in one step — and checks what else is firing in the project before concluding, the quickest way to tell one service breaking from the platform underneath it breaking.
• An extra read-only role lets Nodrik see a service’s configuration, not only its telemetry — Cloud SQL, Memorystore, GKE, Compute Engine or load balancing, granted one service at a time from the console, the script or the Terraform module, and nothing changes if you do not.
• Nodrik investigates GKE alerts from Kubernetes events, the cluster autoscaler’s reasons, OOM kills, container restarts and memory against limits, and the Kubernetes audit log — on the roles you granted on day one, never connecting to your cluster directly.
• One bad month is free. Your subscription only grows if two of your last three billing periods went over your monthly allowance — a single heavy period changes nothing, and you hear from us when it happens. It shrinks back the same way, without being asked, if you are consistently paying for capacity your last three periods did not use.
• Extra investigations raise your daily cap as well as your monthly allowance, and at your project limit the console works out whether the next tier is cheaper than another add-on and leads with whichever it is.
• Test alerts are ten a day, and the counter behind that is accurate — shared rather than per-server, with the Settings card showing how many you have left.
• Every investigation ends with a card, whether Nodrik found the culprit or ran out of road. Daily caps per plan stop a runaway alert storm spending a month’s fair use in an afternoon, and connecting GitHub lets Nodrik answer “what changed?” as well as “what broke?”.