> For the complete documentation index, see [llms.txt](https://docs.noros.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noros.ai/features/savings-opportunities.md).

# Savings Opportunities

Find actionable ways to reduce cloud spending. Noros analyzes your cost and usage data to identify areas where you may be overspending and surfaces opportunities to optimize.

### What Noros Can Identify

#### Commitment Coverage Gaps

Noros analyzes your on-demand vs. reserved vs. savings plan spend to identify where additional commitments could reduce costs:

* "What percentage of my compute is on-demand vs. reserved?"
* "Where do I have commitment coverage gaps?"
* "How much could I save with better savings plan coverage?"

#### High-Cost Services and Resources

Noros can pinpoint the services and resources driving your costs, helping you identify candidates for optimization:

* "What are my most expensive resources?"
* "Which services have the highest cost growth?"
* "Show me resources that cost more than $100/day"

#### Rightsizing Recommendations

Noros can report North's rightsizing recommendations for your resources, including the projected saving on each one:

* "What are my rightsizing recommendations?"
* "Which instances are oversized?"
* "How much would rightsizing save us this month?"

#### Spending Patterns and Waste

By analyzing your spending trends, Noros can surface patterns that suggest waste or inefficiency:

* "Are there any services I'm paying for but not actively using?"
* "What are my top savings opportunities?"
* "How can I reduce my EC2 costs?"

#### Purchase Type Optimization

Noros breaks down your spend by purchase type to show where on-demand pricing is costing you more than it needs to:

* "Break down my costs by on-demand vs. reserved vs. savings plans"
* "What's my spot instance usage?"
* "Which services would benefit most from reserved pricing?"

### Example Conversations

**Quick savings overview:**

> "What are my top savings opportunities?"
>
> Noros analyzes your spending patterns and commitment coverage, then highlights the areas with the most potential for savings.

**Coverage analysis:**

> "What percentage of my compute is on-demand?"
>
> Noros breaks down your compute spend by purchase type and identifies how much of your eligible spend isn't covered by commitments.

**Cost investigation:**

> "Which resources cost the most and are they right-sized?"
>
> Noros identifies your highest-cost resources and provides context about their spending trends.

### Go Further with North

Noros reports rightsizing recommendations in chat, so you can see what to change and what it would save. North is where you act on them. The full platform adds the workflow around each recommendation: instance-level detail for EC2, ECS, EBS, Lambda, and Auto Scaling Groups based on actual utilization metrics, migration complexity scoring, configurable look back periods and headroom, and sharing through Slack, Jira, or email with applied results tracked back into the models. [Learn more about upgrading →](/other/powered-by-north.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.noros.ai/features/savings-opportunities.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.