How it works

Three steps. About five minutes.

1
Connect your AWS account
A 12-line CloudFormation template, one read-only IAM role, zero write permissions. Revoke it anytime from the AWS console.
2
See your waste, in dollars
Idle EBS volumes, unused IPs, forgotten RDS, oversized instances. Each with a monthly price tag. No 300-page report.
3
Delete with one click
You pick what goes. We handle the safe-delete order — snapshots first, dependencies checked. You approve every action.
The usual suspects

What founders forgot last month.

Real findings from beta accounts — anonymized, dollar-weighted, sorted by how often they show up.

CloudWatch
Never-expire log retention
−$180/mo
86%
EBS
Idle volumes from old tests
−$340/mo
78%
RDS
Over-provisioned instances
−$620/mo
64%
EC2
Unused Elastic IPs
−$90/mo
53%
VPC
Forgotten NAT gateways
−$310/mo
41%
EC2
Stopped instances with EBS
−$220/mo
38%
Sample of 47 beta accounts · Q1 2026
Why Signal

Another dashboard won’t fix your bill. A list of what to delete will.

We skip the 300-line cost breakdown. You get a short list of what’s burning money — each item with a dollar figure and a one-click delete.

Built for founders, not FinOps teams
If you can read "you’re paying $84/mo for this unused volume," you can use Signal. No DevOps background, no acronym decoder.
Scan in 2 minutes. Waste list on your screen.
Connect a read-only IAM role. We read Cost Explorer and CloudWatch. Your first waste list appears before your coffee’s done.
Delete with one click. Safely.
Pick what goes — we handle the safe-delete order. Snapshots first, dependencies checked. You approve every action; nothing runs in the background.
FAQ

The stuff you’re about to wonder.

We start read-only — we can see your resources, we can’t touch them. You revoke the IAM role anytime from the AWS console. Deletes only happen when you explicitly click; nothing runs in the background. Full IAM policy is published on our security page.