AI SRE companies, products & suppliers
Incident and reliability products that diagnose production systems. Jobs: incident summarisation; runbook suggestions; root-cause hypotheses.
What is AI SRE?
Incident and reliability products that diagnose production systems. Jobs: incident summarisation; runbook suggestions; root-cause hypotheses.
What problems does it solve?
Incidents still start with a blank timeline and too many dashboards.
Typical business use cases
- Incident summarisation
- Runbook suggestions
- Root-cause hypotheses
Important capabilities
- Telemetry connectors
- On-call context
- Timeline
What buyers should evaluate
- Access to production telemetry
- Whether it can act
- Retention of incident data
Risks and governance considerations
An SRE bot that restarts services or pages the wrong people.
Procurement checklist
- Read vs act
- Paging policy
- Incident data retention
Relevant AI Trustmark assurance
AI Trustmark independent findings appear only when an assessment or certificate exists. Category membership does not imply verification.
Products and providers
Open a product profile for its catalogue details, or use the provider link for the company profile. Claimed listings appear first, then by name. Payment never changes the order.
Amazon DevOps Guru is an AWS machine learning service that detects abnormal operating patterns in applications. It analyses operational data and metrics to flag anomalies, group re
By BigPanda
BigPanda is an agentic IT operations platform that uses AI to automate IT detection, triage and resolution for ITOps and ITSM teams. It enriches incident tickets with context, root
By Ciroos
Ciroos is an AI SRE solution that delivers root cause clarity and SRE toil reduction, and delivers measurable ROI in complex enterprise environments. Ciroos is Ciroos's software pr
By Harness
Harness is a unified AI software delivery platform to manage the SDLC using purpose-built AI agents. Harness AI SRE is Harness's software product, from Harness Inc. Published at ha
By IBM
IBM Concert Operate, formerly IBM Cloud Pak for AIOps, is an IT operations product being brought onto the IBM Concert platform to give a single operational layer across application
By Keep
The open-source AIOps (AI for IT operations) and alert management platform. Keep is Keep's software product, from Keep Alerting LTD. Published at keephq.dev. Directory filing: AI S
By Microsoft
Azure SRE Agent is Microsoft's AI agent for site reliability engineering on Azure. It diagnoses incidents, orchestrates mitigations and helps optimise cloud operations to reduce op
By PagerDuty
Turn incidents into intelligence. PagerDuty's AI-first Operations Platform helps you automate, resolve, and prevent critical issues — from detection to resolution. PagerDuty O
By Resolve AI
Resolve AI is Resolve AI's software product, from Resolve AI, Inc. Published at resolve.ai. Directory filing: AI SRE. Deployment options: SaaS. Recorded capabilities: Tool use and
Products
Claimed products appear first. Ranking packs and payment do not change this list.
- Amazon DevOps Guru· Amazon Web Services
- AWS DevOps Agent· Amazon Web Services
- Azure SRE Agent· Microsoft
- BigPanda· BigPanda
- Ciroos· Ciroos
- Harness AI SRE· Harness
- IBM Concert Operate· IBM
- Keep· Keep
- PagerDuty Operations Cloud· PagerDuty
- Resolve AI· Resolve AI
Related categories
Relevant procurement and assurance guides
Frequently asked questions
What is AI SRE?
Incident and reliability products that diagnose production systems. Jobs: incident summarisation; runbook suggestions; root-cause hypotheses.
What should not be listed as AI SRE?
Products whose buyer job is DevOps pipeline assistants, observability platforms, or generic coding assistants. Those belong on their own category page so search queries are not split.
Has AI Trustmark independently assessed every AI SRE supplier?
No. A category listing is descriptive. Independent assessment is shown only on company or product pages that carry Trustmark evidence.
Should coding assistants be allowed to send private source code to third-party models?
That is a buyer policy decision. Procurement should require the default data-use terms, retention, whether snippets leave the organisation, and whether secrets are redacted. A listing under coding assistants does not mean code stays on-premises.
How should prompt injection and tool-output attacks be controlled?
Agents that read untrusted content or tool output can be instructed to exfiltrate data or take writes. Buyers should ask what is treated as untrusted, whether tool output can change the plan, and what tests were run. Scanner marketing is not the same as independent testing.
How can buyers tell whether customer data is used to train models?
Ask whether prompts, files, logs or outputs are used to train, fine-tune or evaluate models, including by subprocessors. Require the contractual default, any opt-out, and whether the setting can be changed silently. Treat marketing 'we do not train' claims as unverified until evidenced.
What model or provider changes should a buyer insist on being told about?
Material change usually includes a new model family, new region, new subprocessor, new write-capable tool, or a change that affects logging, privacy or human oversight. Those changes should trigger evidence refresh rather than a silent release.
How should buyers verify where AI customer data is processed?
Ask for the named processing locations, cloud regions and any subprocessors that see prompts, files or outputs. A directory listing is not evidence of residency. Independent assessment records the locations that were in scope on the assessment date.