# Robusta.dev > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-10-04. - **Brand record:** https://optimly.ai/brand/robusta-dev - **Dataset:** https://optimly.ai/brand/robusta-dev.json - **Markdown:** https://optimly.ai/brand/robusta-dev/llms.txt - **Official website:** https://robusta.dev - **Slug:** robusta-dev - **Categories:** saas-cloud-software ## Overview - **Tagline:** AI-powered automatic root cause analysis and alert investigation, leveraging HolmesGPT for evidence gathering across diverse data sources, and offering centralized control via the Robusta Platform with flexible deployment options. Source: Brand's website (https://robusta.dev) · 2026-10-04 - **Description:** Robusta is an AI-powered SRE agent designed to automatically investigate alerts and find root causes. It leverages HolmesGPT to connect with existing monitoring, ITSM, and cloud tools, providing automated analysis, chat-based interaction, and centralized control through the Robusta Platform. It is available as SaaS, self-hosted, or open source. Source: Brand's website (https://robusta.dev) · 2026-10-04 ## Offerings - **Core capabilities:** - Robusta AI-powered SRE Agent - Robusta Platform - HolmesGPT Source: Brand's website (https://robusta.dev) · 2026-10-04 - **Pricing:** Subscription (SaaS/Self-hosted), Freemium (Open Source) Source: Brand's website (https://robusta.dev) · 2026-10-04 ## Audience - **Target industry:** Site Reliability Engineers (SREs), DevOps teams, IT Operations teams Source: Brand's website (https://robusta.dev) · 2026-10-04 ## Landscape - **Competitors:** - PagerDuty - Datadog - Splunk - Moogsoft - BigPanda Source: Brand's website (https://robusta.dev) · 2026-10-04 Page last updated 2026-10-17. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.