Sold by: incident.io
AWS Free Tier
Incident management for modern engineering teams, bringing on-call scheduling, incident response, and status pages into one platform. Trusted by 1500+ teams, including Netflix, Etsy, Intercom, and Skyscanner.
4.8
Overview
incident.io is an all-in-one incident management platform built for modern engineering teams. It brings on-call scheduling, incident response, communications, and follow-up work into a single system of record, helping teams run incidents clearly, consistently, and with less manual coordination.
With incident.io, teams can:
- Declare and coordinate incidents quickly with clear severity, ownership, and context from the start
- Assign roles and run response with less chaos, so responders know who is leading, investigating, and escalating
- Keep stakeholders aligned with structured updates and status pages connected directly to incident activity
- Automatically capture a real-time incident timeline as decisions and actions happen
- Track follow-ups and learn from incidents over time with reporting and trends
incident.io integrates with the tools engineering teams already rely on, including Slack, Microsoft Teams, Jira, PagerDuty, Datadog, and cloud infrastructure providers. It is designed to support both fast-moving incidents and large-scale outages, while scaling across teams and organizations.
Whether you're responding to day-to-day incidents or managing critical outages, incident.io provides a consistent system of record for incident response - from alert to resolution and beyond.
Highlights
- Centralize incident response, on-call, communications, and follow-up work in one platform so incidents run consistently every time.
- Coordinate responders in Slack or Microsoft Teams with clear roles, ownership, and structured updates that keep stakeholders aligned.
- Integrate with the tools you already run on AWS like Jira, Linear and Datadog, while keeping a complete audit-ready incident timeline.
Details
Sold by
Delivery method
Deployed on AWS
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Trust Center
Access real-time vendor security and compliance information through their Trust Center powered by Drata or Vanta. Review certifications and security standards before purchase.
Buyer guide
Gain valuable insights from real users who purchased this product, powered by PeerSpot.
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
This product is available free of charge. Free subscriptions have no end date and may be canceled any time.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimensions summary
This listing offers one pricing option: the Basic Plan. You pay per user each month. Pricing scales with the number of users you add, so your cost grows as your team grows. There are no separate tiers or add-ons to choose from on the Marketplace. The Basic Plan gives you incident management tools your team runs directly in your messaging workspace.
Top-of-mind questions for buyers
You pay for each person who uses the Basic Plan in your messaging workspace. Every active user account counts as one unit. As you add or remove people from your team, the number of billed users adjusts to match.
The Basic Plan bills per user each month, so your total moves with your headcount. Adding users raises your monthly charge; removing them lowers it. There are no tiers to cross, so the per-user rate stays the same regardless of team size.
The Basic Plan includes incident response run directly in your messaging workspace. You get single-team on-call, a status page, and essential incident automation. These tools help your team declare, coordinate, and communicate during incidents without leaving the chat platform.
incident.io
Helpful?
Vendor refund policy
All fees are non-cancellable and non-refundable except as required by law.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Support
Vendor support
We provide multiple resources for customers to get help and support with our product. Users can browse our help centre (help.incident.io), join our community (incident.io/community), or get in touch via email (support@incident.io ).
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Updated weekly
By incident.io
By Squadcast Inc.
Sentiment is AI generated from actual customer reviews on AWS and G2
Functionality
Ease of use
Customer service
Cost effectiveness
Positive reviews
Mixed reviews
Negative reviews
AI generated from product descriptions
Incident Declaration and Severity Management
Ability to declare and coordinate incidents with clear severity levels, ownership assignment, and contextual information from initiation.
Role-Based Response Coordination
Support for assigning specific roles to responders with defined responsibilities for leading, investigating, and escalating during incident response.
Real-Time Incident Timeline Capture
Automatic capture and maintenance of incident timelines documenting decisions and actions as they occur, with audit-ready records.
Multi-Platform Integration
Integration with third-party tools including Slack, Microsoft Teams, Jira, Linear, PagerDuty, Datadog, and cloud infrastructure providers.
On-Call Scheduling and Status Page Management
Built-in on-call scheduling capabilities with connected status pages that provide structured updates to stakeholders based on incident activity.
Incident Management
Unified platform for automating and managing incident response processes with integrated workflows
On-Call Alerting
Automated on-call escalation and alert routing capabilities for incident response
Service Level Objective Tracking
SLO and error budget tracking functionality for monitoring service reliability metrics
SRE Workflow Automation
Site Reliability Engineering workflows integrated within a single platform for continuous improvement
Incident Learning and Analytics
Continuous learning from past incidents to refine service expectations and improve response processes
Incident Channel Automation
Automated creation of dedicated incident channels, Zoom rooms, and Jira tickets during incident response
Workflow Customization Engine
Workflow builder enabling customization of incident response processes with conditional logic based on severity levels and team assignments
Multi-Platform Integration
40+ integrations with incident management tools including PagerDuty, Opsgenie, Jira, GitHub, Datadog, Zendesk, Terraform, and custom API support
Automated Postmortem Generation
Automated postmortem timeline generation with action item tracking and support for writing postmortems in Confluence and Google Docs
Incident Metrics Tracking
Tracking and visualization of incident metrics including Mean Time To Resolution (MTTR) and incident cause analysis
Standard contract
No
No
No
Customer reviews
Anonymous
Comprehensive Security Incident Management, Slight Complexity
Reviewed on Aug 27, 2026
Review provided by G2
What do you like best about the product?
I like how incident.io provides a unified platform that records all the triage information we need and assigns incident response leads. Its excellent integration with Slack allows us to send messages in real time, summarize incidents, and keep track of them over time. I appreciate its AI capability to summarize things, which saves time for incident response personnel. They can type in Slack what's happening, and incident.io fills in the rest using meeting recordings and other means, making it easy for new members to get up to speed quickly. It's a really good way of collecting and summarizing all the information generated during an incident, making it accessible for people who are just joining or when looking back on it.
What do you dislike about the product?
I find that the platform has so many features and capabilities that it's a bit overwhelming. It would be better if there was a way to slim some things down, or have a more simple configuration for certain aspects, because it's a lot to continuously maintain. They're always releasing new features, which is great, but it starts to sprawl a little. It would be helpful if there were setup templates to avoid going through all the complicated settings. Also, the pricing is quite tricky; it's expensive and depends on the size of the business.
What problems is the product solving and how is that benefiting you?
I use incident.io for responding to security incidents. It provides a unified platform to record triage information, assign leads, and integrates with Slack for real-time updates. Its AI summarizes incidents, saving time and helping new members catch up quickly with current developments and affected areas.
reviewer2888304
Automation has saved incident creation time and supports fast AI-driven postmortem reports
Reviewed on Aug 16, 2026
Review provided by PeerSpot
What is our primary use case?
My main use case for incident.io is for incident creation, its postmortem, and the on-call feature of incident.io.
What is most valuable?
The best feature that incident.io offers is postmortem creation automatically using the AI which reads the data from the Slack channel.
The AI-driven postmortem creation helps my team because it saves time.
incident.io has positively impacted my organization as it helps to save time for incident creation, allowing people to create incidents via the Slack channel, and multiple teams have access to create incidents for P3 and P4 issues.
Since using incident.io, my team has saved at least 15 minutes, specifically 10 to 15 minutes.
What needs improvement?
incident.io can be improved by having more features in the AI of incident.io.
The AI feature that would be most helpful would involve more capability in finding the root cause of an issue based on the existing incident reports.
For how long have I used the solution?
I have been using incident.io for one year.
What do I think about the stability of the solution?
incident.io is stable.
What do I think about the scalability of the solution?
The scalability of incident.io is scalable, and we have multiple incident data stored in incident.io.
How are customer service and support?
The customer support is good.
Which solution did I use previously and why did I switch?
We previously used PagerDuty, but incident.io's on-call feature is much cheaper than PagerDuty.
What was our ROI?
I have seen a return on investment with incident.io, as time-wise, you can save at least 10 minutes for creating an incident.
Which other solutions did I evaluate?
Only incident.io was evaluated before we chose it.
What other advice do I have?
My advice to others looking into using incident.io is to create incidents via the Slack channel and use the postmortem feature of incident.io where it automatically writes the report of the incident. I would rate this product 9 out of 10.
reviewer2888130
Effective incident workflows have improved on-call response and guided post-incident reviews
Reviewed on Aug 13, 2026
Review provided by PeerSpot
What is our primary use case?
The main purpose of incident.io in my work is configuring the on-call team's response to incidents triggered by alerts.
A specific example of how incident.io helped my on-call team respond quickly to an incident is that we set up a convenient schedule for responding to incidents. Incidents are tied to the criticality of alerts. We were able to conveniently build the on-call schedule thanks to the built-in functionality of incident.io and we successfully continue working with it.
Regarding the main use of incident.io, I would add that it involves running post-mortems, convenient automation of workflows tied to incidents, and creating tasks in Jira.
What is most valuable?
The incident.io features I consider the most useful for my work are incident.io's reaction to alerts and calling the on-call engineer, and the order of support and guidance for the on-call engineer during an incident. Additionally, it has good integration with Slack.
The Slack integration helps my team respond to incidents by allowing incident.io to create channels in Slack for an incident. It invites the right people into this channel during the incident, and incident.io guides the on-call engineer through the workflow. It highlights what needs to be done and gives reminders during the work. When closing an incident via Slack, we redirect to conducting a post-mortem.
Incident.io has positively affected my organization by closing the issue of incident response, setting up on-call schedules, and calling on-call staff. This area was covered thanks to it.
What needs improvement?
I believe everything is functioning well in incident.io, so I do not see anything that could be improved.
If I had the opportunity to add or change something in incident.io, I would choose to enhance the flexibility, customization, and convenience that it already offers.
For how long have I used the solution?
I have been using incident.io for about a year and a half.
What do I think about the stability of the solution?
incident.io is stable in operation, and there have been no outages; everything works well.
What do I think about the scalability of the solution?
I rate the scalability of incident.io as easy because it is simple to expand the use of the tool as the company grows or the number of incidents increases, though it is a paid subscription that extends the capabilities.
How are customer service and support?
I would rate the work of incident.io's support service as needing improvement since we contacted them via a Slack channel, but their response leaves something to be desired. I would like it to be faster.
I would give the support service a rating of seven.
Which solution did I use previously and why did I switch?
I have not used any other incident management solution before.
What was our ROI?
We have not measured the return on investment from using incident.io, so I cannot provide details on time savings or resource savings.
What's my experience with pricing, setup cost, and licensing?
My experience with incident.io's pricing, implementation cost, and licensing is still in progress, so I cannot provide an answer yet.
Which other solutions did I evaluate?
Before choosing incident.io, I only considered incident.io and did not evaluate any other solutions.
What other advice do I have?
My advice to those who are just considering implementing incident.io is to use the demo version and click through the UI functionality. I would rate this review as an eight.
Anonymous
Flexible, User-Friendly Solution for SRE Challenges
Reviewed on Aug 04, 2026
Review provided by G2
What do you like best about the product?
I like the flexibility and ease of use of incident.io. The alerting and AI on-call completion features are particularly valuable to me.
What do you dislike about the product?
Not alot to dislike on my end
What problems is the product solving and how is that benefiting you?
I use incident.io for SRE related issues. I like the flexibility and ease of use. The alerting and AI oncall completion features are valuable.
Marketing and Advertising
Highly Configurable Platform with Strong Slack/Teams Integration and AI
Reviewed on Aug 04, 2026
Review provided by G2
What do you like best about the product?
The services that form the core of the platform are highly configurable, which lets you set things up in a very specific way. It performs well with Teams integration, and especially with Slack. That said, the menu navigation can be a bit tricky at times, with certain settings tucked away in places you wouldn’t expect.
The site itself performs quickly, occasionally you are waiting for a few seconds if there's a lot to load - but this isn't often.
In contrast, the incident and alert pages themselves are laid out very sensibly, so everything is easy to find and feels intuitive. The support we received during onboarding was excellent as well; whenever issues came up, they were identified quickly and resolved ASAP, usually within 24 hours.
The AI features are also very useful. The scribe provides notes from calls, and the AI then pulls from those notes, along with Teams/Slack chats, to put together post-mortems for you. Like the rest of the platform, it’s extremely configurable—right down to the prompts the AI uses for specific tasks, and even the individual sections of the report.
The site itself performs quickly, occasionally you are waiting for a few seconds if there's a lot to load - but this isn't often.
In contrast, the incident and alert pages themselves are laid out very sensibly, so everything is easy to find and feels intuitive. The support we received during onboarding was excellent as well; whenever issues came up, they were identified quickly and resolved ASAP, usually within 24 hours.
The AI features are also very useful. The scribe provides notes from calls, and the AI then pulls from those notes, along with Teams/Slack chats, to put together post-mortems for you. Like the rest of the platform, it’s extremely configurable—right down to the prompts the AI uses for specific tasks, and even the individual sections of the report.
What do you dislike about the product?
While the services are highly configurable, that flexibility also makes initial setup more complicated. It isn’t always clear how services should be configured to work effectively across the system—for example, how they should appear and behave on status pages. A tutorial, or clearer in-platform guidance on what’s required, would be very helpful.
The status pages themselves also feel a bit too rigid. The layout isn’t really changeable beyond switching between dark and light mode. Even then, it’s just a manual toggle: there’s no option to respect the user’s OS setting, or to let each user choose their own preference. That leaves you having to pick between forcing people who struggle with light pages to use them, or doing the opposite.
Finally, status pages only support automation for the single-page variant. There’s currently no automation available for the sub-page variant (for example, for regions), although this is under review and may change in the future.
The status pages themselves also feel a bit too rigid. The layout isn’t really changeable beyond switching between dark and light mode. Even then, it’s just a manual toggle: there’s no option to respect the user’s OS setting, or to let each user choose their own preference. That leaves you having to pick between forcing people who struggle with light pages to use them, or doing the opposite.
Finally, status pages only support automation for the single-page variant. There’s currently no automation available for the sub-page variant (for example, for regions), although this is under review and may change in the future.
What problems is the product solving and how is that benefiting you?
They’ve streamlined what used to be a very manual workflow for us. We previously had to raise incidents by hand and keep track of everything ourselves, logging the investigation as we went. Now we can rely on incident.io’s scribe and integrations to capture those notes for us, which lets us pre-generate incident reports and status updates. As a result, we can focus much more on actually resolving the issue and spend far less time on the related admin work.