nOps Reviews & Product Details

What I like most is that it makes AWS costs much easier to understand. I can quickly see where the money is going and which service is costing the most. For example, when I saw the costs going up, I could break it down and see EC2 was the biggest part. I also like that it shows possible savings, so you don't only see the problem but also where you can potentially reduce the cost. Review collected by and hosted on G2.com.

At the beginning there is quite a lot of information on the screen, so it took me some time to understand where to look and which data is most important. Once you spend some time with it, it becomes easier, but I think the first experience could be a little more simple and guided. Review collected by and hosted on G2.com.

I really like the way nOps presents data. The reporting is quite nice, with clear visual representations of each cost and idle resources. The automatic cost-saving feature is pretty good too. Their support is quite nice, and they introduce features rapidly, making it feel like we've invested in the right place. The initial setup was nice as well, just connecting the account, and although data fetching can be a bit long, it was manageable. Review collected by and hosted on G2.com.

The overwhelming filters sometimes confuse us as there are so many in one place. They could improve the user experience by providing a design that considers the engineering perspective better. It seems like the design team might not be standing in the engineering shoes. They probably need more experienced personnel in that area. Review collected by and hosted on G2.com.

nOps helps us manage AWS Reserved Instances (RIs) and Savings Plans (SPs), and it can adapt as our AWS resource usage patterns change. With nOps, we avoid getting locked in for 1–3 years the way we might with self-deploying AWS RIs and/or SPs. Review collected by and hosted on G2.com.

I’m encouraged by the progress of the AI tools, though they’ll be even more helpful as they continue to improve. The integrations with Claude and ChatGPT are also encouraging. Review collected by and hosted on G2.com.

The best thing about nOps is that it helped our company bring costs down by more than 20% through consistent pattern analysis. With central monitoring, it also made our decision-makers’ jobs a lot easier. For a self-financed startup, it has helped us scale while still keeping our costs optimized. Review collected by and hosted on G2.com.

It feels a little skewed toward AWS integration. Since we use all the major cloud providers, having similar support features across the others would definitely improve overall usability. Review collected by and hosted on G2.com.

I like that nOps delivers continuous workload rightsizing at the container level and node-level optimization across Spot, On-Demand, and committed capacity. It helps reduce cloud infrastructure costs and continuously scans accounts to prioritize savings actions, like removing idle snapshots or rightsizing underutilized instances based on implementation effort and risk. It's also very easy to switch to nOps, which I would recommend to everyone. Review collected by and hosted on G2.com.

The AI breakdowns can be more detailed. It would also be great if the tool could handle costing and tagging of resources. Review collected by and hosted on G2.com.

They help us understand the cost loopholes in our Infra and provide us with valuable info saving us thousands of dollars. Also they show cost visibility of our AI models in bedrock, which is a cherry on top :) Review collected by and hosted on G2.com.

I believe it is heavily tailored towards AWS, if i want deep and equal automations across GCP, it lacks that. But the data is enough for me to deep dive in GCP myself, so overall i am happy Review collected by and hosted on G2.com.

Its user-friendly interface and the visibility it provides into cloud infrastructure and costs. It makes it easier to monitor resources, identify potential cost-saving opportunities, and understand overall cloud usage. I also appreciate the automation capabilities, which help reduce manual effort and make cloud management more efficient. Review collected by and hosted on G2.com.

One area that could be improved is the learning curve for some of the more advanced features. It can take some time to understand all the available options and configurations. More detailed documentation, guided workflows, and simpler navigation for complex tasks would make the overall experience even better. Review collected by and hosted on G2.com.

I like nOps for its easy cost tracking and the optimization insights it provides. It really makes AWS management much easier. The ability to monitor AWS infrastructure effectively and keep track of cloud costs is something I find quite valuable. Also, nOps offers better cost visibility and optimization compared to what we used before, which led us to switch from AWS Cost Explorer. Review collected by and hosted on G2.com.

Resource-level insights could be more detailed. For example, showing CPU, memory, and cost together for EC2 instances would make it easier to identify underutilized resources. Review collected by and hosted on G2.com.

I like how nOps simplifies cloud management, making it much easier for me to handle. It also helps me with AWS cost optimization and provides great resource visibility, which are really valuable features for me. Additionally, the initial setup was pretty easy, which made getting started with nOps a breeze. Review collected by and hosted on G2.com.

I find the learning curve for some of the advanced features in nOps challenging. It could be improved with step-by-step tutorials and guided walkthroughs of the features. Review collected by and hosted on G2.com.

The developer API combined with nOps' container-level cost visibility. It breaks EKS spend all the way down to per-namespace and per-application cost (the Cluster Application Cost view), which native AWS billing tags never gave us, and it surfaces idle "Excess Capacity" we'd otherwise never have caught. Because it's all exposed through a clean API, we pulled org-wide cost, per-app breakdowns, and Savings Plan/RI coverage straight into our own automated weekly and monthly reports. The clincher: nOps' figures reconcile to the dollar against AWS Cost Explorer, so we treat it as our source of truth rather than just another dashboard telling a different story. Review collected by and hosted on G2.com.

The main friction was the developer API's discoverability. The endpoint paths aren't clearly documented — they're spread across a few different prefixes and the OpenAPI/Swagger spec sits behind a session login, so we spent time probing to find the right cost/usage endpoints. A few things we wanted (like the org-level savings summary) are only exposed in the UI rather than via the API key, and generating the API key itself — with the RSA signature-verification step — was more involved than expected. None of it was a blocker: once we found the right endpoints everything worked and reconciled cleanly. But clearer API reference docs and fuller API-to-UI parity would make integrations a lot faster. Review collected by and hosted on G2.com.