nOps - Cloud Optimization Platform

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

The main problem it solves for me is understanding where AWS costs are actually coming from. When the total cost increases, it can be difficult to know what exactly caused it. With nOps I can break the costs down by service and quickly see which one is driving the increase. It also shows potential savings opportunities, which helps me understand where we should look first instead of checking everything manually.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

nOps simplifies cloud operations by solving cloud management issues and providing visibility into AWS infrastructure. It eases cloud management, excels in AWS cost optimization, and enhances resource visibility.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

nOps helps our devops team manage AWS costs and track servers across regions without being overwhelmed. Our leaders love seeing spending and resource utilization clearly. Its reports and automatic cost-saving features are quite good.

What do you like best about the product?

I like the future forecast it provides of the costs. It gets connected to cloud accounts quickly too without agents or major changes

What do you dislike about the product?

It does not have detailed tutorials and I am not very familiar with cloud billing or cost optimization

What problems is the product solving and how is that benefiting you?

It is assisting with expensive cloud based systems. We can track Spending trends and future costs.

What do you like best about the product?

There are very few automated commitment management platforms with nOps giving the best results and highest savings.

What do you dislike about the product?

Great team and very responsive support. Nothing to dislike.

What problems is the product solving and how is that benefiting you?

nOps provides automated commitment management for AWS, GCP, and Azure. Compared to competitors this vendor can save more.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

We regularly update our fleet of EC2 instances to stay aligned with the best price/performance instance types for our use cases. Knowing we can make these changes without disrupting our Reserved Instances and Savings Plans coverage gives us confidence that these fleet updates won’t jeopardize our cost savings.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

nOps solves AWS cost visibility and attribution across a multi-account, EKS-heavy estate. Before, most of our spend was effectively unattributable native billing tags left the majority of cost untagged, so we couldn't reliably say which app or team drove a change. nOps gives us cost broken down to the namespace, application, and container level, plus an idle "Excess Capacity" metric that flags reclaimable EKS capacity we couldn't see before. It also manages our Savings Plans and RIs, so commitment coverage is handled rather than guessed at.

My primary use case for nOps is automated AWS cost optimization, FinOps compliance, and infrastructure visibility. I use it to instantly surface underutilized resources and automate the management of spot instances and handle lifecycle commitment features like saving plans and reserved instances seamlessly.

In our cloud infrastructure setup, nOps helps us automate cost optimization as we host several high-throughput client platforms across multi-tier AWS organizations. We integrate nOps directly with our AWS cost and usage reports, CURs, and infrastructure event streams. A typical workflow involves nOps continuously scanning our products launched in the production environment, such as auto-scaling groups, containers, and clusters. If it detects over-provisioned compute power or idle RDS instances during off-peak hours, it triggers automated resizing recommendations or the scheduling of spot market instances to keep operational costs low.

nOps has positively impacted our organization by shifting our engineering culture from reactive cloud cost tracking to proactive cloud financial engineering. Instead of waiting for an unexpectedly high monthly cloud bill to arrive before investigating, our DevOps team gets automated alerts and continuous actionable insights to prune waste in real-time.

Since making this shift, we have seen a twenty to thirty percent reduction in the total AWS compute expenditure, which represents a significant win for us.

The standout feature nOps offers is ShareSave for automated commitment optimizations, the nOps dashboards, and its granular event-driven visibility into daily cloud cost spikes. It goes far deeper than native tools such as AWS Cost Explorer by correlating a cost surge directly with the exact infrastructure configuration changes or deployment events.

The most valuable capability for our daily work is AI-driven spot instances orchestration through nOps' ShareSave feature. Running enterprise web applications safely on spot instances requires incredible precision to prevent downtimes. When AWS reclaims the capacity, nOps automates the preemptive shifting of workloads across spot pools, which allows us to maximize compute discounts completely risk-free.

While the AWS integration is flawless and deeply mature, I believe the multi-cloud capabilities for platforms such as Microsoft Azure or Google Cloud Platform can sometimes feel a bit less comprehensive in comparison.

When dealing with highly complex custom enterprise billing agreements or custom AWS tiers, the dashboard calculations can occasionally require manual fine-tuning to perfectly reflect the customized billing structure. Streamlining the onboarding setup for non-standard enterprise discount configurations would make it a flawless out-of-the-box experience.

I have been using nOps for almost two years.

nOps earned its score because it delivers a good or exceptional return on investment and provides unparalleled visibility into complex AWS infrastructure. However, it misses a perfect score because multi-cloud feature parity is still catching up to its gold-standard AWS toolset.

My advice for others looking into using nOps is to start by setting up the read-only integration to run a baseline cost and architectural audit. Let the platform analyze your actual infrastructure using the usage patterns for a couple of weeks to surface immediate quick wins, such as orphaned EBS volumes or idle RDS instances before diving deeper into the automated spot or saving plans commitments. I have given this review a rating of eight out of ten.

Public Cloud

Amazon Web Services (AWS)

My main use case for nOps is cost savings.

A quick, specific example of how I use nOps for cost savings is through their automated cost savings feature. This involves automated management of savings plans, resizing of resources, identification of cost savings, and identifying cost savings areas in my day-to-day work.

The best feature nOps offers is the automated cost savings feature.

What makes the automated cost savings feature stand out for me compared to other solutions is that it is incredibly easy. nOps has been around for a while, they are trusted, they are recommended by the account managers, and they save a lot of money for many customers.

nOps has impacted my organization positively by helping our customers with cost optimization, cost savings, and easily identifying areas where we can help our customers save money when it comes to AWS.

nOps can be improved by having their account managers be more responsive and treat customers that are tail spend a little bit better than enterprise customers. I understand that smaller customers spend less money with nOps, but it still would be nice to be treated in a good manner with fast and prompt follow-up and response.

I have been using nOps for two years.

nOps is stable.

The scalability of nOps is incredibly easy.

The customer support is lacking but still pretty good.

Positive

I did not use a different solution before nOps.

nOps is deployed in my organization across all types of cloud environments and we have used it with multiple customers.

I did not evaluate other options before choosing nOps.

I have seen a return on investment. One customer saved 35 percent on their cloud bill, which is pretty significant. I do not have any other exact metrics right in front of me because this was a random observation, and I do not have specific numbers otherwise.

My experience with pricing, setup cost, and licensing is that it was very easy, and it was also brokered by us with the client. I did not purchase nOps through the AWS Marketplace.

I did not evaluate other options before choosing nOps.

My advice to others looking into using nOps is to build a strong relationship with your account manager. I gave nOps a review rating of 10.

Public Cloud

Amazon Web Services (AWS)