nOps

Name: nOps
Brand: nOps

nOps provides automated cloud cost optimization and comprehensive visibility solutions for AWS, GCP, and Azure.

Est 2017|Valuation $88.9M|Raised $40.1M|42 Ref Customers

LinkedIn 35K|Web traffic 13K|FTEs 172|HQ San Francisco, California, US

MarketsCloud Management & FinOps Cloud Cost Management

Published Oct 15, 2026

01Common complaints

- Organizations that cannot tolerate broad IAM permissions or cannot reach agreement on least-privilege access; at least one customer rejected nOps on this basis. - Organizations that require best-in-class multi-cloud coverage today (AWS + Azure + GCP) with equal depth; reviewer feedback suggests an AWS focus. - Organizations that require near-real-time cost data for rapid feedback loops; CUR-based pipelines can introduce approximately 24-hour lag. - Organizations with highly fragile workloads where instance mis-sizing or aggressive automated changes are unacceptable unless strict approvals/guardrails are in place. - Organizations that primarily need Kubernetes optimization with transparent, usage-based pricing and minimal emphasis on AWS commitments; Kubernetes-focused platforms (e.g., CAST AI) may be simpler. - Organizations with mature internal FinOps and tooling where only incremental improvements are required; ROI may be weaker.

Disqualifiers / poor fit signals

Organizations requiring strict least-privilege IAM with limited ability to negotiate permissions.
Teams needing full multi-cloud parity (AWS + Azure + GCP) with equal depth.
Very small AWS spend where vendor fees likely outweigh realistic savings.

Issues and limitations indicated by reviews

- IAM permissions perceived as overly permissive; least-privilege negotiation issues have been reported. - Multi-account IAM role work can be cumbersome. - Automation can be aggressive in some cases, with reported mis-sizing incidents. - Data latency: cost reporting can lag by about 24 hours due to CUR timing. - AWS-centric limitations: some users seek GCP/Azure coverage. - Reporting: advanced reporting may be an add-on; base reporting may feel limited to some buyers.

Vendor-documented constraints

nOps support SLA is documented (help desk hours, severity handling). Note the off-hours process for Severity 1 incidents requires contacting a designated CSM.

02Why they buy

Reported by customers (not just vendor claims)

Some customers report measurable savings (for example, several thousand dollars per month) and reduced manual effort.
Customer reviews frequently mention proactive support and engagement.

Differentiation claims to validate

Vendor-stated guarantees or credits related to commitment utilization should be validated in contract terms and exclusions.
Karpenter compatibility and Spot orchestration are emphasized for Kubernetes-heavy AWS environments; procurement teams should verify operational controls and failure modes.

Areas where competitors may have advantages

More transparent published pricing and simpler onboarding in some competitors.
Multi-cloud Kubernetes optimization depth (CAST AI).
Governance-as-code and multi-cloud allocation breadth (Harness).

03Field reports

Review platform snapshots

G2: very highly rated on G2.
Capterra: well rated on Capterra.
AWS Marketplace: majority positive ratings with a small number of lower ratings noted.

Direct quotes (positive)

From G2: - “We’ve had nOps for almost two years, and it instantly delivered meaningful monthly savings… It saves you money now.” (Director of Engineering). - “They are very responsive and always willing to help no matter what issues arise.” From Capterra: - “nOps provided me with detailed data on our workloads’ consumption of AWS services and highlighted all possible savings at once.” - “Using nOps to automatically stop and start instances helped a lot… able to cease idle EC2 instances without requiring my interference.” From AWS Marketplace reviews: - “Thanks to nOps, we are now saving substantial amounts in AWS costs each month.”

Direct quotes (negative / critical)

From AWS Marketplace reviews: - “…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 want you to add the ReadOnlyAccess policy… and then add explicit Denies… ReadOnlyAccess is managed by AWS and changes occasionally.” From Capterra: - “I had to come and modify IAM roles for each account, which was quite cumbersome in a multi-account scenario.” - “…may be costly for small organisation.” From G2: - “There have been bumps – a few mis-sized instances, or heavy handed automations.” - “It’s behind AWS data by about a day due to having to wait for the CUR report.”

