nOps review

nOps is a hosted cloud cost management platform, not a library or command-line tool. It sits alongside cloud accounts and provides cost visibility, allocation, anomaly detection, recommendations, and commitment management. The homepage says teams connect AWS, Azure, and GCP accounts with read-only access; it also says there are no agents or infrastructure changes.

Its commitment workflow identifies and manages Reserved Instances, Savings Plans, and GCP Committed Use Discounts (CUDs). The vendor says its engine maps usage patterns, purchases and manages commitments, and continuously rebalances them hourly. That puts nOps in the FinOps and cloud operations layer, rather than in an application request path. It also presents cost reporting for Kubernetes, SaaS, and AI services, with hourly allocation to models, accounts, teams, customers, and features. For AI spend, it names Bedrock, Cursor, Claude, and OpenAI. The homepage describes a FinOps AI agent for cost questions and tasks, but does not describe a public API for integrating that agent into an application.

The integration surface described on the homepage is cloud-account connection: link AWS, Azure, or GCP accounts using read-only access. The vendor says setup takes under five minutes, requires no agents, and makes no infrastructure changes. For commitment optimization, nOps says it automatically purchases and manages the relevant mix of RIs, Savings Plans, and CUDs.

The homepage also names cost integrations or coverage for Bedrock, Cursor, Claude, and OpenAI, and announces Cursor and Claude.ai Enterprise integrations. It does not name a public REST API, webhooks, CLI, SDK, supported programming languages, or package repositories. We would not build a code-level dependency around nOps without confirming those interfaces and their documentation directly with the vendor. Ask whether cost data and recommendations are available programmatically, how credentials are scoped and rotated, and whether integrations support your cloud account structure. The homepage points prospective customers to a platform tour and case studies; it does not describe a developer documentation portal.

The pricing page lists two models, with no monthly or annual prices and no published starting price. Share of Savings is for automated cloud commitment savings and charges a percentage of savings realized. The plan lists AWS, GCP, and Azure support, automated optimization, minimal IAM permissions, and a free savings analysis. Ask how realized savings are calculated, what baseline is used, and whether the fee applies to all optimized workloads or only eligible commitments.

The visibility plan is a fixed fee based on cloud spend. It includes hourly visibility across multicloud, Kubernetes, SaaS, and AI costs, anomaly detection, root-cause analysis, recommendations, and a 14-day trial with core features. The vendor does not publish the fixed fee, spend bands, or trial conversion terms. No free plan or add-ons are listed. The bill therefore depends on your cloud spend or realized savings, but the exact rate and treatment of usage changes are unknown. Request a written quote that covers spend growth, trial limits, billing cadence, and any overage or cancellation terms before rolling out to production.

The homepage presents nOps as a hosted platform, but does not publish an open-source license, source repository, or self-hosted deployment option. It describes connecting cloud accounts to the service, so teams should plan for a vendor-hosted workflow unless nOps confirms another deployment model. Ask the vendor whether customer data can be exported, in what formats, and whether exports include allocation rules, tags, recommendations, and historical cost records.

The main lock-in risk is operational rather than a stated proprietary file format: commitment recommendations and automated purchases become part of how a team manages discounts. Before enabling automatic commitment management, confirm who owns purchased commitments, how they are managed if you leave, and what happens to them after cancellation. Also ask whether you can export configuration and audit history, and whether disabling automation leaves cloud commitments unchanged. The available material does not publish migration tooling or exit terms, so include them in procurement review.

The vendor says account connections use read-only access and require no agents or infrastructure changes. That reduces the stated footprint, but the homepage also says nOps automatically purchases and manages commitments; confirm the permissions required for those actions separately from the read-only visibility connection. Review IAM policies, approval controls, audit logs, and rollback procedures before enabling automated purchases.

The homepage claims hourly rebalancing and real-time tracking for savings metrics, but it does not publish service-level objectives, data freshness guarantees, API rate limits, account or workload caps, or incident history. Ask how the platform behaves when billing data is delayed or cloud accounts are disconnected, and how it handles conflicting recommendations. Security and compliance certifications, data residency, retention, encryption, and support response targets also need confirmation before production use. The 14-day trial is listed for the visibility plan; confirm what data and features remain available after it ends. Teams with strict availability or compliance requirements should get these terms in writing.