Reduce Ops by Managing oncalls, tickets, incidents over Slack
Hi HN! In all the organisations, we have worked, SDEs and EMs spend a lot of time on on-call, incident operations, ticket operations - Constantly updating everyone on the current status of an incident, figuring out who is the current Oncall in Slack threads like @dev-oncall, Missing following up on Action Items post-incident, creating a post-mortem RCA document, Spending time on creating and analysing oncall reports For each of these tasks, there is a Developer who doesn't like to spend time on these tasks and an Engineering leader who stresses maintaining this culture. This is why we…
Reduce Ops by Managing oncalls, tickets, incidents over Slack launched on November 9, 2023 with 24 votes, #1,248 of 4,332 launches that month and more than 75% of that year's launches. The site was still online in September 2026, 2 years on.
In plain words
Reduce Ops is a Slack-integrated tool that streamlines on-call management, incident operations, and ticket handling for software development teams. It automates tasks like tracking current on-call engineers, updating incident status, managing post-incident action items, and generating on-call reports—all within Slack. The tool syncs with PagerDuty and Opsgenie schedules and supports round-robin rotations, designed to reduce administrative overhead for developers and help engineering leaders maintain operational discipline.
written from the facts on this page · September 2026
From the sources
Manage and create on-call schedules, sync oncalls with Slack usergroups, Jira and JSM on Slack, Opsgenie on Slack, and run incident response inside Slack…
Sync Opsgenie and other tools' oncalls with Slack usergroups. Create your own round-robin rotations, assign tasks in round-robin manner, and run unlimited incidents - all inside Slack and Teams. Build round-robin or custom schedules directly in Pagerly. Daily, weekly or custom interval shifts, with on-call responsibility auto-assigned across the team. Add phone numbers for paging and the on-call engineer receives a call, SMS and email. Connect AWS, Datadog or Sentry to raise incidents automatically. Pagerly combines the context and gives responders what they need without leaving Slack - auto-generated Zoom links, Jira tickets and dashboard links in the channel. Simple, clear status pages…from pagerly.io
In the maker’s words, at launch
Hi HN! In all the organisations, we have worked, SDEs and EMs spend a lot of time on on-call, incident operations, ticket operations - Constantly updating everyone on the current status of an incident, figuring out who is the current Oncall in Slack threads like @dev-oncall, Missing following up on Action Items…
Does a similar job
all alternatives →
Incident/OpsJan 2026 · incidentops.io · ▲59I'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…
I built an open-source tool to make on-call suck less2024 · github.com · ▲319Hey HN, I am building an open source platform to make on-call better and less stressful for engineers. We are building a tool that can silence alerts and help with debugging and root cause analysis. We also want to automate tedious parts of being on-call (running runbooks manually, answering questions on Slack, dealing with Pagerduty). Here is a quick video of how it works: https://youtu.be/m_K9Dq1kZDw I hated being on-call for a couple of reasons: * Alert volume: The number of alerts kept increasing over time. It was hard to maintain existing alerts. This would lead to a lot…
More dev tools this month
the category →
Contribute to oosexgang/hackios-xnu-kernel development by creating an account on GitHub.
Dev tools · 1d ago · github.com
open-source IDE for thoughtful software design. Contribute to devdotfast/whiteboard development by creating an account on GitHub.
Dev tools · 29d ago · github.com
Contribute to reladraw/reladraw development by creating an account on GitHub.
Dev tools · 27d ago · github.com
OpenBot▲362Grok Bot alternative: free, local, open-source, multiplayer
Dev tools · 25d ago · openbot.run
Talanoa▲346Hi HN, I’m a fullstack developer, and honestly, I’ve lost count of how many side projects I’ve worked on over the years. But one idea kept coming back to me: a different kind of email client. It first came to me in 2014: “What if we could handle emails more like conversations?” Every year, I’d revisit this concept in my “Build Notes.” Ten years later, no one had built exactly what I had in mind — so I finally decided to do it myself. That’s how Talanoa was born. I wanted something focused on people, not timelines. I was tired of marking messages as unread just to remember to reply later, or…
Dev tools · 22d ago · talanoa.email
Source: Show HN post ↗ · launch text quoted in part
Launched alongside, November 2023
the whole month →
Discover & book top creators to promote your product
Growth · 2023 · passionfroot.me
SpeedVitals▲829Hi HN, I’m Kashish, one of the co-founders of SpeedVitals, a platform for testing & monitoring website performance with a major emphasis on Core Web Vitals. Until now, our platform has only focused on Synthetic/Lab testing, such as Lighthouse tests and TTFB tests. But now, we have developed a Real-User Monitoring platform that doubles up as a Web Analytics tool. One major feature we have that most RUM tools lack is Performance Audits. Just like Lighthouse audits work on Lab test data, our audits work across all the real-user visits and gives suggestions on what task to prioritize first.…
Dev tools · 2023 · speedvitals.com