FinOps Toolkit: start with context, end with clarity

The context

The FinOps Toolkit began as an experiment, a way to turn the idea that context is everything into something you can actually see, touch, and run.

I didn’t want another concept or framework. I wanted something real — something people could open, use, and understand directly.

It was also my way of exploring the idea of moldable development, as described by Feenk: software that adapts to its context rather than forcing a fixed shape. I wanted to know whether I could build FinOps tools that worked the same way — flexible, composable, explainable.

When I looked around for examples of systems that already embodied that spirit, the answer was sitting right in front of me: the shell.
A space where every tool is small, focused, and can be combined freely. That felt exactly right.

So I started there.
Because I work in FinOps, the first problem was obvious: I needed data, and AWS APIs are a labyrinth. So I began with a script to extract costs, then added a forecaster. Each new tool followed the same rule: keep it simple, contextual, and composable.

Another layer emerged: how to accelerate creation itself.
I wanted to use generative AI not as a crutch, but as a collaborator, exploring how to teach a system the minimal concepts needed to generate new, reliable tools. The Toolkit became both a testbed for that idea and a real working suite for anyone practicing FinOps.

That’s how the FinOps Toolkit was born: a collection of open-source tools designed to make the principle of context visible and usable.

Why I built it

Every FinOps conversation I’ve ever had eventually ends with the same phrase:

“It depends [on the context].”

That’s the truth nobody can automate away.

The same number can mean three different things depending on who looks at it.
A product lead sees opportunity.
Finance sees risk.
An engineer sees an architectural choice.

And yet, most FinOps tools try to compress all of that into a single dashboard or metric.
They trade nuance for visibility, and in doing so, they lose what makes FinOps work: understanding why.

I built the FinOps Toolkit as a way to bring the context back in.
It’s not a platform or a SaaS product. It’s a set of simple, composable tools — designed to be run locally, in the terminal, with outputs you can redirect, remix, and reason about.

Because FinOps should fit your context, not force you into someone else’s.

What it is

The Toolkit is a living, open collection of Python scripts and shell helpers that:

• Pull and analyse cloud cost and usage data.
• Forecast future trends using multiple statistical and ML methods.
• Detect anomalies, track budgets, and connect spend with business context.
• Output clean CSVs you can use anywhere: Excel, notebooks, or pipelines.

Some tools are AWS-specific, living under an aws/ directory.
Others — like the forecasting and analysis scripts — are vendor-neutral, built to work with any time series.

If you can put it in a table with dates and numbers, the Toolkit can help you make sense of it.

What it’s not

It’s not another dashboard.
It’s not an API service.
And it’s definitely not a FinOps “platform.”

It’s a way to think and work with your data — locally, transparently, and contextually.

You can pipe, share, version-control, and extend everything yourself. No hidden magic. No black boxes.

How it started

These tools began as small internal scripts I used to make AWS data explainable.
Then I started adding forecasting, variance checks, and anomaly detection.
What connected them all was a philosophy:

Start with context. End with clarity.

Each script answers a question that depends on who’s asking — not just what’s being measured.

That’s the essence of FinOps in practice: making data personal, not abstract.

What’s next

Over the coming weeks, I’ll publish a post for each tool in the FinOps Toolkit.
Each post will focus on a different context — the analyst, the engineer, the product owner, the finance partner — and show how to use the tools in a way that makes sense for you.

If you’d like to follow along:

• 🌐 Bookmark github.com/fcontrepois/finops-toolkit
• 📰 Follow the site for updates, examples, and essays about FinOps in context
• 💬 Share your stories and use cases — the Toolkit grows with your context

Why this matters

FinOps is often described as the balance between cost, speed, and quality.
But underneath that, it’s really a practice of understanding people through data.

When we talk about cloud spend, we’re really talking about behaviour, priorities, and trade-offs.
We can’t automate that understanding — but we can design tools that make space for it.

The FinOps Toolkit is my attempt to do exactly that.

Because understanding your AWS bill shouldn’t require a séance, a therapist, or a second mortgage — just the right context, a few well-named CSVs, and a cup of tea.

👉 Explore the FinOps Toolkit on GitHub
(Open-source, MIT licensed, contributions welcome.)