SaveOps: the FinOps tool I ended up turning into a SaaS

July 27, 2026

I’ve spent more than 5 years working in FinOps (before I even knew that’s what it was called, or that it was what I was doing). First from consulting, then from inside a product company.

And every morning I ended up doing the same thing: opening AWS Cost Explorer and hunting for patterns by hand. Runaway growth, services eating up half the bill, things nobody has touched in months.

Tired of repeating it, I started coding. A few evenings later I had a tool that did the work on its own.

SaveOps is born

I’ve decided to release it as a SaaS, so this knowledge can reach whoever needs it. It’s called SaveOps.

It keeps a live inventory of everything you have running and, from there, tells you where you’re overpaying: resources to delete, others to right-size, with the numbers right next to them. It also flags configurations that don’t cost you money but do cost you headaches, like open ports or overly permissive policies. And it compares your real infrastructure against your Terraform state files, to show you what’s running that nobody manages.

All of this rolls up into a FinOps Health Score for compute, storage, databases, and network, with the possible improvements for each area.

Right now it covers the main AWS services. The plan is to keep adding more, and later reach other clouds.

Try the beta

It’s currently in beta and free. I’m looking for people who manage AWS infrastructure and feel like trying it out. It only needs read-only permissions, and deployment is done with Terraform or CloudFormation.