$ -weight: 500;">git clone https://github.com/Arvo-AI/aurora.-weight: 500;">git
cd aurora
make init
make prod-prebuilt
-weight: 500;">git clone https://github.com/Arvo-AI/aurora.-weight: 500;">git
cd aurora
make init
make prod-prebuilt
-weight: 500;">git clone https://github.com/Arvo-AI/aurora.-weight: 500;">git
cd aurora
make init
make prod-prebuilt - On-call scheduling — Flexible rotations, escalation policies, shift overrides
- Alert routing — 700+ integrations for ingesting alerts from every monitoring tool
- Multi-channel paging — SMS, phone, push notifications, email
- Incident coordination — War rooms, stakeholder communications, -weight: 500;">status pages
- SLA tracking — Urgency-based alerting and escalation
- AI noise reduction — AIOps add-on claims 91% alert noise reduction via intelligent correlation and deduplication - AI incident summaries ("catch me up" in Slack)
- AI-generated -weight: 500;">status updates
- AI postmortem drafts (Beta)
- SRE Agent for triage and approved remediation actions
- Probable Origin for pattern-based root cause suggestions - Analyze the alert context (severity, -weight: 500;">service, timing)
- Dynamically select from 30+ tools to investigate
- Execute -weight: 500;">kubectl, aws, az, gcloud commands in sandboxed Kubernetes pods
- Query logs, metrics, and recent deployments across cloud providers
- Search the knowledge base for relevant runbooks and past incidents
- Traverse the infrastructure dependency graph for blast radius
- Synthesize everything into a structured root cause analysis - Incident timeline with timestamps
- Root cause identification with evidence and citations
- Impact assessment
- Remediation steps (taken and recommended)
- One-click export to Confluence or Jira - PagerDuty receives alerts from your monitoring tools (Datadog, CloudWatch, Grafana)
- PagerDuty pages the right on-call engineer via SMS/phone
- Aurora receives the same alert via PagerDuty webhook (incident.triggered)
- Aurora's AI agents investigate autonomously in the background
- The on-call SRE opens Aurora and finds a completed RCA with root cause, timeline, and remediation
- Aurora generates the postmortem and exports it to Confluence - You don't need enterprise on-call — Your team is small enough that a simple rotation works
- You already have alerting — Datadog, Grafana, or CloudWatch can send webhooks directly to Aurora
- Investigation is your bottleneck — You're spending more time diagnosing than coordinating
- You need self-hosted — Compliance or security requires keeping incident data on-premise
- Budget is limited — PagerDuty + AI add-ons at $2,000+/mo isn't feasible - Aurora vs Traditional Incident Management Tools — Comparison with Rootly, FireHydrant, incident.io
- Root Cause Analysis: The Complete Guide for SREs — RCA techniques from manual to AI-powered
- Open Source Incident Management: Why It Matters — The case for self-hosted tools
- Aurora Documentation — Full setup and configuration guides
- PagerDuty Pricing — Official PagerDuty pricing page
- PagerDuty AIOps — PagerDuty's AI features