Head Of DevOps at a tech vendor with 11-50 employees
Real User
Top 5
Jul 13, 2026
Incident.io can be improved with more integrations with leading observability tools; for example, Groundcover is now leading in observability from my side. I'm the only single DevOps in the world, so if I want to lead my company to use incident.io, it needs to be more friendly and easier to set up, with more integrations with Groundcover that would make it easy for me to integrate. Maybe more guides, something very short and easy to make a simple alert, and a more user-friendly UI, which could be less complicated. I know that incident.io is built for large companies with many teams and many shifts, many kinds of alerts, and many sections, but for a small company starting to use it, such as mine with only one person handling all the issues, we need something more manageable.
I would like to see incident.io improved in terms of maturity, as it is not a complete solution at the moment. It narrowly focuses solely on incident management and lacks the breadth of a platform such as PagerDuty, which has a high service catalog encompassing everything from asset management to change management. incident.io is not there yet. It's not so much of a feature request; it's about the niche they're working on. For it to develop further for enterprise-level customers, it needs to transition into more of a platform than just a solution. When it comes to pricing, I have seen a great ROI with incident.io after switching from PagerDuty. However, I must clarify that those ROIs were also met with PagerDuty, meaning it isn't extensive that we are observing. The MTTR trends are something that is sadly missing in incident.io, which we had with PagerDuty. Cost estimations are also lacking. If an incident occurs, for example, seeing high cardinality metrics in production leading to a jump in billing, those estimations can't be done in incident.io while they could be done in PagerDuty. Thus, it feels more of a downgrade for us, but again, every choice has its pros and cons. incident.io is cheaper, and we needed a more economical solution, as simple as that.
The AI features are quite expensive pricing-wise, and the pricing should be reduced. Apart from pricing, there are no other improvements needed for incident.io.
PagerDuty Operations Cloud and incident.io compete in the incident management sector, with PagerDuty Operations Cloud having a feature advantage and incident.io offering cost benefits.Features: PagerDuty Operations Cloud provides extensive automation, advanced alerting, and integrations with major IT systems. Incident.io offers streamlined collaboration, real-time updates, and intuitive interfaces for rapid incident resolution.Ease of Deployment and Customer Service: PagerDuty provides...
Incident.io can be improved with more integrations with leading observability tools; for example, Groundcover is now leading in observability from my side. I'm the only single DevOps in the world, so if I want to lead my company to use incident.io, it needs to be more friendly and easier to set up, with more integrations with Groundcover that would make it easy for me to integrate. Maybe more guides, something very short and easy to make a simple alert, and a more user-friendly UI, which could be less complicated. I know that incident.io is built for large companies with many teams and many shifts, many kinds of alerts, and many sections, but for a small company starting to use it, such as mine with only one person handling all the issues, we need something more manageable.
I would like to see incident.io improved in terms of maturity, as it is not a complete solution at the moment. It narrowly focuses solely on incident management and lacks the breadth of a platform such as PagerDuty, which has a high service catalog encompassing everything from asset management to change management. incident.io is not there yet. It's not so much of a feature request; it's about the niche they're working on. For it to develop further for enterprise-level customers, it needs to transition into more of a platform than just a solution. When it comes to pricing, I have seen a great ROI with incident.io after switching from PagerDuty. However, I must clarify that those ROIs were also met with PagerDuty, meaning it isn't extensive that we are observing. The MTTR trends are something that is sadly missing in incident.io, which we had with PagerDuty. Cost estimations are also lacking. If an incident occurs, for example, seeing high cardinality metrics in production leading to a jump in billing, those estimations can't be done in incident.io while they could be done in PagerDuty. Thus, it feels more of a downgrade for us, but again, every choice has its pros and cons. incident.io is cheaper, and we needed a more economical solution, as simple as that.
I do not think any improvement is required. incident.io is a good application.
The AI features are quite expensive pricing-wise, and the pricing should be reduced. Apart from pricing, there are no other improvements needed for incident.io.