nOps Reviews

My main use case for nOps is managing AWS savings plans, and it also optimizes our Kubernetes infrastructure to reduce the number of EC2 instances we need to run.

I find it to be a valuable cost-savings tool. Its best features include several things: first, it is hands-off, so I can set it and forget it. I get it set up, and it manages AWS savings plans on my behalf. This frees my team up to work on more valuable work without losing out on valuable discounts.

It also provides a dashboard with more detailed insights into cost and AWS cloud costs than what comes out of the box with AWS Cost Explorer.

Third, the nOps Kubernetes agent automatically resizes pods based on usage, which allows us to run significantly fewer EC2 instances than we would otherwise. nOps has positively impacted my organization by saving both time and money.

I do not think there are any improvements needed; we are overall happy with the product. nOps does the job we need just fine.

I have been using nOps for about three years.

nOps is stable.

Its scalability is good; it has scaled to meet our needs.

The nOps team has been a pleasure to work with; they are quick with their response and always available to help out. My customer support experience has been excellent; I have had positive experiences.

Positive

We did not previously use a different solution.

It was easy to deploy nOps in my environment. My experience with the configuration process was straightforward; nothing tricky occurred.

nOps integrates well with other AWS services I use, though it integrates as a cost-savings and reporting tool only; it integrates very well at what it does.

My experience with the procurement process was easy; it sets up right through the AWS Marketplace, and it bills back automatically based on usage.

I have seen a return on investment; I save roughly $2,000 a month in money saved, and I have saved time as well.

The metering and billing experience is fair; they charge based on a percentage of what we save, so in any scenario where we pay them, we are already saving money. My experience with pricing, setup cost, and licensing was both fair and transparent.

I evaluated other options before choosing nOps, but I cannot remember which ones; it was years ago.

My advice for others looking into using nOps is to use it. I give this review a rating of 5.

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.

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.

My use case was AWS cost optimization.

nOps smoothly integrated with our AWS infrastructure and achieved significant savings without much intervention from our internal team. This allowed the team to focus on our priorities, while the nOps platform takes care of Spot Instances, Reserved Instances, and Savings Plans.

Smooth integration and the minimal effort needed to implement and maintain the system is the greatest value for us. We are able to achieve forecasted savings without the need to spend much time within the system.

The system works as expected, within the limitations of AWS itself. They just refreshed the UI and added even more options to the product, but for our use case, we are fine.

From the features, I would like to see RDS RIs and maybe better visibility on how the engine is deciding whether to use spot or on demand, to replace the instance or not

I have been using the solution for one year.

We managed cost optimization internally, but the next big switch was to implement Spot Instances. Instead of reinventing the wheel and going through all the starter hurdles, we asked nOps for help, and this turned out to be a good decision.

I believe the pricing is fair.

We did evaluate some other options, but the nOps option was very transparent, provided guarantees, and the projections looked good. We were also impressed with the technical approach and the way they designed it to leverage native AWS mechanisms to provide any possible failure recovery, so we feel very safe using it.

We thought about implementing Spot internally, but with the ease of implementation through nOps and the pricing, it would probably end up costing more than using the platform.

I use the solution for reporting, cost allocation, optimization recommendations, anomaly detection, and AI prompts.

The solution provides actionable reporting and cost-saving recommendations. It also includes EKS performance monitoring and optimization recommendations.

Additionally, it offers a commitment management platform that helps manage RIs to cover fluctuating usage.

The customized cost allocation mechanism helps break down costs into service, team, and financial department levels, driving accountability to resource owners.

I suggest improving the heat map capability with the option to use showback values as the x and y-axis. It would be helpful for creating Excel datasets, for example, to show cost grouped by service, service subtype, and operation in one dataset.

I have used the solution for 1 year.

I previously used Harness CCM and haven't switched so far.

The pricing is about average in the market.

I considered alternate solutions such as Apptio, CloudZero, and Lucidity.