Opportunity detail
Everything about one opportunity, why it saves money, the plan, the owner, and the rule that found it.
Select any opportunity in the tracker to open its detail page, for example REC-4501 · Compute Savings Plan · cover steady on-demand.
Header
| Field | Meaning |
|---|---|
| Type and status | For example Commitment · Open |
| Scope | Provider, product, account, and resources in scope |
| Saves | Projected monthly saving, net of commitments |
| Effort | Low, Medium, or High, with a note such as minutes, no restart |
| Risk | Low, Medium, or High, with a note such as reversible · rollback in hours |
| Evidence | strong, fair, or low, and the lookback, such as 90 d |
| Decide by | Days left before the SLA escalates it |
Actions: Summarise (Iris writes a summary you can paste anywhere), Share, and Remediate.
Tabs
Why this saves money — Iris explains the finding, when it was detected, and when it was last re-checked. It breaks the reasoning into:
- Utilisation — the measured usage, such as 90-day steady-state on-demand $61K/mo, and how it was measured.
- Binding constraint — what limits the size of the change, such as sizing to the p10 floor rather than the average.
- Blast radius — what the change touches, such as Billing only — no resource changes.
The evidence sources are listed underneath, with See the numbers.
Plan — numbered steps. Each step is marked done, has a button (such as Request approval), or runs auto. You can hand the plan to a coding agent or run it by hand.
Side panels
Who and by when — owner, team, who assigned it and when, decide-by date, and status.
Where it sits — account, provider, tags, and today's cost.
Detection rule — the rule that found it and its parameters, such as:
| Parameter | Example |
|---|---|
| Rule | uncovered-steady-usage |
| Lookback | 90 days |
| Coverage below | 70% |
| Min saving | $50/mo |
The panel notes whether the rule uses shipped defaults or has been tuned.
Footer actions
| Action | What it does |
|---|---|
| Remediate | Start the plan |
| Ticket chip | Shows the linked ticket and its Jira key, such as TKT-112 · In review · FIN-470 |
| Acknowledge & schedule | Accept the finding and set a date |
| Snooze | Hide it for a while |
| Reassign | Change the owner |
| Decline… | Close it as won't do, with a reason |
Example: a commitment purchase
Size to the floor
OpsLyft sizes the commitment to the p10 of hourly usage over 90 days, so a quiet month still uses it. done
Approve the purchase
Finance approves the term and payment option. Select Request approval.
Purchase
Bought through the payer account. auto
Watch coverage
Coverage and utilisation are re-checked monthly. auto
Commitments can't be cancelled once bought. For Reserved Instances, OpsLyft never rates risk as Low, even though the change is billing-only.