Common themes: why customers choose nOps

Across platforms, common drivers cited by customers include:

Reported savings without building extensive internal tooling.
Centralized AWS Organization visibility and recommendations.
Commitment (RI/SP) management and reduction of manual toil.
Regular human support and check-ins cited by multiple reviewers.

Common themes: why customers struggle or may churn

Most credible churn-risk signals from the reviewed feedback:

Security/IAM friction (least-privilege concerns, setup burden across accounts).
Automation trust (mis-sizing or aggressive actions can create perceived operational risk).
Reporting depth behind paywall (advanced reporting as an additional service).
AWS-only limitations (some reviewers want multi-cloud parity).

Consulting partner (partner use case)

- A vendor case study describes a consulting partner using nOps to perform AWS Well-Architected Reviews, leveraging partner portal features (white labeling, custom questions, encryption, versioning) and automated discovery of AWS architecture. - Claimed benefit: faster, more comprehensive reviews than manual surveys; identifies cost/security gaps across pillars. Critical evaluation: The case study is vendor-authored; it emphasizes benefits but provides limited quantitative methodology (baseline vs. after, time saved measured how, error rates). Treat as directional evidence of capability rather than independently validated ROI.

Standards-focused organization

A vendor case study highlights Business Contexts for pseudo-tagging/showback, hourly cost breakdowns, amortization, and an assessment tool aligned to architecture best practices.

Critical evaluation: Again, vendor-authored and light on independently audited metrics; useful for understanding which features are pitched as differentiators (allocation/showback and assessments).

Vendor/press metrics worth validating

Vendor marketing materials include high savings claims and utilization guarantees. These are high-impact statements but are not consistently backed by transparent methodology in the materials reviewed. Procurement teams should request:

definitions of qualifying workloads
baseline methodology
savings calculation methodology (gross vs. net of fees)
precise contract terms for any guarantees or credits

04Best fit

Company size

Best fit: mid-market and enterprise organizations with meaningful AWS spend where vendor fees are justified.
Potential fit for smaller organizations: may be appropriate if AWS spend is meaningful and the team lacks FinOps expertise, though some reviewers note it can be costly for very small organizations.

Industries

Seen in reviews/case studies and likely fit:

SaaS/tech, IT services, telecom, and organizations with steady compute spend.
Regulated industries can be a fit if IAM/security concerns are addressed (request SOC 2 report and permission scoping).

Roles/personas

Decision makers: VP Engineering, CTO, Head of Infrastructure/Platform, FinOps lead, Cloud Center of Excellence.
End users: Cloud engineers, DevOps/SRE, Finance/FinOps analysts.

Pain points addressed

Difficulty managing RI/SP/Spot commitments efficiently.
Inadequate cost allocation and accountability across teams.
Need for automated waste reduction (idle resources, scheduling, rightsizing).
Need for anomaly detection, budgeting/forecasting, and reporting.

05The pitch

What the product does (core value proposition)

nOps is a FinOps / cloud cost optimization platform focused primarily on AWS, with modules for cost visibility & allocation, anomaly detection, forecasting/budgeting, and automated optimization (especially compute commitments and Kubernetes/compute optimization). The vendor positions the platform to combine reporting with automation (e.g., compute provisioning choices across On‑Demand / Reserved Instances / Savings Plans / Spot). Key product lines and concepts commonly referenced: - Cost Visibility & Allocation (hourly visibility, allocation/showback/chargeback-style reporting, anomaly detection). - Automated Rate Optimization (share-of-savings / pay-for-performance commercial approach described by the vendor). - Compute Copilot (automation for compute provisioning and commitment management; also markets compatibility with Karpenter/EKS/ASG/ECS). - FinOps agent positioning appears in documentation and partner listings.

Target market and positioning

