Risk Tolerance
The Risk Tolerance setting controls how cautious CloudCtrl is when showing you recommendations. If your team prefers only the safest, easiest changes, set a stricter tolerance. If you're comfortable evaluating each recommendation on its own merits, leave it open.
The setting applies to your whole organisation and is saved between sessions.
Presets
| Preset | What it shows |
|---|---|
| None (default) | All recommendations, regardless of risk or effort. Same as Aggressive. |
| Conservative | Only low-risk recommendations where the change is quick to make and can be undone if needed. Best for teams with strict reliability requirements or who are new to acting on recommendations. |
| Balanced | Recommendations with moderate risk. A good starting point for most production environments. |
| Aggressive | All recommendations — your team will judge the risk for each one. |
How filtering works
CloudCtrl uses the risk and effort signals provided by the cloud provider (or estimated by CloudCtrl where the provider doesn't supply them) to decide which results to show.
- Conservative — only shows results where the performance risk is very low, the effort is low or trivial, and the change can be rolled back.
- Balanced — only shows results where the performance risk is moderate or lower.
- Aggressive / None — shows everything.
When risk or effort information isn't available for a result, it is included in the list regardless of the preset. A warning may be shown in the UI to indicate that the result's inclusion is based on incomplete data.
Changing the setting
Open the Risk Tolerance selector in the Recommendations view. Your choice takes effect immediately — the list refreshes to show only the results that match your selected preset.
Recommendations filtered out by your risk tolerance setting are not counted in your headline savings total.