git404hub

what is incident-ai fr?

chs018/incident-ai — explained in plain English

Analysis updated 2026-05-18

0TypeScriptAudience · ops devopsComplexity · 3/5Setup · moderate

tl;dr

A hackathon project that uses AI to speed up incident response by automatically analyzing outages, mapping cascading failures, and suggesting fixes.

vibe map

mindmap
  root((repo))
    What it does
      Automated incident triage
      Root cause analysis
      Blast radius mapping
    Tech stack
      Next.js
      Supabase
      pgvector
      Groq
    Use cases
      SRE dashboards
      Incident memory search
      Model routing
    Audience
      SRE teams
      DevOps engineers
      Hackathon judges
    Setup
      Supabase keys
      Groq API key
      Vercel deploy

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Get an automatic root cause explanation when a monitored system throws an incident.

VIBE 2

Visualize how a failure in one service could cascade through dependent services.

VIBE 3

Store past incident resolutions in a searchable memory so teams do not repeat the same fixes.

what's the stack?

Next.jsTypeScriptSupabasePostgreSQLpgvectorGroqTailwind CSS

how it stacks up fr

chs018/incident-ai0xkinno/astraea0xkinno/halcyon
Stars000
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatehardhard
Complexity3/54/54/5
Audienceops devopsdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires Supabase and Groq API keys before the app will run.

in plain english

Incident AI, also called CascadeFlow AI in the README, is a hackathon project built for HackwithChennai 2026 that aims to speed up how engineering teams respond to system outages. The idea is that when a major outage happens, engineers currently have to manually dig through monitoring tools like Datadog and Prometheus and coordinate over Slack, which takes time. This project tries to automate that triage process using AI. The README describes a dashboard showing live system health across monitoring services, an automated root cause analysis feature that explains what broke and suggests fixes, and a visual map showing how a failure in one part of a system could cascade into others. It also describes a memory feature built on a vector database that would let the system recall how past incidents were resolved, and a feature that routes different tasks to different sized AI models depending on how much reasoning they need. Under the hood, the project uses Next.js 15 for the frontend, Supabase with PostgreSQL and pgvector for data storage, and the Groq API running Llama 3.3 70B for the AI reasoning. Styling is done with Tailwind CSS and framer-motion for animations. To run it locally, you clone the repository, install dependencies with npm or pnpm, add Supabase and Groq API keys to an environment file, and start the development server. It can also be deployed to Vercel with the same environment variables. The README makes large claims about cost savings and accuracy numbers, but these read as illustrative rather than measured results, since this is presented as a hackathon build rather than a project with published benchmarks or a track record in production. There is no license file mentioned beyond a note that it targets SOC2 Type II compliance standards, which is a goal stated in the text rather than something verified.

prompts (copy fr)

prompt 1
Help me set up the Supabase pgvector schema this project expects for its memory library.
prompt 2
Walk me through connecting Datadog or Prometheus alerts into this incident triage app.
prompt 3
Explain how the dynamic LLM model routing between Groq models is meant to work here.
prompt 4
Show me how to deploy this Next.js project to Vercel with the required environment variables.

Frequently asked questions

what is incident-ai fr?

A hackathon project that uses AI to speed up incident response by automatically analyzing outages, mapping cascading failures, and suggesting fixes.

What language is incident-ai written in?

Mainly TypeScript. The stack also includes Next.js, TypeScript, Supabase.

How hard is incident-ai to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is incident-ai for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.