Relvy AI GTM brain

Relvy sells AI-assisted runbook execution and debugging notebooks to on-call software engineering teams.

category

AI incident investigation

market profile

  • text: Responders must gather evidence from dashboards, logs, traces and code during production outages.
  • text: Relvy competes with both AI investigation products and broader observability platforms.

personas

  • title: On-call engineer or SRE
    pains:
    • Jumping between telemetry tools during an outage
    • Losing time reconstructing prior investigations and runbook steps
  • title: Platform engineering or reliability lead
    pains:
    • Inconsistent triage across on-call rotations
    • Need to trust and audit AI recommendations before production changes

icp

  • text: Software organizations with production on-call rotations, alerting, documented runbooks and a substantial observability footprint; exact employee size is unconfirmed.
  • text: Teams already using tools such as Datadog, Grafana, New Relic or PagerDuty are plausible integration-ready accounts.

message pillars

  • text: Turn existing natural-language runbooks into automated investigations.
  • text: Connect the telemetry stack so investigations use current operational evidence.
  • text: Keep engineers in control of actions against production.

objections

  • objection: Will an AI take unsafe production actions?
    response: Relvy says its AI recommends actions and requires human approval before touching production; verify permissions in a pilot.
  • objection: Will it find root causes in our unique environment?
    response: Run a bounded trial against historical incidents and review evidence in the notebook; benchmarks do not establish accuracy on your own incidents.
  • objection: Will it connect to our tools?
    response: The repository lists Datadog, New Relic, Grafana, Elastic and PagerDuty; confirm exact permissions and versions.

competitors

  • name: Scoutflo
    why: AI SRE incident investigation and root cause analysis.
  • name: Better Stack
    why: Unified observability and uptime tools address related incident workflows.
  • name: Datadog
    why: Cloud monitoring and incident investigation platform, also an integration partner.

influencers

  • name: Bharath Bhat
    url: https://www.linkedin.com/posts/bharathpbhat_at-relvy-ai-yc-f24-we-are-building-a-debugging-activity-7323794807976341504-xsZH
    why: Discusses engineers guiding Relvy's debugging assistant.

keywords

  • AI incident response
  • automated root cause analysis
  • AI on-call engineer
  • runbook automation
  • SRE alert investigation
  • debugging notebooks

voice

  • Technical and direct
  • Operational and outcome focused
  • Emphasizes engineer control

signals

  • text: An organization is expanding on-call coverage or struggling with repetitive incident triage.
  • text: A team maintains markdown runbooks and uses supported telemetry or paging tools.

stack

  • Datadog
  • New Relic
  • Grafana
  • Elastic
  • PagerDuty
  • Docker Compose

pricing

model: unknown

motion

hybrid

channels

  • GitHub
  • LinkedIn
  • Product Hunt
  • events
  • YC launch

confidence

medium

Founders

  • name: Bharath Bhat
    title: Founder/CEO
    role: CEO
    bio: Co-founder, CEO at Relvy AI. I enjoy building delightful AI powered software. Previously worked on efficient computer vision/language models for Google Pixel, YouTube and Uber.
  • name: Simranjit Singh
    title: Founder/CTO
    role: CTO
    bio: Co-founder and CTO at Relvy. Previously I worked at Microsoft and Amazon on researching and developing SOTA Computer Vision models. I also Co-Founded Vetan, a payroll app that was used by over 30k SMBs. Prior to that I developed distributed systems at Nutanix.

Back to YC companies