What I found most useful is the way Parny brings infrastructure signals and incident context together. In a factory environment, a technical interruption can affect more than a single system, so understanding which services or infrastructure components may be involved is important. Parny AI’s impact analysis and infrastructure visibility provide a more structured starting point than reviewing separate alerts one by one. Review collected by and hosted on G2.com.

The platform becomes more valuable as more infrastructure context is connected. Initial setup and agent deployment may require coordination with IT and security teams, especially in controlled production environments. Review collected by and hosted on G2.com.

I like that I can use it both when something is actively failing and when I want to look back at service health.

The uptime view, incident history and affected-service context are useful because they give more meaning to the alerts we already have. If there is a problem, I can understand the impact quickly. Later, I can also see whether the same kind of issue has happened before instead of starting from zero. Review collected by and hosted on G2.com.

Nothing major in my current use. More detailed historical reporting and comparisons between recurring incidents would be useful. Review collected by and hosted on G2.com.

I like that Parny AI does more than display alerts. Its root cause assessment and dependency mapping capabilities help explain how a problem in one technical component may affect other services. From a manufacturing perspective, this is useful because production processes often depend on multiple connected applications and infrastructure systems. Review collected by and hosted on G2.com.

The dependency view may need some validation and naming adjustments during the initial evaluation. Technical teams and operational teams may describe the same systems differently, so the structure should be reviewed together. Review collected by and hosted on G2.com.

Parny’s organizational separation by customer and the detailed information provided in incoming alarms offer us many advantages. When an alarm is triggered, it is much easier for us to analyze which service the alarm is related to, whether it is a critical situation, and the details provided in the description section. The newly added AI support also helps us analyze and evaluate alarms more effectively.

The maintenance mode feature is another important advantage. When teams are performing maintenance or other planned activities, putting the relevant system into maintenance mode helps prevent unnecessary alarm notifications. The notification we receive when a system is placed into maintenance mode also makes it easier to keep track of ongoing activities. This helps reduce alarm noise and, more importantly, reduces the risk of missing critical alarms from other customers.

Parny’s performance is generally stable and reliable. Alarms are delivered quickly and on time, and the system remains responsive even during periods of high alarm traffic. The web and mobile applications load quickly, allowing us to access alarm details and take action without significant delays. We have not experienced any major performance issues or noticeable slowdowns while using the platform.

In addition, AI support helps us analyze alarms, integrations can be implemented easily and quickly, and Parny’s web and mobile applications are user-friendly and easy to use. The customer-based organization makes alarm management and monitoring more structured, while detailed information such as the related service, severity, and description helps us identify the root cause of an issue more quickly. Overall, these features improve our workflow, reduce unnecessary effort, and allow us to respond to critical situations more efficiently. Review collected by and hosted on G2.com.

A little more development could be made on the mobile application side. Features such as setting and managing maintenance mode (MNT mode), which are available on the web application, could also be added to the mobile application for a more flexible user experience. Review collected by and hosted on G2.com.

We've been using Parny for our on-call and incident management, and the new ParnyAI features have honestly made a noticeable difference. When an alarm comes in, it provides useful context and suggestions that help us understand the issue much faster instead of manually checking multiple dashboards and logs. The AI Insights & Predictions page has also been great for identifying noisy alerts and spotting patterns we would have probably missed, making it much easier to fine-tune our alerting over time. DomainTree is another feature I use a lot because it gives a clear picture of how our resources are connected, which is especially helpful during incidents.

Overall, Parny has been easy to work with. Setting up integrations doesn't take much effort, and managing multiple teams and organizations from one place is really convenient. The Timeline page is also helpful during incidents since everyone can follow what happened and when. Compared to other on-call tools I've used, Parny feels simpler, more practical, and the AI features are something I actually find myself using every day rather than just being a nice extra. Review collected by and hosted on G2.com.

Parny has been great overall, and we are really happy with the platform and how it supports our daily operations. We are looking forward to exploring the new features and improvements as they continue to be released. Continuous development and new capabilities will make an already useful platform even better. Review collected by and hosted on G2.com.

What I liked most is that database-related findings do not remain isolated in a separate monitoring screen. Parny DB Agent can surface slow or unusual query behavior and send it into the same alert and incident workflow used by the rest of the platform.

This makes it easier to look at a database issue as part of a wider operational problem rather than treating it as a standalone technical warning. Review collected by and hosted on G2.com.

Nothing stood out as a major concern during my evaluation. I would need more time in a live environment to comment in greater detail. Review collected by and hosted on G2.com.

As an SRE, I am usually cautious about tools that put an AI-generated summary on top of a noisy alert stream and call it root cause analysis.

What I liked about Parny is the hybrid approach. It first uses alert details, service relationships, and infrastructure failure signals to determine which events are likely to belong to the same incident. The AI analysis then works on top of that structured context.

This matters because connected services are not automatically part of the same failure. Parny’s approach gives the root cause assessment, affected services, and recommended actions a more technically credible foundation. Review collected by and hosted on G2.com.

At this stage, I have not identified a clear area of dissatisfaction. The overall experience has been straightforward. Review collected by and hosted on G2.com.

What stood out to me is that Parny does not simply send a group of alerts to an AI model and generate a generic explanation. It first uses infrastructure relationships and alert context to determine which signals are likely to belong to the same incident. This makes the root cause assessment more useful because the analysis begins with a structured incident rather than an unfiltered alert list. For complex environments, that difference matters. Review collected by and hosted on G2.com.

The analysis becomes more detailed when the platform has access to a complete infrastructure map. The alert-only experience is still useful, but connecting the InfraMap Agent provides significantly more context. Review collected by and hosted on G2.com.

I work in industrial automation, so I tend to look at technical systems in terms of continuity, dependencies, and how quickly a problem can be isolated. I explored Parny from that perspective.

What I liked most is that companies do not need to replace the monitoring tools they already use. Parny takes existing alerts and adds useful context around them, such as what may have failed, what could be affected, and where the investigation should begin. The overall approach felt practical without being unnecessarily complex. Review collected by and hosted on G2.com.

So far, I have not encountered any major issues. The platform was straightforward to explore, and my overall experience was positive. Since my evaluation was limited to an initial review, I would need more time in a live environment to comment on any deeper limitations. Review collected by and hosted on G2.com.

I looked into Parny on my own because I was curious about how AIOps products make incident data easier to understand. As a business analyst, I am not the person who directly manages infrastructure, so I found it helpful that Parny does not only show alerts. It also explains the possible root cause, affected services, impact, and suggested next steps in the same view.

I was able to understand the general incident flow without needing deep DevOps knowledge. That was the part that impressed me most. Review collected by and hosted on G2.com.

Some of the infrastructure and AIOps terms were unfamiliar to me at first. A short onboarding flow or more examples for business users would make the first experience easier.

I only explored the product individually, so I cannot comment on how it performs in a full production environment. Review collected by and hosted on G2.com.