Relay investigates incident tickets across AWS and Azure, read-only, and gives your engineers a root cause report with the evidence behind every finding.
The 14:02 deploy set the service's task count to zero, so the load balancer had no healthy targets. Rolling back restores capacity.
The flow runs on its own for every ticket. Watch each step live, or come back to the finished report.
From DevRev or the console. Relay opens a case and starts the run in the cloud.
It matches the ticket to the right customer environment, and asks one clear question when it cannot tell.
Read-only agents check alarms, metrics, logs and recent changes in AWS or Azure.
A report with the cause, its confidence and the evidence behind every claim, posted to the ticket.
Relay does the first hour of an investigation and leaves the decisions to your team.
Every claim cites a tool result. A second pass looks for evidence against the cause before the report is posted.
The same intake, routing and report for both clouds, each case pinned to the environment it belongs to.
AWS DevOps Agent and Azure SRE Agent take over when Relay's own investigation is inconclusive.
Anything that would change production goes to an on-call approver first. Their reply resumes the run.
Each tool call streams to the console as it happens, from the first check to the final report.
Engineers rate each report against the real cause, so accuracy, speed and cost are tracked per agent.
Relay reads; it does not change. Access is scoped to one environment per case, and every action leaves a record. It runs in your own AWS account.
Agents use read-only roles and allow-listed tools. Nothing they call can change a customer's account.
Relay assumes a role each customer deploys, per case. Secrets stay in AWS Secrets Manager.
Every sign-in, change and agent action is recorded and archived with S3 Object Lock.
Amazon Cognito with multi-factor authentication, Microsoft sign-in and role-based access.
Sign in with your work account. Your Relay admin decides what you can see and do.