<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Recoup</title>
    <description>The latest articles on DEV Community by Recoup (@recoup).</description>
    <link>https://dev.to/recoup</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4257012%2F96e020c5-ba66-492f-868c-430f80414cc9.jpeg</url>
      <title>DEV Community: Recoup</title>
      <link>https://dev.to/recoup</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/recoup"/>
    <language>en</language>
    <item>
      <title>Your AWS bill has a graveyard. I built a tool that finds the bodies and the person who buried them.</title>
      <dc:creator>Recoup</dc:creator>
      <pubDate>Sat, 21 Nov 2026 09:43:59 +0000</pubDate>
      <link>https://dev.to/recoup/your-aws-bill-has-a-graveyard-i-built-a-tool-that-finds-the-bodies-and-the-person-who-buried-them-43hi</link>
      <guid>https://dev.to/recoup/your-aws-bill-has-a-graveyard-i-built-a-tool-that-finds-the-bodies-and-the-person-who-buried-them-43hi</guid>
      <description>&lt;p&gt;Last month somebody on your team spun up a GPU box "just to test something."&lt;/p&gt;

&lt;p&gt;It's still running. Nobody remembers why. The person who started it has changed teams, and the ticket that explains it was closed in a cleanup sprint. Meanwhile it quietly adds a line to your invoice every hour.&lt;/p&gt;

&lt;p&gt;Multiply that by every account, every region, and every engineer who has ever typed &lt;code&gt;aws ec2 run-instances&lt;/code&gt; on a Friday afternoon. That is your cloud graveyard: unattached volumes, idle load balancers, old snapshots, orphaned IPs, forgotten test stacks.&lt;/p&gt;

&lt;p&gt;Everyone knows it exists. Almost nobody cleans it, for three reasons:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Finding it is tedious.&lt;/strong&gt; The resources are spread over a dozen regions and several accounts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deleting is scary.&lt;/strong&gt; "What if something still depends on it?" is a fair question, and nobody wants to answer it at 2 a.m.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nobody owns it.&lt;/strong&gt; If you can't say whose it is, you can't ask them to delete it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;So I built &lt;strong&gt;Recoup&lt;/strong&gt;, a tool aimed at those three problems.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Recoup does
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;It finds the stale stuff, across accounts and regions.&lt;/strong&gt;&lt;br&gt;
Point it at your AWS accounts with read-only credentials. It sweeps the regions and lists resources that look forgotten.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It tells you whose they are, and which code made them.&lt;/strong&gt;&lt;br&gt;
Each finding is attributed to an owner and cross-referenced to the code that created it. "Who do I ask?" stops being a Slack archaeology project.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It shows its maths.&lt;/strong&gt;&lt;br&gt;
Every monthly-waste estimate comes from a formula you can inspect. If a number looks wrong, you can see exactly why it is that number, and argue with it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It writes the cleanup, but never runs it.&lt;/strong&gt;&lt;br&gt;
You get tiered cleanup scripts, from safe to risky, and they are reversible. Nothing is executed from the browser. You read the script and you run it, or you don't.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It remembers.&lt;/strong&gt;&lt;br&gt;
The History page asks the uncomfortable question: &lt;em&gt;did the waste come back?&lt;/em&gt; Cleaning up once is easy. Staying clean is the hard part, and recurrence shows you whether the same leak reopened.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It makes the case to your finance team.&lt;/strong&gt;&lt;br&gt;
There's a savings report as a PDF, built for the person who approves the budget and doesn't care what a NAT gateway is.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part I care most about: it's read-only
&lt;/h2&gt;

&lt;p&gt;A tool that scans your cloud account has to earn trust before it gets any. So:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It needs &lt;strong&gt;read-only&lt;/strong&gt; credentials.&lt;/li&gt;
&lt;li&gt;It doesn't delete anything.&lt;/li&gt;
&lt;li&gt;Nothing runs from the browser.&lt;/li&gt;
&lt;li&gt;You can revoke its access at any time.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It hasn't had an independent security review yet, and I won't claim it has. That is planned. For now, the safest design I could think of is one that can't change your account at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who it's for
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Platform and DevOps engineers who inherited an account they didn't build&lt;/li&gt;
&lt;li&gt;Startups whose AWS bill grew faster than their revenue&lt;/li&gt;
&lt;li&gt;FinOps folks who are tired of sending spreadsheets that nobody acts on&lt;/li&gt;
&lt;li&gt;Anyone who has said "we should really clean that up" more than twice&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  It's a pilot, so it's invite-only
&lt;/h2&gt;

&lt;p&gt;Recoup is in a closed pilot. Sign-up needs an invite code, and I'm handing them out in small batches so I can talk to every early user.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;To request one:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;📧 Email &lt;strong&gt;&lt;a href="mailto:hello@recoupify.in"&gt;hello@recoupify.in&lt;/a&gt;&lt;/strong&gt; with the subject &lt;code&gt;Recoup invite&lt;/code&gt;.&lt;br&gt;
Tell me in a line or two how many AWS accounts you run and what hurts the most. I read every message.&lt;/p&gt;

&lt;p&gt;🌐 Site: &lt;strong&gt;&lt;a href="https://recoupify.in" rel="noopener noreferrer"&gt;https://recoupify.in&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Early users get a direct line to me, and their feedback decides what gets built next.&lt;/p&gt;

&lt;h2&gt;
  
  
  One question for the comments
&lt;/h2&gt;

&lt;p&gt;What's the most expensive thing you ever found running in AWS that nobody could explain?&lt;/p&gt;

&lt;p&gt;Mine is a story for another post. I'd like to hear yours first.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;If this was useful, a ❤️ or a 🦄 helps other engineers find it. If your AWS bill is a mystery, you know where to email.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>aws</category>
      <category>devops</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
