My use case was AWS cost optimization.
External reviews
External reviews are not included in the AWS star rating for the product.
Actionable cost savings, with integrated cost saving automation
Node selection automation - Allowing nOps to Choose the right cost/performance balanced nodes.
Future - Container right sizing, for optimizing container and EKS efficiency.
Knowledgable and Trustworthy
Smoothly integrated with our AWS infrastructure and achieved significant savings
What is our primary use case?
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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
For how long have I used the solution?
I have been using the solution for one year.
Which solution did I use previously and why did I switch?
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.
What's my experience with pricing, setup cost, and licensing?
I believe the pricing is fair.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Excellent cost saving
Amazing Support
Great partner providing significant savings and guidance
The time the nOps team spend with us on a regular basis, has helped us save thousands of dollars.
I will work with nOps any time I am in a complex AWS environment are the team and the product are great.
No risk cost savings and great support
Strong support and finOps Solution
nOps
Overall, I highly recommend nOps as a FinOps partner for organizations looking to optimize their AWS expenditures.
Strong support and finOps Solution
I have been using nOps Compute Co-Pilot for several months, and it has significantly optimized our AWS EC2 costs. The platform's ability to continuously manage, scale, and optimize our compute resources ensures we're always getting the best deals. One standout feature is their 100% commitment utilization guarantee, where they provide credits for any unused Reserved Instances (RIs) they've recommended, adding an extra layer of financial assurance.
nOps
However, it's worth noting that some of the more advanced reporting features are part of an additional service. Without subscribing to this, the reporting capabilities can feel limited. Despite this, the core functionalities offer substantial value.
Overall, I highly recommend nOps as a FinOps partner for organizations looking to optimize their AWS expenditures.
I wanted to like them, but poor security
The product idea is great and I was looking forward to working with them, but the IAM permissions they require are far too permissive and they wouldn't work with me to come up with a least-privilege permission set. They are violating the AWS Well Architected Framework recommendations. They want you to add the ReadOnlyAccess policy (which is too permissive) and then add explicit Denies to counteract the permissiveness. This is not a good approach as ReadOnlyAccess is managed by AWS and changes occasionally as new products and features are released. If you don't actively monitor this, you will end up inadvertently give nOps too much access to your accounts. nOps should fix this by issuing an IAM policy that has explicit grants for all the permissions it needs rather. This is necessary in order to be taken seriously given how much access nOps needs on an account.