![Verified User in Oil & Energy](/assets/icons/anonymous-avatar-purple-4ae1032bdb50ee5682003170c8184aee790d25958bd397abbd384ba52c596a7b.svg "Verified User in Oil & Energy")
AO

Verified User in Oil & Energy

Mid-Market (51-1000 emp.)

7/2/2026

"Our source of truth for AWS cost - down to the container"

4.5/5

What do you like best about nOps?

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.

What do you dislike about nOps?

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.

What problems is nOps 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. Review collected by and hosted on G2.com.

Show More

Response from Ghazaleh Davoudzadeh of nOps

[Editedit](https://www.g2.com/survey_responses/nops-review-13059569/official_response/edit)

Thank you for your detailed feedback! We're thrilled that nOps has become your source of truth for AWS cost visibility. We also appreciate your feedback on our API experience and documentation—it's invaluable as we continue to improve.

Validated ReviewerSource: Organic

See what 132 reviewers think of nOps

4.8 out of 5 · Verified reviews from real users

[
Read all reviews
](https://www.g2.com/products/nops/reviews)