See the first-scan brief before you connect anything
This preview shows the structure of the executive summary and top-5 opportunity list that OpsCurb uses during the first review. It reflects the format we deliver, not a fabricated testimonial or named customer claim.
A first-scan brief you can assign, track, and forward
Most cloud cost tools stop at a savings number. Your first scan produces a concise executive summary, a ranked action queue, and owner-ready remediation guidance. See the product tour.
Sample first-scan brief
Executive Summary
In a typical $5,000/mo account, this first scan surfaced about $424/mo in recurring, low-risk waste. That is enough to matter, but still believable for a first pass focused on obvious cleanup and storage tuning. The point is not just the detections. The first actions stay visible first: one is overdue, one is escalated, and one still needs an owner. Leadership can see what is owned, what is stuck, and what needs follow-through before the next scan.
Ranked action queue
Overdue → unassigned → monthly impact#1 priority
Idle RDS development instance
Confirm no connections for 14 days, take a final snapshot, then stop and remove the single-AZ dev instance in the next change window.
$138/mo
Owner: Platform
#2 priority
NAT route to S3 still pending
Route S3 traffic through a gateway endpoint, validate data-path performance, then remove the NAT path for that workload.
$71/mo
Owner: Networking
#3 priority
CloudWatch retention drift
Assign the owner, move noisy debug groups to 7-day retention, and keep audit-oriented logs at 30 days.
$33/mo
Owner: Unowned
#4 priority
Storage cleanup batch in 3 regions
Confirm no point-in-time recovery dependency, then delete 11 orphaned gp2 volumes and 6 stale AMI snapshots in one cleanup batch.
$94/mo
Owner: Infra
#5 priority
gp2 migration backlog
Start with 4 low-risk 150-300GB gp2 volumes in dev and staging, migrate to gp3, then re-run performance validation before queue expansion.
$88/mo
Owner: App team
Lifecycle snapshot
Assigned → overdue → escalated → resolved or snoozed. This is the workflow layer, not just a list of cleanup checks.
2
findings in this state
1
findings in this state
1
findings in this state
1
findings in this state
What this proves
- Overdue or unowned waste is obvious before it slips back into backlog debt.
- Each action shows who owns it and what should happen next.
- Leadership can forward a short summary and see what still needs escalation.
Want this for your own AWS account instead of a sample?