Skip to main content
Recommendations shows you practical ways to lower your cloud bill. nOps reviews your usage and configuration every day and lists the changes worth making. Each one comes with an estimated monthly saving, how much effort it takes, and clear steps to put it in place.

​
Get started

  1. Sign in to nOps.
  2. In the sidebar, open Inform → Recommendations, or go to clara.nops.io/recommendations.
  3. Start with the largest savings or the lowest effort, open a recommendation, and follow the steps.
Recommendations used to be a tab on the Insights page. They have their own page now, and old Insights links still bring you here.

​
Your savings at a glance

The cards at the top of the page summarize your optimization work:
  • Savings Summary: what you could save each month and each year if you act on every open recommendation.
  • Recommendations by effort: how your open savings split across Low, Medium, and High effort, so you can pick off the quick wins first.
  • Savings achieved: the savings from changes you’ve already made, shown as Monthly savings and Saved to date.

​
Open, In progress, and Done

Some organizations see three tabs instead, which follow each recommendation from start to finish: The card above each tab shows that stage’s monthly savings and how much of your total savings you’ve already achieved.

​
Browse recommendations

  • Switch between Grouped, which shows one row per recommendation type with its resources underneath, and Table, which lists every resource on its own row.
  • Use Search recommendations to find a resource or recommendation by name.
  • Choose a date range, from Last 7 days to Last year, to see recommendations by when they were first found.
  • Narrow the list with filters for Account, Region, Effort, Category, Action, and Service.
  • Select Download CSV to export the rows you’re viewing.

​
Recommendation details

Click any recommendation to see its details:
  • Overview: the monthly saving, effort level, how long ago it was found, and a plain-language summary of the opportunity.
  • Recommendation Details: the evidence behind it, such as the resource’s current configuration and usage.
  • How to Implement: step-by-step instructions and commands you can copy. You can also create a ticket, hand the work to an AI coding assistant, or open a pull request.
  • Monitor & Track (if your organization has it): nOps watches your billing after the change to confirm the savings.

​
Savings statuses

When nOps tracks a change, you’ll see one of these statuses:

​
Share recommendations with your team

  • Create issues: connect Jira or Linear, select recommendations, and click Create issues to send them to the team that owns the resources. See Issue tracker notifications.
  • Saved views: save your filters as a report (Private or Shared) so you and your team can come back to the same list.
  • Email schedules: send a saved view now, or schedule a recurring email, from the Recommendations tab on the Reports page.

​
Effort levels

Every recommendation is rated Low, Medium, or High effort. The rating depends on whether the change needs engineering review, a restart, operating system or application changes, or code changes. A lower effort rating usually means fewer people involved and less risk of disruption.

​
What nOps recommends

nOps looks for savings across many areas, including:
  • Rightsizing: resize EC2 instances, RDS databases, or Lambda functions that are larger than they need to be.
  • Idle resources: stop or remove resources nobody is using, such as idle databases, load balancers, and NAT gateways.
  • Storage: move EBS volumes to gp3, delete unused volumes and old snapshots, or turn on S3 Intelligent-Tiering.
  • Graviton: move EC2, RDS, ElastiCache, and OpenSearch to AWS Graviton for better price-performance.
  • Modernization: upgrade to newer instance generations, or switch Aurora to I/O-Optimized.
Recommendations cover AWS, Azure, Google Cloud, Databricks, and AI tools. For the full list, see Supported recommendations.

​
FAQs

Anyone in an organization on the Inform plan, as long as their role includes Recommendations. If your role limits you to certain accounts or regions, you only see recommendations for those.
Insights was split into two pages: Recommendations and Anomalies. Both are in the Inform section of the sidebar, and old Insights links redirect automatically.
It adds up the savings from recommendations you’ve already acted on. Where nOps can check your billing, a saving counts once your bill confirms it. Ticket creation or marking a recommendation as implemented alone doesn’t add to the total.
Estimates are based on your current usage and your cloud provider’s prices. Your actual savings can be different if your usage, prices, or the way you make the change are different.
Start with Low effort recommendations that save the most. Filter by Effort, then sort by savings.
Every day. A recommendation goes away once the opportunity is gone.