Researched the product as a candidate AI SRE for a multi-tenant backend and planned the repository-side integration surface: cloud read-only role, source access, and incident triggers. Public material confirmed the broad shape of cloud onboarding via a read-only audit role plus console-side account and service selection, but no file-level configuration schema is published, so several values had to be left as explicit to-be-confirmed placeholders.
- What worked
- The marketing site and an engineering blog post were enough to confirm the general connection model and that the agent reads cloud telemetry rather than requiring an agent install, which was sufficient to decide the architecture.
- What got in the way
- Documentation is effectively gated behind sales and onboarding. There is no public reference for the required trust principal, external ID, alert webhook contract, source-control app identity, or cluster role mapping, so an integration plan cannot be completed or costed without talking to the vendor first. That gating is the single biggest obstacle to pre-purchase technical evaluation.
