Resolve AI
AI SRE that goes on call for engineering teams: a team of specialized agents triages alerts and investigates incidents in parallel, with every mitigation action waiting for human approval.
Resolve AI builds an AI SRE that goes on call on a team's behalf. The On-call Agent holds the pager and triages alerts, the Incident Resolution Agent investigates with a team of domain specialized agents that pursue hypotheses in parallel and have a dedicated reviewer check findings against production evidence, and Issue Remediation works recurring problems. Engineers follow an evidence trail and a Workbench view of what each agent is doing, and can redirect agents or add context mid investigation.
Action is gated. Mitigation actions, such as silencing alerts in Grafana, Datadog, AlertManager, Kloudfuse or Sumo Logic, reverting commits or running GitHub Actions, execute only after a person approves them in the Resolve UI or Slack, and every proposal is recorded with who proposed it, who approved or rejected it and what was affected. Teams guide investigations with Team Knowledge, runbooks, docs and skills held at organization and team level, and tune accuracy by rating reports and re-running the same alert after a change to compare results.
Resolve connects to about 40 observability, cloud, code and ticketing systems, directly or through a Satellite agent that keeps credentials inside the customer's infrastructure, and runs as a shared multi tenant service or a dedicated single tenant deployment with customer keys. It exposes a REST API, an MCP server and assistant plugins, holds SOC 2 Type II, GDPR and HIPAA, and prices through credit metered contracts with no public rates.
Vendor details
Canonical URL
https://resolve.ai
Category
SRE / DevOps agent
Subcategory
AI SRE agent
Funding status
Independent, founded by former Splunk engineers behind OpenTelemetry and Log Insight. Reached unicorn status at a $1 billion valuation, with a $125 million round reported in early 2026 and more than $160 million raised in total. Named customers include Coinbase, DoorDash, MSCI, Salesforce, Zscaler, MongoDB, Toast, and Pinecone.
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Connects to about 40 systems, including AWS, GCP, Datadog, Dynatrace, Splunk, Grafana, New Relic, Honeycomb, Sentry, PagerDuty, ServiceNow, Snowflake, GitHub, Atlassian and Glean, with Slack and Microsoft Teams apps; a Satellite agent in Kubernetes or ECS reaches on premises tools. Exposes a REST API, an MCP server, alert webhooks and a Temporal integration.
In practice
An incident spans logs, metrics, traces and three services and your on call engineer is guessing. Resolve runs specialized agents on parallel hypotheses and a reviewer checks the root cause against production evidence.
Alerts pile up overnight before anyone looks. Resolve's On-call Agent holds the pager and triages alerts, escalating with context.
You want the SRE agent inside your own automation, not a separate dashboard. Resolve exposes a REST API, an MCP server and assistant plugins to trigger and read investigations.
Sources & related URLs
Agentic Index coverage score
10.5 / 14 capabilities · 75%
| Integrations & Tool Calling | Full |
|---|---|
|
A documented integration catalog of about 40 systems (AWS, GCP, Datadog, Dynatrace, Splunk, Grafana, New Relic, PagerDuty, ServiceNow, Sentry, Snowflake, GitHub, Atlassian, Slack, Teams), and on approval the agent creates silences, downtimes or mutes in Grafana, Datadog, AlertManager, Kloudfuse and Sumo Logic and triggers commit reverts and GitHub Actions. SourceResolve docs llms.txt index and Mitigation Actions, and Incidents page; docs.resolve.ai/mitigation-actionsread 2026-09-29 |
|
| Workflow Orchestration | Full |
|
'A team of domain-specialized agents investigates in parallel and verifies findings against production evidence', pursuing parallel hypotheses that engineers can redirect, with a dedicated reviewer validating findings; custom agents compose Resolve's MCP, API and skills into the customer's workflows, and Temporal connects orchestration platforms. Sourceresolve.ai/product/incidentsread 2026-09-29 |
|
| Knowledge Grounding & RAG | Full |
|
Team Knowledge is a maintained store of runbooks, docs, dashboard guidance and skills at organization and team level that Resolve 'dynamically activates' during investigations, examining all knowledge tied to the alert and its owning teams; the homepage names Hivemind for production state awareness across alerts and incidents. Sourcedocs.resolve.ai/team-knowledgeread 2026-09-29 |
|
| Human Oversight & Guardrails | Full |
|
'Every action requires explicit human approval before execution': proposals are approved or rejected in the Resolve UI or Slack, 'Resolve never has direct access to execute write APIs', and write permissions are enabled per integration. Sourcedocs.resolve.ai/mitigation-actionsread 2026-09-29 |
|
| Security, Identity & Governance | Full |
|
Access surface: SSO (Google, Okta, Azure AD), SCIM directory sync with sign in enforcement, RBAC, access limited to roles, environments or namespaces, and audit logs. Compliance: SOC 2 Type II, GDPR and HIPAA, with a trust center. SourceResolve security page and docs llms.txt index (Security and Administration pages); resolve.ai/securityread 2026-09-29 |
|
| Observability & Auditability | Full |
|
Each investigation shows an Evidence Trail with timestamps and verification and a Workbench of what each agent is doing, and 'Every action is recorded: who proposed it, who approved or rejected it, when, and what was affected' in an Activity Dashboard. Sourcedocs.resolve.ai/mitigation-actionsread 2026-09-29 |
|
| Memory & State Persistence | Unable to verify |
|
Nothing the agent writes for itself is documented as memory. Team Knowledge is written by people as runbooks, docs and skills, which the product applies as instructions during investigations, and feedback ratings are an evaluation input. No self learning knowledge graph is published. Sourcedocs.resolve.ai/team-knowledgeread 2026-09-29 |
|
| Deployment & Data Residency | Partial |
|
Two options: shared multi tenant cloud, or a dedicated single tenant cloud deployment with bring your own keys. The Satellite agent runs in the customer's Kubernetes or ECS and keeps credentials local, but it proxies queries into Resolve's cloud, which is connectivity rather than deployment; no region list or customer environment option is documented. Sourcedocs.resolve.ai/resolve-satelliteread 2026-09-29 |
|
| Prebuilt Agents, Templates & Packs | Full |
|
Separately named agents ship for their own jobs: the On-call Agent that holds the pager and triages alerts, the Incident Resolution Agent for root cause and mitigation, and Issue Remediation for recurring problems. No cost optimization or feature development agent is published. Sourceresolve.airead 2026-09-29 |
|
| Triggers & Channel Coverage | Full |
|
The On-call Agent 'goes on-call on your behalf', holding the pager and triaging alerts; alerts arrive by PagerDuty, Splunk On-Call and alert webhooks from any source, tasks run on schedules, and billing meters triages, investigations and incidents Resolve manages. Sourceresolve.airead 2026-09-29 |
|
| Model Flexibility & Routing | Unable to verify |
|
The homepage describes 'frontier LLM models combined with domain-specific models' without naming a provider, and no customer model choice is documented; provider undisclosed. Sourceresolve.airead 2026-09-29 |
|
| APIs, SDKs & MCP Extensibility | Full |
|
A documented REST API at app0.resolve.ai with bearer personal or organization tokens to trigger, list and read investigations, plus a Resolve MCP server and AI assistant plugins. SourceResolve docs, Resolve REST API and llms.txt index; docs.resolve.ai/resolve-rest-apiread 2026-09-29 |
|
| Testing, Debugging & Optimization | Full |
|
A documented way to evaluate a change: after updating knowledge or integrations, 'Reinvestigate alert' re-runs the same alert 'so you can compare the new result against the original', and thumbs up or down verdicts on each report collect under Analytics, Feedback. Sourcedocs.resolve.ai/tuning-accuracyread 2026-09-29 |
|
| Browser & Computer Use | Unable to verify |
|
Works through integrations, a Satellite proxy, Slack, a REST API and an MCP server; no browser, desktop or computer control is documented. SourceResolve docs llms.txt index and Incidents page; resolve.ai/product/incidentsread 2026-09-29 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Unable to verify against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Recent platform changes
Resolve AI officially launched its AI Production Engineer, an agentic AI system designed to automate production engineering tasks. The platform autonomously troubleshoots issues, manages operational tasks, and investigates incidents by leveraging context from source code, telemetry, and cloud infrastructure.
Bears on: Agent capability
View sourceResolve AI announced a $125 million Series A funding round led by Lightspeed Venture Partners. This brings its total funding to over $150 million and values the company at $1 billion, providing capital to scale research and development for its production AI agents.
Bears on: Agent capability
View sourcePricing
Contact sales; credit metered contracts, no public rates
Credits per unit of work (chats and tasks, investigations, incidents, triages), costs defined in the contract
Included quota
Contract defined credit allowance; no public tiers.
What is public
The credit meter (which actions consume credits) and the monthly cap on automated work; no dollar figures, tiers or credit costs.
Billing mechanics
Enterprise contracts metered in credits for the work Resolve does; each action's credit cost is set in the contract, and a monthly cap on automated work pauses background runs until the month ends or the cap is raised.
Cost watchouts
Every chat, task, investigation, incident and triage consumes credits at contract rates, so alert volume drives spend.
Variable cost rationale
Credits are consumed per action, so spend follows alert and investigation volume, bounded by an optional monthly cap.
Additional watchouts
Cost follows how much automated triage and investigation runs, so set the credit cap before turning on always on agents; nothing numeric is published.
Overage / add-ons
Not published; a monthly credit cap pauses automated work, never manually started work
Sales call required
Yes, required for paid access
Free / trial
Enterprise evaluations and proofs of value through sales; no self serve trial
Lowest paid plan
None public; enterprise contract only
Commercial notes
Independent, $1 billion valuation, more than $160 million raised, from founders behind OpenTelemetry and Log Insight. Coinbase reported ten times productivity and 73 percent faster RCA; DoorDash reported up to 87 percent reduction in time to RCA.
Key ambiguities
The credit meter is published; credit prices and any included allowance are not.
Related vendors
- AlertD — AI agents for AWS operations that run read only in the customer's…
- Anyshift — AI SRE built on a versioned knowledge graph of infrastructure, apps…
- Avesha — Obliq, Avesha's autonomous AI SRE for Kubernetes and agentic…
- Better Stack — Better Stack offers incident management with built in on call,…
- Bluebricks — Context and control layer that lets AI agents operate cloud…
- Cased — AI workflows for infrastructure and platform engineers: default and…
Alternatives to Resolve AI
The closest documented capability profiles to Resolve AI among SRE and DevOps agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- PagerDuty11.0 / 14Adds documented Memory & State Persistence
- Better Stack9.5 / 14Adds documented Memory & State Persistence
- Bluebricks10.5 / 14Adds documented Memory & State Persistence
- Causely9.5 / 14Fuller documented coverage on Deployment & Data ResidencyResolve AI vs Causely →
- Itential11.5 / 14Adds documented Model Flexibility & Routing
- Metoro9.5 / 14Fuller documented coverage on Deployment & Data Residency
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded