Incident/Ops
I've been an on-call engineer at startups where "incident management" meant someone panic-creating a Slack channel called #fire-fire-fire, or all incidents handled in the #incidents channel at the same time... and the postmortem was whatever someone remembered to write in Notion three days later. So I built a Slack bot to fix my own workflow. Figured I'd share it. What it does: "/incident start sev2 API latency spike" creates a dedicated channel, invites whoever's on-call, pins the details, and starts recording a timeline. When you run "/incident resolve", it uses GPT-4 to analyze…
Incident/Ops launched on January 6, 2026 with 59 votes, #512 of 14,585 launches that month and more than 95% of that year's launches.
What it does
Run incidents, manage on-call rotations, and generate clean postmortems, all without leaving Slack. Built for engineering teams who move fast.
Run incidents, capture timelines, and generate AI-powered postmortems directly in Slack. Built for engineering teams who move fast.
Run incidents, manage on-call rotations, and generate clean postmortems—all without leaving Slack. Built for engineering teams who move fast. No context switching. No manual note-taking. Just run incidents naturally in Slack. Kick off tracking with a single command. Your team is notified instantly. Add timeline events as you go. Every update is captured automatically. AI analyzes the timeline and generates a clean, structured postmortem. From the first alert to the final review, IncidentOps captures what matters and helps your team learn from every incident. Manage incidents where your team already works. No context switching, no new tools to learn. Start, update, and resolve incidents with…from incidentops.io
In the maker’s words, at launch
I've been an on-call engineer at startups where "incident management" meant someone panic-creating a Slack channel called #fire-fire-fire, or all incidents handled in the #incidents channel at the same time... and the postmortem was whatever someone remembered to write in Notion three days later. So I built a Slack…
Does a similar job
all alternatives →
Autonomous Incident Reports & FixesMar 2026 · prodrescueai.com · ▲7Hi HN, Most of us have been there: It’s 3 AM, there’s an outage, and the #incident channel is exploding with 200+ messages. Once the fix is deployed, the real pain begins—spending 4 hours reconstructing the timeline for the post-mortem. I built ProdRescue AI to automate this. It’s an incident intelligence engine that correlates technical logs with human context from Slack. How it works: Native Slack Integration: Connect via OAuth 2.0. We only access channels you explicitly invite the bot to. Contextual Correlation: It maps Slack timestamps to log events, identifying not just what failed, but…
More ai this month
the category →
Paintings by AI models: programs run through a simulation of oil paint.
AI · 20d ago · stillwet.art
PixVerse R2▲381A real-time world model you can explore and change
AI · 29d ago · world.pixverse.video
Source: Product Hunt launch ↗ · launch text quoted in part
Launched alongside, January 2026
the whole month →- IN
Hey HN! I wanted to share something I built over the last few weeks: isometric.nyc is a massive isometric pixel art map of NYC, built with nano banana and coding agents. I didn't write a single line of code. Of course no-code doesn't mean no-engineering. This project took a lot more manual labor than I'd hoped! I wrote a deep dive on the workflow and some thoughts about the future of AI coding and creativity: http://cannoneyed.com/projects/isometric-nyc
AI · Jan 2026 · cannoneyed.com
Automatic AI-powered code reviews the moment you open a PR
Dev tools · Jan 2026 · kilo.ai