nOps targets: - AWS-centric organizations that want automated savings without building extensive in-house FinOps tooling. - Teams with multiple AWS accounts / AWS Organizations, containerized workloads (EKS/ECS), and meaningful usage of commitments (Savings Plans / Reserved Instances). - Mid-market to enterprise buyers, plus consultancies/partners performing AWS Well-Architected Reviews for clients. nOps describes itself as an integrated FinOps platform that includes AI/ML capabilities and automation at the container level. Some reviewers note gaps or limitations in reporting unless buying add-ons.

Get a comprehensive analysis of nOps including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

Organizations that cannot tolerate broad IAM permissions or cannot reach agreement on least-privilege access; at least one customer rejected nOps on this basis.
Organizations that require best-in-class multi-cloud coverage today (AWS + Azure + GCP) with equal depth; reviewer feedback suggests an AWS focus.
Organizations that require near-real-time cost data for rapid feedback loops; CUR-based pipelines can introduce approximately 24-hour lag.
Organizations with highly fragile workloads where instance mis-sizing or aggressive automated changes are unacceptable unless strict approvals/guardrails are in place.
Organizations that primarily need Kubernetes optimization with transparent, usage-based pricing and minimal emphasis on AWS commitments; Kubernetes-focused platforms (e.g., CAST AI) may be simpler.
Organizations with mature internal FinOps and tooling where only incremental improvements are required; ROI may be weaker.

Disqualifiers / poor fit signals

Organizations requiring strict least-privilege IAM with limited ability to negotiate permissions.
Teams needing full multi-cloud parity (AWS + Azure + GCP) with equal depth.
Very small AWS spend where vendor fees likely outweigh realistic savings.

Issues and limitations indicated by reviews

IAM permissions perceived as overly permissive; least-privilege negotiation issues have been reported.
Multi-account IAM role work can be cumbersome.
Automation can be aggressive in some cases, with reported mis-sizing incidents.
Data latency: cost reporting can lag by about 24 hours due to CUR timing.
AWS-centric limitations: some users seek GCP/Azure coverage.
Reporting: advanced reporting may be an add-on; base reporting may feel limited to some buyers.

Vendor-documented constraints

nOps support SLA is documented (help desk hours, severity handling). Note the off-hours process for Severity 1 incidents requires contacting a designated CSM.

02Why they buy

Reported by customers (not just vendor claims)

Some customers report measurable savings (for example, several thousand dollars per month) and reduced manual effort.
Customer reviews frequently mention proactive support and engagement.

Differentiation claims to validate

Vendor-stated guarantees or credits related to commitment utilization should be validated in contract terms and exclusions.
Karpenter compatibility and Spot orchestration are emphasized for Kubernetes-heavy AWS environments; procurement teams should verify operational controls and failure modes.

Areas where competitors may have advantages

More transparent published pricing and simpler onboarding in some competitors.
Multi-cloud Kubernetes optimization depth (CAST AI).
Governance-as-code and multi-cloud allocation breadth (Harness).

03Field reports

Review platform snapshots

G2: very highly rated on G2.
Capterra: well rated on Capterra.
AWS Marketplace: majority positive ratings with a small number of lower ratings noted.

Direct quotes (positive)

From G2:

“We’ve had nOps for almost two years, and it instantly delivered meaningful monthly savings… It saves you money now.” (Director of Engineering).
“They are very responsive and always willing to help no matter what issues arise.”

From Capterra:

“nOps provided me with detailed data on our workloads’ consumption of AWS services and highlighted all possible savings at once.”
“Using nOps to automatically stop and start instances helped a lot… able to cease idle EC2 instances without requiring my interference.”

From AWS Marketplace reviews:

“Thanks to nOps, we are now saving substantial amounts in AWS costs each month.”

Direct quotes (negative / critical)

From AWS Marketplace reviews:

“…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 want you to add the ReadOnlyAccess policy… and then add explicit Denies… ReadOnlyAccess is managed by AWS and changes occasionally.”

From Capterra:

“I had to come and modify IAM roles for each account, which was quite cumbersome in a multi-account scenario.”
“…may be costly for small organisation.”

