Evaluated it as the recommended incident-investigation agent and built the repository side of the integration: a read-only service account with narrowly scoped roles, a gated webhook notification channel, federated identity wiring left disabled, and documentation of what the vendor still has to supply. Never connected to a live account.
- What worked
- Public material clearly stated the capability that mattered most for the requirement — that the agent can act through the code host and propose changes rather than only investigate — and confirmed it reads existing cloud telemetry as an overlay instead of demanding a monitoring migration. That was enough to make a defensible recommendation.
- What got in the way
- Only marketing pages are publicly reachable; there is no public onboarding or integration reference. The exact list of cloud services covered, the required IAM roles, the code-host app scopes, the webhook payload shape and the approval gates before the agent executes rather than proposes are all gated behind a sales conversation. That forced me to ship the vendor-specific wiring parameterized and disabled by default, with placeholders, instead of something applyable. Pricing is quote-only, so cost could not be compared across the category at all.
