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.