From G2:

“There have been bumps – a few mis-sized instances, or heavy handed automations.”
“It’s behind AWS data by about a day due to having to wait for the CUR report.”

Common themes: why customers choose nOps

Across platforms, common drivers cited by customers include:

Reported savings without building extensive internal tooling.
Centralized AWS Organization visibility and recommendations.
Commitment (RI/SP) management and reduction of manual toil.
Regular human support and check-ins cited by multiple reviewers.

Common themes: why customers struggle or may churn

Most credible churn-risk signals from the reviewed feedback:

Security/IAM friction (least-privilege concerns, setup burden across accounts).
Automation trust (mis-sizing or aggressive actions can create perceived operational risk).
Reporting depth behind paywall (advanced reporting as an additional service).
AWS-only limitations (some reviewers want multi-cloud parity).

Consulting partner (partner use case)

A vendor case study describes a consulting partner using nOps to perform AWS Well-Architected Reviews, leveraging partner portal features (white labeling, custom questions, encryption, versioning) and automated discovery of AWS architecture.
Claimed benefit: faster, more comprehensive reviews than manual surveys; identifies cost/security gaps across pillars.

Critical evaluation: The case study is vendor-authored; it emphasizes benefits but provides limited quantitative methodology (baseline vs. after, time saved measured how, error rates). Treat as directional evidence of capability rather than independently validated ROI.

Standards-focused organization

A vendor case study highlights Business Contexts for pseudo-tagging/showback, hourly cost breakdowns, amortization, and an assessment tool aligned to architecture best practices.

Critical evaluation: Again, vendor-authored and light on independently audited metrics; useful for understanding which features are pitched as differentiators (allocation/showback and assessments).

Vendor/press metrics worth validating

definitions of qualifying workloads
baseline methodology
savings calculation methodology (gross vs. net of fees)
precise contract terms for any guarantees or credits

04Best fit

Company size

Best fit: mid-market and enterprise organizations with meaningful AWS spend where vendor fees are justified.
Potential fit for smaller organizations: may be appropriate if AWS spend is meaningful and the team lacks FinOps expertise, though some reviewers note it can be costly for very small organizations.

Industries

Seen in reviews/case studies and likely fit:

SaaS/tech, IT services, telecom, and organizations with steady compute spend.
Regulated industries can be a fit if IAM/security concerns are addressed (request SOC 2 report and permission scoping).

Roles/personas

Decision makers: VP Engineering, CTO, Head of Infrastructure/Platform, FinOps lead, Cloud Center of Excellence.
End users: Cloud engineers, DevOps/SRE, Finance/FinOps analysts.

Pain points addressed

Difficulty managing RI/SP/Spot commitments efficiently.
Inadequate cost allocation and accountability across teams.
Need for automated waste reduction (idle resources, scheduling, rightsizing).
Need for anomaly detection, budgeting/forecasting, and reporting.

05The pitch

What the product does (core value proposition)

Key product lines and concepts commonly referenced:

Cost Visibility & Allocation (hourly visibility, allocation/showback/chargeback-style reporting, anomaly detection).
Automated Rate Optimization (share-of-savings / pay-for-performance commercial approach described by the vendor).
Compute Copilot (automation for compute provisioning and commitment management; also markets compatibility with Karpenter/EKS/ASG/ECS).
FinOps agent positioning appears in documentation and partner listings.

Target market and positioning

nOps targets:

AWS-centric organizations that want automated savings without building extensive in-house FinOps tooling.
Teams with multiple AWS accounts / AWS Organizations, containerized workloads (EKS/ECS), and meaningful usage of commitments (Savings Plans / Reserved Instances).
Mid-market to enterprise buyers, plus consultancies/partners performing AWS Well-Architected Reviews for clients.

nOps describes itself as an integrated FinOps platform that includes AI/ML capabilities and automation at the container level. Some reviewers note gaps or limitations in reporting unless buying add-ons.

Get a comprehensive analysis of nOps including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →